Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When only one host is available and it is put in maintenance, all VMs on it are Stopped. #3707

Closed
anuragaw opened this issue Nov 22, 2019 · 3 comments · Fixed by #4534
Closed

Comments

@anuragaw
Copy link
Contributor

When host is put in maintenance, and it is the only host available, all VMs on it are shutdown. This seems intentional code implementation and needs change.

ISSUE TYPE
  • Improvement Request
COMPONENT NAME

CLOUDSTACK VERSION

CONFIGURATION
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
Go to host on a cluster with single host, or all but one host put into maintenance, errorinmaintenance state. Now put the last host in maintenance.
EXPECTED RESULTS
VMs are not stopped and proper message is displayed. Host should be put to ErrorInMaintenance State.
ACTUAL RESULTS

All VMs are shutdown and host is put to maintenance.


@weizhouapache
Copy link
Member

let's discuss all issues and solutions in #3720

@borisstoyanov
Copy link
Contributor

This is different issue than #3720, this is about a STOP initiated from cloudstack intentionally.

@DaanHoogland
Copy link
Contributor

I don't think this is a finished idea yet, reviewing discussions on #3720. Also it has gone silent.
bhaviour can be defined on the basis of arguments or global settings. work to be done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants