Repository navigation
Cloudstack assigns Volume to wrong host #11828
Description
Problem:
- Deploy Instances with terraform
- Cloudstack creates Instances and Volumes
- Volumes were mapped to wrong host, even to hosts of different cluster ( Primary Storage is set to cluster scope)
Setup:
CloudStack 4.21.0
OS: Rocky Linux 9.6
Hypervisor: KVM/QEMU
Primary Storage: Powerflex 4.6.1.0 (715)
Secondary Storage: NFS
Infrastruce-Setup:
1 Zone
2 Pods with 1 Cluster each
4 Hosts in each Cluster
example:
Currently, a working state can occasionally be achieved with very frequent deployment runs.
Most of the time, the mapping is not executed correctly.
Metadata
Metadata
Assignees
Labels
No labels
Activity
boring-cyborg commentedon Oct 13, 2025
Thanks for opening your first issue here! Be sure to follow the issue template!
HeinzM commentedon Oct 13, 2025
We created a new Deployment.
VR with ID 330
Instance 1 with ID 329
and Instance 2 with ID 331.
The Volumes are named correctly in CloudStack.
but in Powerflex the following volumes appear:
HeinzM commentedon Oct 13, 2025
Is there any connection with the missing host_ip entries in the database?
sureshanaparti commentedon Oct 13, 2025
Hi @HeinzM There is no connection with the host_ip entries for the PowerFlex volumes. Are the PowerFlex storage pools (i.e. primary storages with cluster scope) added in each CloudStack cluster belongs to same or different PowerFlex storage cluster?
pool_id column in cloud.volumes table maps to the current storage pool of the volume, and storage host details are in cloud.storage_pool table. Can you query with the following sql:
SELECT vol.name, vol.pool_id, vol.last_pool_id, vol.instance_id, vol.device_id, vol.size, vol.path, pool.name AS pool_name, pool.cluster_id AS pool_cluster_id, pool.host_address AS pool_host_address, pool.path AS pool_path FROM cloud.volumes vol JOIN cloud.storage_pool pool ON vol.pool_id = pool.id WHERE vol.instance_id IN (329, 330, 331);HeinzM commentedon Oct 13, 2025
Hello @sureshanaparti,
there is one specific storage system per cluster. cluster 1 gets powerflex system 1 and cluster 2 gets powerflex system 2.
The pfx systems are individual clusters
The query gets the following result:
sureshanaparti commentedon Oct 13, 2025
@HeinzM I don't issue any issue with storage pool host assignment for all these volumes. If your concern is regarding the host_ip column in cloud.volumes table, it is not applicable for PowerFlex volumes. The PowerFlex volume mapping is based on the host_id column in the vm_instance table (for the volumes attached to the instance, check instance_id column in the cloud.volumes table).
HeinzM commentedon Oct 13, 2025
I'm confused right now. I expected that the volume name in cloudstack matches the volume descriptor in powerflex.
sureshanaparti commentedon Oct 13, 2025
@HeinzM You can check the volume naming conventions here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158873968#PowerFlex/ScaleIOstorageplugin-NamingconventionsforScaleIOvolumes
sureshanaparti commentedon Oct 14, 2025
@HeinzM Is it clear now? Are you looking for any other information?