Back to bug 1320567

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-23 14:04:49 UTC Target Release --- 8.0
Marios Andreou 2016-03-23 14:05:30 UTC Assignee jstransk mandreou
Marios Andreou 2016-03-23 17:24:14 UTC Link ID OpenStack gerrit 296491
Marios Andreou 2016-03-23 17:24:45 UTC Link ID Launchpad 1561012
Jaromir Coufal 2016-03-23 19:53:55 UTC CC jcoufal
James Slagle 2016-03-24 00:00:05 UTC Status NEW ON_DEV
CC jslagle
James Slagle 2016-03-28 11:05:36 UTC Status ON_DEV POST
Link ID OpenStack gerrit 297288
James Slagle 2016-03-28 15:57:15 UTC Status POST MODIFIED
Fixed In Version openstack-tripleo-heat-templates-0.8.14-1.el7ost
errata-xmlrpc 2016-03-29 14:39:12 UTC Status MODIFIED ON_QA
Arik Chernetsky 2016-03-30 07:38:25 UTC QA Contact achernet ohochman
Marius Cornea 2016-03-31 12:22:12 UTC Status ON_QA ASSIGNED
CC mcornea
Marius Cornea 2016-03-31 13:01:49 UTC Status ASSIGNED ON_QA
Scott Lewis 2016-04-05 12:37:45 UTC Target Milestone --- ga
Mike Burns 2016-04-06 18:58:18 UTC Keywords TestOnly
Mike Burns 2016-04-06 19:16:12 UTC Keywords TestOnly
Marios Andreou 2016-04-13 13:50:06 UTC Doc Text Cause: The final stage of the upgrades process wasn't ensuring that pacemaker cluster resources were being restarted properly, in this case haproxy in particular.

Consequence: The haproxy service wasn't restarted after the new 'upgrade' configuration was applied to all nodes. This caused a problem for the glance service which was unavailable (not listening on its configured port) as a result with and returning a "500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500)" for cli operations such as 'glance image-list'

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. Overcloud glance and all other services are available as expected.
Marios Andreou 2016-04-13 13:58:03 UTC Link ID OpenStack gerrit 297175
Marios Andreou 2016-04-13 14:02:44 UTC Doc Text Cause: The final stage of the upgrades process wasn't ensuring that pacemaker cluster resources were being restarted properly, in this case haproxy in particular.

Consequence: The haproxy service wasn't restarted after the new 'upgrade' configuration was applied to all nodes. This caused a problem for the glance service which was unavailable (not listening on its configured port) as a result with and returning a "500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500)" for cli operations such as 'glance image-list'

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. Overcloud glance and all other services are available as expected.
Cause: The final stage of the upgrades process wasn't ensuring that pacemaker cluster resources were being restarted properly, in this case haproxy in particular.

Consequence: The haproxy service wasn't restarted after the new 'upgrade' configuration was applied to all nodes. This caused a problem for the glance service which was unavailable (not listening on its configured port) as a result and returning a "500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500)" for cli operations such as 'glance image-list'

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. Overcloud glance and all other services are available as expected.
Mike Burns 2016-04-13 16:46:58 UTC Keywords TestOnly
Omri Hochman 2016-04-18 18:37:07 UTC Status ON_QA VERIFIED
Mike Burns 2016-04-20 11:22:02 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2016-04-20 07:22:02 UTC

Back to bug 1320567