weizhouapache commented on issue #8177: URL: https://github.com/apache/cloudstack/issues/8177#issuecomment-1790932959
> After reading the longs for a while longer, I suspect it's related to renaming or destroying a VM, not creating it. > Yes, could be. > At 8:49, a VM has been renamed from "test-ci-12" to "test-ci-12-CDSDEL" (our CI/CD tooling adds a suffix to the VM name prior to deletion, to make the name available for a replacement even before Delete/Expunge/Destroy is complete) Did the CI/CD tool add the suffix by manual db changes or cloudstack API `updatevirtualmachine` ? if the API (https://cloudstack.apache.org/api/apidocs-4.18/apis/updateVirtualMachine.html) is used, cloudstack should update the dns in VRs automatically (see #5425) > At 8:50, the VM has been destroyed (destroyVirtualMachine, expunge=true) At 8:57, the health check message says `"Missing entries for VMs in /etc/hosts -\n10.12.96.9 test-ci-12"`, so it apparently neither has caught up with that rename, nor the destroy. > > That process happens many times, only rarely do we get the Health Check failed email. But with 4.11 it came a few times per year, since upgrading to 4.18, it comes multiple times a week. > The VR health check feature was introduced in cloudstack 4.14 (see #3575 ) > @weizhouapache The management server log from that rename up to the health check is 1.4MB, and cleaning all internal data (VM names, host names, user names, domains, IPs) would most probably make it useless. If you have specific questions, I can look it up though. -- 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]
