409 Error Occurs When Creating or Moving a File System or Mount Target

When creating or moving a file system or mount target from one compartment to another, you encounter a 409 error.

For example:

oci.exceptions.ServiceError: {'opc-request-id': <<OPC REQUEST ID>>, 'code': 'Conflict', 'message': 'Another filesystem is currently being provisioned, try again later', 'status': 409}

Cause: There are constraints that limit the number of concurrent operations that a tenancy can perform on file system and mount target resources in a region:

• Each tenancy in a region can have one CreateFileSystem or ChangeFilesystemCompartment operation in progress at a time.
• Each tenancy in a region can have one CreateMountTarget or ChangeMountTargetCompartment operation in progress at a time.

Solution: Retry the operation, either manually or programmatically. The default retry strategy for the OCI SDK is to not retry 409 conflicts, so create a custom retry strategy that retries on 409.

For more information, see 409 error occurs when creating or moving a file system or mount target in Known Issues.

For more information about retry strategies, see SDK Behaviors - Retries.

Several examples of building a custom retry strategy are provided at https://github.com/oracle/oci-python-sdk/blob/master/examples/retries.py.