| Summary: | Upgrade needs update identifier set to prevent down services | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | mathieu bultel <mbultel> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Marios Andreou <mandreou> |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 (Liberty) | CC: | adahms, jslagle, mburns, rhel-osp-director-maint, sclewis, slinaber |
| Target Milestone: | ga | Keywords: | TestOnly |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.14-4.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the final stage of the upgrades process did not ensure that pacemaker cluster resources were being restarted properly. This would cause some resources to remain down after the upgrade was complete. For example, updating the password of the rabbit messaging service as part of an upgrade would mean that you would also need to restart all the services that communicate with this service such as neutron-server, but only after having restarted the rabbit service itself. Now, pacemaker resources are restarted during the final part of the upgrade, and the upgrade completes successfully with all pacemaker resources reported as "Started".
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-20 13:04:27 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: | |
|
Description
mathieu bultel
2016-03-24 14:14:12 UTC
Proposed review : https://review.openstack.org/297175 *** Bug 1320825 has been marked as a duplicate of this bug. *** verified with openstack-tripleo-heat-templates-kilo-0.8.14-7.el7ost.noarch the code is merged from: https://github.com/openstack/tripleo-heat-templates/blob/a12087715f0fe4251a95ab67120023d553c24a45/extraconfig/tasks/pacemaker_resource_restart.sh#L11 to: /usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/pacemaker_resource_restart.sh the upgrade command included major-upgrade-pacemaker-converge.yaml: openstack overcloud deploy --templates /usr/share/openstack-tripleo-heat-templates -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml -e /home/stack/ssl-heat-templates/environments/enable-tls.yaml -e /home/stack/ssl-heat-templates/environments/inject-trust-anchor.yaml -e network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-pacemaker-converge.yaml [heat-admin@overcloud-controller-1 ~]$ openstack-status | grep neutron-server neutron-server: active (disabled on boot) pcs status view: ----------------- Started: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 ] Clone Set: neutron-server-clone [neutron-server] 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://rhn.redhat.com/errata/RHBA-2016-0653.html |