Description of problem: When we enable destroy_empty_storage_group and a storage group is destroyed after it's emptied, the VNX driver or storops cache isn't updated and the driver doesn't recreate the storage group upon subsequent attachment. How reproducible: 100% Steps to Reproduce: 1. Enable destroy_empty_storage_group initiator_auto_deregistration in vnx driver configuration 2. Delete attachment of all volumes on a compute node until it's deregistered by the driver 3. Attempt to re-attach a volume on deregistered compute node. Actual results: ~~~ 2019-02-25 17:11:30.089 10661 ERROR oslo_messaging.rpc.server ImageCopyFailure: Failed to copy image to volume: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: Error: storagegroup command failed 2019-02-25 17:11:30.089 10661 ERROR oslo_messaging.rpc.server The group name or UID does not match any storage groups for this array ~~~ Expected results: It should work
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0929