[yoga] nova-cloud-controller units stuck waiting: Incomplete relations: messaging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack RabbitMQ Server Charm |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
In testrun:
https:/
The ncc units are stuck waiting:
```
nova-cloud-
filebeat/51 active idle 10.246.167.175 Filebeat ready.
hacluster-
landscape-
logrotated/45 active idle 10.246.167.175 Unit is ready.
nova-
nrpe/51 active idle 10.246.167.175 icmp,5666/tcp Ready
public-
telegraf/51 active idle 10.246.167.175 9103/tcp Monitoring nova-cloud-
```
In the logs we see:
```
var/log/
var/log/
var/log/
```
However, the rabbitmq units themselves show that they are happy. We know that the relations are getting rendered because of the juju-show-unit output that is in the crashdump.
Pausing and resume the ncc units does not help, suggesting that its not a race condition.
Link to crashdumps etc:
https:/
List of occurrences of this bug:
https:/
description: | updated |
summary: |
- [yoga-edge] nova-cloud-controller units stuck waiting: Incomplete - relations: messaging + [yoga] nova-cloud-controller units stuck waiting: Incomplete relations: + messaging |
tags: | added: cdo-qa foundations-engine |
Moving over to rabbitmq-server as upon inspection of the juju status, many of the related services are waiting on an incomplete messaging relation. A quick perusal suggests this may be related to not creating users after the service is clustered.