weizhouapache commented on issue #11764: URL: https://github.com/apache/cloudstack/issues/11764#issuecomment-3356854005
> [@weizhouapache](https://github.com/weizhouapache), in my case I have one NFS cluster-wide, 1 NFS zone-wide and 2 StorPool zone-wide pools, and the VMs are stopped. After that it cannot find pool with the matching tag to start the VM. The SQL query is looking for pools with status=Up and matching tags > > > 25-10-01 11:59:37,982 TRACE [c.c.u.d.T.Statement] (Work-Job-Executor-12:[ctx-5a4edfb7, job-5470/job-5471, ctx-16d60488]) (logid:0c10c265) Preparing: SELECT storage_pool.* from storage_pool LEFT JOIN storage_pool_tags ON storage_pool.id = storage_pool_tags.pool_id WHERE storage_pool.removed is null and storage_pool.status = 'Up' AND storage_pool_tags.is_tag_a_rule = 0 and storage_pool.data_center_id = ? and (storage_pool.pod_id = ? or storage_pool.pod_id is null) and storage_pool.scope = ? and (storage_pool.cluster_id = ? OR storage_pool.cluster_id IS NULL) AND ((storage_pool_tags.tag='nfs-cluster1')) GROUP BY storage_pool_tags.pool_id HAVING COUNT(storage_pool_tags.tag) >= ? > > > maybe we should mark the storage as Up at first, then start the vms which are stopped when enable storage maintenance. > > I agree with this one ^^ @slavkap @nvazquez I just found that the behavior on storpool pools is same as it when cancel storage migration ..... https://github.com/apache/cloudstack/blob/cd12fa584825889692d88d909132d684b6c6c778/plugins/storage/volume/storpool/src/main/java/org/apache/cloudstack/storage/datastore/lifecycle/StorPoolPrimaryDataStoreLifeCycle.java#L238-L245 created a draft PR: https://github.com/apache/cloudstack/pull/11773 -- 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]
