weizhouapache commented on PR #13611: URL: https://github.com/apache/cloudstack/pull/13611#issuecomment-5570223925
The issue can be reproduced with both CLUSTER-scope and ZONE-scope storage pools using the following steps: - Stop cloudstack-agent on the KVM host. - Manually set its status to Up in the database. - Create a volume. - Attach the volume to a VM. - The operation fails, but pool_id is still set. - Start cloudstack-agent again. - Attaching the volume to a VM fails with Unable to find suitable primary storage when creating volume. This also happens with CLUSTER-scope storage pools, as pod_id is always NULL in my environment. I verified that the fix correctly cleans up the pool_id of the Allocated volume, and the volume can then be attached to a VM successfully. cc @DaanHoogland could you please review ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
