AndreaGHG opened a new issue #3664: Instances status out of sync with hypervisor VM's URL: https://github.com/apache/cloudstack/issues/3664 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Cloudstack Manager ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ Cloudstack 4.11.3.0, VMWare 6.5 as hypervisor. ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> 1 Cloudstack management server, 1 dedicated DB server with MariaDB 5.5, 3 node VMWare VSphere 6.5 cluster. Cloudstack advanced networking setup. ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> Management server installed on CentOS 7. ##### SUMMARY <!-- Explain the problem/feature briefly --> Often it happens that Instances status goes out of sync with VMWare virtual machines status. I startup one instance, it boots up correctly and goes to the "Running" state. After some time (hours, days, months, there is not a defined amount of time) it appears in the "Stopped" status on the manager web interface (in the "instances" section) without any user interaction, but if I look in the VSphere interface the virtual machine is still running fine and I can connect to its console. This happens with randomly on instances, both with Windows and Linux VMs. VSphere cluster has DRS enabled, I have tried to turn DRS off but this behavior doesn't change. ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> Setup many instances, turn them on and wait. After an undefined amount of time one or more instances could appears stopped in Cloudstack management web interface but they are still powered on and running for VMWare VSphere. <!-- Paste example playbooks or commands between quotes below --> ~~~ ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ ~~~
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
