GitHub user Jayd603 added a comment to the discussion: Agent can't start even if only one KVM VM was using network attached primary storage and that storage becomes unavailable.
> @Jayd603 , if the vm is already deployed (has run before) I would indeed > expect it to start if no nas is available. If not at least a copy from > secondary to primary should be possible, i.e. secondary should be available > to the host. > > do you have logging or stack traces available to have a look? > > I do not know of any fix that would change the behaviour between 21 and 22. > Maybe @slavkap, @harikrishna-patnala , @sureshanaparti or @rp- is aware? I don't have any further logs/details yet, this happened on a cluster that had lost power where most of the VMs were on local disk storage. The management server and all hosts were brought up fine but then agents refused to start until the primary (but barely used) NAS storage was brought up. This led me to realize the potential weakness. I think the management server had everything needed to bring up the instances that were on local disks but that wasn't possible because the agent's refused to start. On my my recent cluster I was able to install without any primary NAS storage at all, just local disks and secondary NFS storage. Now if I want to add some shared primary storage to the cluster, seems like it could prevent the agents from starting on all hosts even if I used it for storage on just one instance. GitHub link: https://github.com/apache/cloudstack/discussions/12168#discussioncomment-15136186 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
