-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
rhos-17.1.9
-
None
-
False
-
-
False
-
?
-
rhos-storage-glance
-
None
-
-
-
-
Important
To Reproduce Steps to reproduce the behavior:
- Change /var/lib/config-data/puppet-generated/glance_api_internal/etc/glance/glance-api.conf on all controller nodes, so Glance API internal will listen on port 9292
- Restart tripleo_glance_api_internal
- Run 10s of requests against Glance API
Some requests are logged in /var/log/containers/glance/api_internal.log, others – in /var/log/containers/glance/api.log
Expected behavior
After restart conflict is reported, glance_api_internal fails to bind to port 9292 because glance_api already listens on it.
Bug impact
Configuration mistakes that force both Glance API services backends to the same port are not reported during deployment and may very weird behavior that is hard to troubleshoot and isolate.
Known workaround
Fix deployment templates, so Glance services will be distributed properly.
Additional context
- sosreports from affected environment are attached to support case