Deployment of Keystone cluster often fails due to haproxy service not listening on ports that it should
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
Medium
|
Frode Nordahl | ||
keystone (Juju Charms Collection) |
Invalid
|
Medium
|
Frode Nordahl |
Bug Description
$ juju status --format=tabular
keystone/0 active idle 1.25.8 188 5000/tcp 10.5.14.180 Unit is ready
keystone/1 blocked idle 1.25.8 189 5000/tcp 10.5.14.181 Services not running that should be: haproxy; Ports which should be open, but are not: 5000, 35357
keystone/2 blocked idle 1.25.8 190 5000/tcp 10.5.14.182 Services not running that should be: haproxy; Ports which should be open, but are not: 5000, 35357
Log excerpt from working node /var/log/
2016-12-08 10:33:49 INFO juju-log shared-db:332: Wrote template /etc/haproxy/
2016-12-08 10:33:54 INFO shared-
2016-12-08 10:36:32 INFO juju-log Registered config file: /etc/haproxy/
Log excerpt from non-working node /var/log/
2016-12-08 10:34:02 INFO juju-log Wrote template /etc/haproxy/
2016-12-08 10:34:02 INFO leader-
On both nodes there are various log messages with this error:
error: no relation id specified
This might be related to haproxy steps (install, leader-
Changed in keystone (Juju Charms Collection): | |
assignee: | nobody → Frode Nordahl (fnordahl) |
tags: | added: openstack sts |
summary: |
Deployment of Keystone cluster often fails due to haproxy service not - being started + listening on ports that it should |
Changed in charm-keystone: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
importance: | Undecided → Medium |
Changed in keystone (Juju Charms Collection): | |
status: | New → Invalid |
Changed in charm-keystone: | |
milestone: | none → 17.08 |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
No log evidence as of why haproxy does not start.