Comment 10 for bug 1775782

We need to reopen this. I couldn't get devstack to start earlier this week (with a cherry-pick of my don-t-use-uwsgi patch) because glance-api kept timing out when stack.sh was checking to see if the API was available. Turns out that the API was being started on the same port as the registry (19191, I had tls-proxy enabled; g-api should be listening on 19292). I think that just telling oslo-config what directory to look in is not specific enough, and it's reading the DEFAULT/bind_port from the wrong file (could be it's reading all the files, and since r > a, the registry setting wins.)

Anyway, using --config-file=/etc/glance/glance-api.conf allowed the API (and devstack) to start correctly. I didn't experiment with using both --config-dir and --donfig-file, and I'm not inclined to. I think we need to use code to find the config-dir that the loaded api.conf is in, and then look for the import.conf there, just like the uwsgi code is doing.

I don't think this is related to the problems being reported in #openstack-infra earlier this week, though they did sound kind of similar ... the difference is that they're using default devstack (which uses uwsgi) and they're apparently only seeing this happen on vexxhost. More info: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2019-04-23.log.html#t2019-04-23T13:28:43