btzq commented on issue #9336: URL: https://github.com/apache/cloudstack/issues/9336#issuecomment-2602438421
Hey @DaanHoogland , More or less similar scenario, but few notes: **"extra VMs were being created (note that this is strange behaviour as no VMs were disguarded as being part of the group)"** - This looks like an issue as well. I think CS should only decide to scale up, if it manages to correctly detect that these VMs are no longer contactable. - There is also a scenario where if CS is not able to detect that the VMs are down, the LB might still send traffic to VMs that may not exist. **starting the stopped VMs these were also expunged one by one normalising the situation.** - In my situation, the VMs that were reconnected under the LB/ASG Group was not down. The host may have disconnected for a minute and reconnected again. Our VMs were still running. - But if we were to play out your scenario, where the VMs were stopped, then yes, i think it is correct to have the VMs automatically scale down on its own once its started. As long as CS recognizes these VMs as still under the ASG Group. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
