Bug 1280011
Summary: | Overcloud update fails due to nova-consoleauth service restart failure | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jiri Stransky <jstransk> |
Component: | rhosp-director | Assignee: | Jiri Stransky <jstransk> |
Status: | CLOSED ERRATA | QA Contact: | Gabriel Szasz <gszasz> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | calfonso, jslagle, kbasil, mburns, mcornea, ohochman, rhel-osp-director-maint |
Target Milestone: | y2 | Keywords: | TestOnly, Triaged |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Note: the doc text is the same as for BZ 1275986, i don't think we want to release this text twice, so i'm setting requires_doc_text-.
Cause: Pacemaker prevented Puppet from restarting services during overcloud update.
Consequence: Puppet run failed, which caused overcloud update to fail.
Fix: Pacemaker is put into maintenance mode for the duration of Puppet run during the overcloud update.
Result: Puppet is allowed to restart services, and it doesn't cause the overcloud update to fail anymore.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-21 16:58:24 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: |
Description
Jiri Stransky
2015-11-10 17:41:51 UTC
jistr, assigning this one to you as I think it will be fixed under the larger umbrella of fixing pacemaker/puppet service restart issues I did several updates for both 7.0 -> 7.2 and 7.1 -> 7.2 and I didn't hit the issue reported here so I will move this to verified. This bug is almost same issue as bug 1275986. The use case has been already covered by Marius (see Comment 3). 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-2015:2651 |