-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bz1123301 nova metadata haproxy #336
Bz1123301 nova metadata haproxy #336
Conversation
Re-enabling is causing the following issue with openstack-status for me. Not sure what the issue is yet.
|
Further debugging:
It looks like metadata_host in /etc/nova/nova.conf needs to be defined to avoid this error (i.e. bind on just the backend_ip instead of 0.0.0.0). |
@jguiditta , I was able to get this PR to work with the addition of this commit: cwolferh@73a342a (the branch it is coming from is https://github.com/cwolferh/astapor/commits/bz1123301_nova-metadata-haproxy_testing) -- so maybe just cherry-pick that commit onto your branch. Note that I called out the wrong config value in my last comment; it is actually metadata_listen, not metadata_host. Tested on nova network and neutron HA controllers, and non-HA nova network controller. |
…aproxy.cfg https://bugzilla.redhat.com/show_bug.cgi?id=1123301 This was already in the puppet, but had been disabled for a previous release. This patch re-enables it to see if it now works as expected.
https://bugzilla.redhat.com/show_bug.cgi?id=1123301 Otherwise openstack-nova-api attempts to listen on 0.0.0.0, causing the error: ERROR nova.wsgi [-] Could not bind to 0.0.0.0:8775 CRITICAL nova [-] error: [Errno 98] Address already in use (cherry picked from commit 73a342a)
@cwolferh pulled in your commit, not sure who should merge it now though... |
Merging with blessing from morazi. |
Bz1123301 nova metadata haproxy
Add listener to haproxy config