Veritas CloudPoint Release Notes
- Getting help
- Known issues
- Fixed issues
Indexing or classification jobs may fail in an Azure environment (13940)
This issue occurs when CloudPoint is running in an Azure cloud environment.
When multiple indexing or classification operations are run simultaneously, then one of the jobs might fail and the other jobs remain stuck in a queued state.
The following error appears in the logs:
flexsnap-coordinator: GenericError: The maximum number of data disks allowed to be attached to a VM of this size is 4. [src/azure/azure.py:131]
When an indexing or classification job is triggered on a disk-level snapshot, CloudPoint attaches the disk snapshot to the CloudPoint host instance to perform the operation. The disk is detached from the host after the operation is completed. This process is repeated for each indexing or classification operation.
In a case where multiple simultaneous operations are triggered, it is observed that some times CloudPoint fails to detach the snapshot disk from the CloudPoint host. As a result, the disk attach operation for the next indexing or classification job remains in a queued state and may eventually fail.
If you encounter such an issue, verify if there are any snapshot disks attached to the CloudPoint host instance and are currently not in use. If you see any such disks, detach them from the instance.
This will ensure that subsequent indexing or classification jobs do not fail.