phsm commented on issue #8055: URL: https://github.com/apache/cloudstack/issues/8055#issuecomment-1768270907
We have tried to reporoduce the bug multiple times under different circumstances. Unfortunately, there's no reliable reproduce scenario so far. Here are our findings: - On big Cloudstack platform that had been running for 10 years: we can reproduce the issue. It takes 20+ minutes for each routervm instance to even appear on the selected hypervisor. If a VPC has many tiers, the amount of time for the routervm to appear becomes too much. In this case a hypervisor fencing mechanism reports to the management server that the VM is missing, and it is turned into "Stopped" state. - On a small but old Cloudstack platform: we can also reproduce the issue: it takes 20+ minutes for each routervm to start. - On smaller platforms, or freshly installed platforms: the issue doesn't exist. We continue our investigation. -- 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]
