ParallelComputingService / Client / exceptions / ConflictException

ConflictException#

class ParallelComputingService.Client.exceptions.ConflictException#

Your request has conflicting operations. This can occur if you’re trying to perform more than 1 operation on the same resource at the same time.

Examples

A cluster with the same name already exists.
A cluster isn’t in ACTIVE status.
A cluster to delete is in an unstable state. For example, because it still has ACTIVE node groups or queues.
A queue already exists in a cluster.

Example

try:
  ...
except client.exceptions.ConflictException as e:
  print(e.response)

response#

The parsed error response. All exceptions have a top level Error key that provides normalized access to common exception atrributes. All other keys are specific to this service or exception class.

Syntax

{
    'message': 'string',
    'resourceId': 'string',
    'resourceType': 'string',
    'Error': {
        'Code': 'string',
        'Message': 'string'
    }
}

Structure

(dict) –

Your request has conflicting operations. This can occur if you’re trying to perform more than 1 operation on the same resource at the same time.

Examples
- A cluster with the same name already exists.
- A cluster isn’t in ACTIVE status.
- A cluster to delete is in an unstable state. For example, because it still has ACTIVE node groups or queues.
- A queue already exists in a cluster.
- message (string) –
- resourceId (string) –
  
  The unique identifier of the resource that caused the conflict exception.
- resourceType (string) –
  
  The type or category of the resource that caused the conflict exception.”
- Error (dict) – Normalized access to common exception attributes.
  - Code (string) – An identifier specifying the exception type.
  - Message (string) – A descriptive message explaining why the exception occured.