Bug 1706992
| Summary: | [OSP13][RFE] Backport - After the compute reboot, the vm on compute state is shut off | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Andreas Karis <akaris> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Martin Schuppert <mschuppe> |
| Status: | CLOSED ERRATA | QA Contact: | Piotr Kopec <pkopec> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | amodi, aschultz, cswanson, djuran, egallen, marjones, mbooth, mburns, ndeevy, sisadoun |
| Target Milestone: | z8 | Keywords: | FutureFeature, Patch, Triaged, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | puppet-nova-12.4.0-22.el7ost puppet-tripleo-8.4.1-22.el7ost openstack-tripleo-heat-templates-8.3.1-66.el7ost | Doc Type: | Enhancement |
| Doc Text: |
With this update, you can now configure automatic restart of instances on a Compute node if the node reboots without migrating the instances. You can configure Nova and the libvirt-guests agent to shut down the instances gracefully and restart them when the Compute node reboots. The following parameters are new in Red Hat OpenStack Platform 13: NovaResumeGuestsStateOnHostBoot (True/False) NovaResumeGuestsShutdownTimeout (default 300s)
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-03 16:55:32 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: | |
| Embargoed: | |||
| Bug Depends On: | 1614282 | ||
| Bug Blocks: | |||
|
Description
Andreas Karis
2019-05-06 15:00:04 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2624 |