f70bfbf711
The SolidFire driver retries API requests in case a connection error occurrs. When network is unstable, there may be the possibility that the SolidFire backend successfully receive and process a create volume operation, but fail to deliver the response back to the driver. When this scenario occurrs, the SolidFire driver automatically resends the request, creating a second volume and leaving a duplicate unused. Although this doesn't affect driver functionality at first moment (the volume id from the cluster is always correctly associated to cinder provider id), further operations may hit the unused volume, leading to unexpected hehavior. This patch fixes this issue by: 1. Checking if the volume name already exists in the backend before trying to create it. Volume creation will raise a exception and abort in case of a volume is found. 2. Checking for volume creation right after a read timeout is detected, preventing invalid API calls. 3. Adding option ´sf_volume_create_timeout´ to the SolidFire driver, to allow users to set the appropriate timeout value for their environment. Closes-Bug: #1896112 Change-Id: I4383b691a8cc4aacb046332e418aafb88ba8ba56 (cherry picked from commit |
||
|---|---|---|
| .. | ||
| drivers | ||
| flows | ||
| targets | ||
| __init__.py | ||
| api.py | ||
| configuration.py | ||
| driver.py | ||
| driver_utils.py | ||
| group_types.py | ||
| manager.py | ||
| qos_specs.py | ||
| rpcapi.py | ||
| throttling.py | ||
| volume_migration.py | ||
| volume_types.py | ||
| volume_utils.py | ||