FFU: deploy_steps_playbook.yaml playbook fails because rabbitmq_init_bundle container is unable to successfully run Executing: 'rabbitmqctl status | grep -F "{rabbit,"'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
High
|
Unassigned |
Bug Description
Description of problem:
FFU: deploy_
[root@controller-0 ~]# docker logs --tail 10 rabbitmq_
Debug: Executing: 'rabbitmqctl status | grep -F "{rabbit,"'
Debug: /Stage[
Debug: /Stage[
Debug: Exec[rabbitmq-
Debug: Executing: 'rabbitmqctl status | grep -F "{rabbit,"'
Debug: /Stage[
Debug: /Stage[
Debug: Exec[rabbitmq-
Debug: Executing: 'rabbitmqctl status | grep -F "{rabbit,"'
Debug: /Stage[
This step eventually times out. When trying to run the rabbitmqctl status command manually I get:
[root@controller-0 ~]# docker exec -it rabbitmq_
Error: Failed to initialize erlang distribution: {{shutdown,
Version-Release number of selected component (if applicable):
rhosp13/
pacemaker-
resource-
How reproducible:
100%
Steps to Reproduce:
1. Deploy Newton with 1 controller + 1 compute
2. Run through the FFU steps
3. Run deploy_
Actual results:
Playbook eventually times out because rabbitmq_
Expected results:
deploy_
Additional info:
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
status: | Triaged → Invalid |
Acording to the discussion in https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1551397# c6:
"Ok so reason is that when the init_bundle runs the cluster is in maintenance mode:
4 nodes configured
16 resources configured
*** Resource management is DISABLED ***
The cluster will not attempt to start, stop or recover services
Online: [ controller-0 ]
Full list of resources:
ip-172.17.3.17 (ocf::heartbeat :IPaddr2) : Started controller-0 (unmanaged) :IPaddr2) : Started controller-0 (unmanaged) :IPaddr2) : Started controller-0 (unmanaged) :IPaddr2) : Started controller-0 (unmanaged) :IPaddr2) : Started controller-0 (unmanaged) :IPaddr2) : Started controller-0 (unmanaged) mirror- brq.usersys. redhat. com:5000/ rhosp13/ openstack- rabbitmq: pcmklatest] (unmanaged) bundle- 0 (ocf::heartbeat :rabbitmq- cluster) : Stopped (unmanaged) mirror- brq.usersys. redhat. com:5000/ rhosp13/ openstack- mariadb: pcmklatest] (unmanaged) :galera) : Stopped (unmanaged) mirror- brq.usersys. redhat. com:5000/ rhosp13/ openstack- redis:pcmklates t] (unmanaged) :redis) : Stopped (unmanaged) mirror- brq.usersys. redhat. com:5000/ rhosp13/ openstack- haproxy: pcmklatest] (unmanaged) bundle- docker- 0 (ocf::heartbeat :docker) : Stopped (unmanaged)
ip-172.17.4.11 (ocf::heartbeat
ip-172.17.1.15 (ocf::heartbeat
ip-10.0.0.110 (ocf::heartbeat
ip-192.168.24.9 (ocf::heartbeat
ip-172.17.1.12 (ocf::heartbeat
Docker container: rabbitmq-bundle [rhos-qe-
rabbitmq-
Docker container: galera-bundle [rhos-qe-
galera-bundle-0 (ocf::heartbeat
Docker container: redis-bundle [rhos-qe-
redis-bundle-0 (ocf::heartbeat
Docker container: haproxy-bundle [rhos-qe-
haproxy-
So we're actually waiting for rabbitmq bundle to come up but it never will because cluster is in maintenance mode."