Bug 1551265 - OSP11 -> OSP12 upgrade: major upgrade composable step fails because rabbitmq_init_bundle container fails to start on 2/3 controllers
Summary: OSP11 -> OSP12 upgrade: major upgrade composable step fails because rabbitmq_...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z2
: 12.0 (Pike)
Assignee: Michele Baldessari
QA Contact: Marius Cornea
URL:
Whiteboard:
: 1550589 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-04 05:33 UTC by Marius Cornea
Modified: 2018-03-28 17:33 UTC (History)
13 users (show)

Fixed In Version: puppet-tripleo-7.4.8-5.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-28 17:32:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 550743 0 None MERGED Fix stack update with rabbitmq containers 2021-01-25 00:27:07 UTC
Red Hat Product Errata RHBA-2018:0607 0 None None None 2018-03-28 17:33:08 UTC

Description Marius Cornea 2018-03-04 05:33:36 UTC 
Description of problem:
OSP11 -> OSP12 upgrade: major upgrade composable step fails because rabbitmq_init_bundle container fails to start on 2/3 controllers. We can see in the rabbitmq_init_bundle containerthat the '/usr/sbin/rabbitmqctl -q list_users' command fails on controller-1 and controller-2. The command succeeds on the container on controller-1.

Version-Release number of selected component (if applicable):
container image: openstack-rabbitmq:12.0-20180222.1 

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP11 with 3 controllers + 1 compute
2. Upgrade tot OSP12

Actual results:
The major-upgrade-composable-steps-docker.yaml step fails because rabbitmq_init_bundle container gets sutccessfuly started only on the first controller. 

Expected results:
Upgrade succeeds.

Additional info:
The same issue has been observed during fast forward upgrade when upgrading to OSP13 in BZ#1547589
Comment 7 John Eckersberg 2018-03-19 14:58:55 UTC 
*** Bug 1550589 has been marked as a duplicate of this bug. ***
Comment 12 errata-xmlrpc 2018-03-28 17:32:48 UTC 
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-2018:0607
Note You need to log in before you can comment on or make changes to this bug.