-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
ISSUE TYPE
- Bug Report
- Improvement Request
- Enhancement Request
COMPONENT NAME
API, UI
CLOUDSTACK VERSION
4.16.0
CONFIGURATION
ACS 4.16.0
1 Zone
Cluster A: Two Xenserver 7.0 hosts
Cluster B: Two XCP-NG 8.2 hosts
Each Cluster has each own NFS primary storage
There is a Zone-wide Solidfire Storage
OS / ENVIRONMENT
VM-A1, on Cluster A, has 1 ROOT disk on Solifire storage
VM-B1, on Cluster B, has 1 ROOT disk on Solifire storage
Vol-A created on NFS storage
Vol-B created on NFS storage
SUMMARY
While VM-A1, VM-B1 on RUNNING state:
Attempt to attach Vol-A on VM-A1 throws "Failed to attach volume: Vol-A Unable to find suitable primary storage when creating volume Vol-A
Attempt to attach Vol-B on VM-B1 throws "Failed to attach volume: Vol-B Unable to find suitable primary storage when creating volume Vol-B
While VM-A1, VM-B1 on STOPPED state:
Attempt to attach Vol-A on VM-A1 throws "Failed to attach volume: Vol-A Unable to find suitable primary storage when creating volume Vol-A
Attempt to attach Vol-B on VM-B1 throws "Failed to attach volume: Vol-B Unable to find suitable primary storage when creating volume Vol-B
STEPS TO REPRODUCE
1. Create VM-A1 with ROOT disk on Solidfire storage, on Xenserver cluster
2. Create VM-B1 with ROOT disk on Solidfire storage, on XCP-NG clusters
3. Create Volume on NFS primary storage
4. Attach Volume on VM-A1
5. Attach Volume on VM-B1
EXPECTED RESULTS
Volume should be attached on VM-A1, or VM-B1
ACTUAL RESULTS
While VM-A1, VM-B1 on RUNNING state:
Attempt to attach Vol-A on VM-A1 throws "Failed to attach volume: Vol-A Unable to find suitable primary storage when creating volume Vol-A
Attempt to attach Vol-B on VM-B1 throws "Failed to attach volume: Vol-B Unable to find suitable primary storage when creating volume Vol-B
While VM-A1, VM-B1 on STOPPED state:
Attempt to attach Vol-A on VM-A1 throws "Failed to attach volume: Vol-A Unable to find suitable primary storage when creating volume Vol-A
Attempt to attach Vol-B on VM-B1 throws "Failed to attach volume: Vol-B Unable to find suitable primary storage when creating volume Vol-B