glance backend tls toggle breaks glance

Bug #1901777 reported by Alexander Diana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Triaged
Low
Unassigned

Bug Description

**Bug Report**

What happened:

Upon testing backend tls, we enabled and disabled tls multiple times, whenever reconfiguring with TLS disabled, the glance service would break.

What you expected to happen:

glance_tls_proxy container should be stopped or removed on tls disabled reconfigure, ensuring the containers don't fight over ports.

glance-tls-proxy.cfg is also not removed in the main haproxy config, which causes constant hammering with https health checks to the reverted to plain port and other fighting.

How to reproduce it:

Reconfigure with tls enabled
Reconfigure with tls disabled
glance will be non-functional, and crash with unable to listen on ip after 30 seconds

**Environment**:
* Kolla-Ansible version: stable/ussuri

Revision history for this message
Mark Goddard (mgoddard) wrote :

I can see how this happens. I'm sure it's not the only issue of this class. From IRC:

one option would be to run the container check even if the service is disabled (but still do the group check). If the container is running but should be disabled, we can stop it.

Changed in kolla-ansible:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Mark Goddard (mgoddard) wrote :

The same will happen with neutron from Victoria.

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

Other bug subscribers

Remote bug watches

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