cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [cloudstack] DaanHoogland opened a new issue #3741: power sync marks missing VMs as stopped
Date Wed, 04 Dec 2019 10:01:41 GMT
DaanHoogland opened a new issue #3741: power sync marks missing VMs as stopped
   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.
   Out of band migration can cause VMs to be stopped, that shouldn't be.
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
    * Improvement Request
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   New line separated list of affected versions, commit ID for issues on master branch.
   Information about the configuration if relevant, e.g. basic network, advanced networking,
etc.  N/A otherwise
   Information about the environment if relevant, N/A otherwise
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   The issue in the title occurs when an out of band migration takes place, for instance by
a third party DRS system (vmware build in being the culprit in this case).
   The sequence that occurs is such:
   - VM migrates
   - it's old host reports its VMs
   - cloudstack marks the VM stopped
   - the new host reports its VMS
   This is not specific to a hypervisor in its logic so I think it needs a generic solution.
An easy solution is to add a state missing to the fsm for VMs, but that gives extra problems
in cases of HA enabled VMs.
   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 -->
   The issue has a timing facet and as such is hard to replay reliably. As shown in the description.
   <!-- You can also paste links for larger files -->
   <!-- What did you expect to happen when running the steps above? -->
   VM keeps running and re-appears to cloudstack
   <!-- What actually happened? -->
   <!-- Paste verbatim command output between quotes below -->
   VM gets marked as stopped and an abundant StopCommand is send to the hypervisor. In theory
this can be the old and the new hypervisor, depending on timing.

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:

With regards,
Apache Git Services

View raw message