kolla

rabbitmq fail to restart on image update/upgrade

Bug #1521231 reported by Vladislav Belogrudov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Critical
Vladislav Belogrudov
kolla mitaka-3 "mitaka-3"

Bug Description

If one runs upgrade from release 0.1 to 0.2 rabbitmq data container will restart
and will lose cookie. Bootstrap container won't recreate it because the check for
cookie is done before the data container restarts. This results in failure of
rabbitmq start-up.

Vladislav Belogrudov (vlad-belogrudov)
Changed in kolla:
assignee: nobody → Vladislav Belogrudov (vlad-belogrudov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/251434

Changed in kolla:
status: New → In Progress
Revision history for this message
Vladislav Belogrudov (vlad-belogrudov) wrote :

The problem is much more serious because all data containers restart and remove any state. Only in HA environment one can do such update which essentially means host wipe-out-reinstall

Revision history for this message
Steven Dake (sdake) wrote :

Note in the bug description is that the cookie should be recreated - this is not accurate. Once the data container has been created once, it should never be created again.

Changed in kolla:
importance: Undecided → Critical
milestone: none → mitaka-1
Revision history for this message
Vladislav Belogrudov (vlad-belogrudov) wrote :

one could set pull policy to missing in bootstrap tasks to avoid data container restart as workaround

Steven Dake (sdake)
Changed in kolla:
milestone: mitaka-1 → mitaka-2
Steven Dake (sdake)
Changed in kolla:
milestone: mitaka-2 → mitaka-3
Revision history for this message
Steven Dake (sdake) wrote :

This is resolved with the upgrade action in mitaka.

Changed in kolla:
status: In Progress → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla (master)

Change abandoned by Vladislav Belogrudov (<email address hidden>) on branch: master
Review: https://review.openstack.org/251434
Reason: no need

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.