GitHub user Jayd603 edited a discussion: Agent can't start even if only one KVM VM was using network attached primary storage and that storage becomes unavailable.
In a new 4.22 install I was able to only have local disk primary storage and network attached secondary storage on install. Which should make it possible to still boot machines if there is no primary network attached storage. On a 4.21 cluster with both network attached primary storage and local disk primary storage, the Agents refused to start until network attached primary storage was available and healthy. Even if only a single VM is using that storage, preventing all other VMs from starting. Really only the machines on that missing storage should fail to start, and machines on local disk storage should always be able to boot. Is anyone familiar with the details of this? Did 4.22 fix this? So If I use a mix of primary network attached storage and local disks the agents wont refuse to start all together if network attached primary storage is missing? At some point I will be able to test this myself , I just can't do it yet so I'm seeing if anyone has run into this and already knows the details. Ty! GitHub link: https://github.com/apache/cloudstack/discussions/12168 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
