hacluster may attempt to start services before the primary charm is ready and does not subsequently restart the service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
There is a possible race for services from primary charms that hacluster manages that require relation data from other charms such as mysql or rabbitmq.
The primary charms may need to wait until they have complete relation data before completing the ha relation.
Specific example seen in the wild:
nova-cloud-
Nova console auth fails to start
2017-03-20 22:12:07.931 162718 ERROR oslo_service.
2017-03-20 22:19:42.682 2524 WARNING oslo_reports.
Corosync then never attempts to restart it.
In this instance the problem is actually https:/ /bugs.launchpad .net/charm- nova-cloud- controller/ +bug/166024
There may be a theoretical race condition possible here but the service should be restarted. I am going to mark this invalid until we see this in the wild unrelated to the nova-consoleauth issue.