borisstoyanov opened a new issue #3719: VMware: SystemVMs not cleared after forcing them to stop URL: https://github.com/apache/cloudstack/issues/3719 <!-- 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 VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> ##### SUMMARY <!-- Explain the problem/feature briefly --> Occupy a host with a few VMs and make sure both system vms are there as well ``` MariaDB [cloud]> select name,state,removed from vm_instance where type = 'SecondaryStorageVm' or type ='ConsoleProxy'; +---------+-----------+---------------------+ | name | state | removed | +---------+-----------+---------------------+ | s-1-VM | Destroyed | 2019-11-21 09:37:59 | | v-2-VM | Destroyed | 2019-11-21 09:48:16 | | s-28-VM | Destroyed | 2019-11-21 09:38:58 | | s-29-VM | Destroyed | 2019-11-21 09:45:29 | | s-30-VM | Destroyed | 2019-11-21 09:46:29 | | s-31-VM | Destroyed | 2019-11-21 09:47:29 | | s-32-VM | Destroyed | 2019-11-21 11:50:29 | | v-33-VM | Destroyed | 2019-11-21 11:44:56 | | v-39-VM | Destroyed | 2019-11-21 11:45:59 | | v-40-VM | Destroyed | 2019-11-21 11:50:29 | | v-41-VM | Running | NULL | | s-42-VM | Destroyed | 2019-11-21 11:51:29 | | s-43-VM | Destroyed | 2019-11-21 11:52:29 | | s-44-VM | Destroyed | 2019-11-21 11:53:29 | | s-45-VM | Destroyed | 2019-11-21 11:54:29 | | s-46-VM | Destroyed | 2019-11-21 11:55:29 | | s-47-VM | Destroyed | 2019-11-21 11:56:29 | | s-48-VM | Running | NULL | +---------+-----------+---------------------+ 18 rows in set (0.00 sec) ```  notice how s-29, s-32, 40 are still part of the list but according to cloudstack DB they are removed ##### 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. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ Make sure the host is the last one in the cluster and set it to maintenance Observe that all VMs are shut down Cancel maintenance and observe new system vms will be created Login to vCenter and see that old system vms are not destroyed ~~~ <!-- 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: us...@infra.apache.org With regards, Apache Git Services
