OpenStack Charm Testing

Missing port 9292 for glance, when glance and openstack-dashboard installed on same machine

Bug #1622697 reported by Nell Jerram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Charm Testing
New
Undecided
Unassigned

Bug Description

I have an automated test that deploys https://jujucharms.com/u/project-calico/calico-mitaka-juju2, and in some runs I find that port 9292 is not available on the glance/0 machine, which should be providing the glance API.

'sudo ss -tnlp' shows that there is no server on port 9292. glance-api is listening on 9282.

/etc/haproxy/haproxy.cfg has stanzas for ports 80 and 443 (for openstack-dashboard), but nothing for 9292. If I manually add a stanza for 9292, and 'systemctl reload haproxy', I then get the glance API on 9292 as expected.

I guess this is because of a fight between the openstack-dashboard and glance units both adding their entries to /etc/haproxy/haproxy.cfg...

Revision history for this message
James Page (james-page) wrote :

"I guess this is because of a fight between the openstack-dashboard and glance units both adding their entries to /etc/haproxy/haproxy.cfg..."

Yes - quite correct - we used to have a provider co-location matrix for the charms, but its disappeared from the Ubuntu wiki - I'll see if I can resurrect it somewhere better.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.