Back to bug 1321036

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-24 14:14:16 UTC Target Release --- 8.0
mathieu bultel 2016-03-24 14:14:33 UTC Target Release 8.0 ---
Mike Burns 2016-03-24 14:27:24 UTC Status NEW ON_DEV
Link ID OpenStack gerrit 297175
Mike Burns 2016-03-24 14:28:15 UTC CC slinaber
James Slagle 2016-03-28 11:07:16 UTC CC jslagle
Assignee jstransk mandreou
James Slagle 2016-03-30 14:09:02 UTC Status ON_DEV POST
Mike Burns 2016-03-31 18:42:12 UTC Status POST MODIFIED
Fixed In Version openstack-tripleo-heat-templates-0.8.14-4.el7ost
errata-xmlrpc 2016-04-01 20:03:20 UTC Status MODIFIED ON_QA
Scott Lewis 2016-04-05 12:38:00 UTC Target Milestone --- ga
Scott Lewis 2016-04-05 12:39:14 UTC Target Release --- 8.0
CC sclewis
Mike Burns 2016-04-06 18:58:18 UTC Keywords TestOnly
Mike Burns 2016-04-06 19:16:12 UTC Keywords TestOnly
Arik Chernetsky 2016-04-10 07:04:17 UTC QA Contact achernet ohochman
Marios Andreou 2016-04-13 11:36:41 UTC Doc Text Cause: The final stage of the upgrades process wasn't ensuring that pacemaker cluster resources were being restarted properly.

Consequence: This caused some resources to remain down after the upgrade was completed; for example updating the password of the rabbit messaging service as part of an ugrade means you would also need to restart all the services that talk to it (such as neutron-server for instance), but only after having restarted rabbit itself.

Fix: Setting the UpdateIdentifier in the environment file used for the final stage of the upgrades process causes the pacemaker resources to be restarted after the new configuration has been applied, at https://github.com/openstack/tripleo-heat-templates/blob/a12087715f0fe4251a95ab67120023d553c24a45/extraconfig/tasks/pacemaker_resource_restart.sh#L11

Result: The pacemaker resources are restarted during the final part of the upgrade and the upgrade completes successfully with all pacemaker resources reported to be "Started"
Mike Burns 2016-04-13 16:46:58 UTC Keywords TestOnly
Omri Hochman 2016-04-15 20:29:48 UTC Status ON_QA VERIFIED
Andrew Dahms 2016-04-19 00:34:08 UTC CC adahms
Doc Text Cause: The final stage of the upgrades process wasn't ensuring that pacemaker cluster resources were being restarted properly.

Consequence: This caused some resources to remain down after the upgrade was completed; for example updating the password of the rabbit messaging service as part of an ugrade means you would also need to restart all the services that talk to it (such as neutron-server for instance), but only after having restarted rabbit itself.

Fix: Setting the UpdateIdentifier in the environment file used for the final stage of the upgrades process causes the pacemaker resources to be restarted after the new configuration has been applied, at https://github.com/openstack/tripleo-heat-templates/blob/a12087715f0fe4251a95ab67120023d553c24a45/extraconfig/tasks/pacemaker_resource_restart.sh#L11

Result: The pacemaker resources are restarted during the final part of the upgrade and the upgrade completes successfully with all pacemaker resources reported to be "Started"
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".
errata-xmlrpc 2016-04-20 00:29:36 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-20 13:04:27 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-20 09:04:27 UTC

Back to bug 1321036