| Summary: | [RFE] Nova should try to stop instances gracefully | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ondrej <ochalups> |
| Component: | openstack-nova | Assignee: | Eoghan Glynn <eglynn> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Prasanth Anbalagan <panbalag> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.0 (Liberty) | CC: | berrange, dasmith, ealcaniz, eglynn, kchamart, rcernin, sbauza, sferdjao, sgordon, srevivo, vromanso |
| Target Milestone: | async | Keywords: | FutureFeature |
| Target Release: | --- | Flags: | rcernin:
needinfo?
(eglynn) |
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-27 17:43:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
(In reply to Stephen Gordon from comment #2) > Related: https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown This was implemented some releases ago now, and attempts to perform a graceful shutdown by default, are you sure the issue isn't that the guests in question take a long time to shutdown and as a result are forced off after the timeout expires? The default timeout is 60 seconds as defined by the shutdown_timeout config setting. It can also be set per guest using the image_os_shutdown_timeout image property. This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. |
Description of problem: Hello, When executing a "nova stop" command, instances do not have the option to graceful shutdown the OS. For some instances (Windows mostly), this behavior is causing many problems. Is there any option to implement a new feature to have both options: 1- Nova stop --> should try a graceful shutdown (maybe a --timeout parameter or nova stop-soft?) 2-Nova force stop --> current behavior This is an important feature because many instances has been affected. In customer upgrade procedure admins are stopping all instances performing a "nova stop" command. When we start instances again, some of them (Windows mostly) are corrupted. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Being able to gracefully shut the os down with nova stop Additional info: