Bug 1123301
Summary: | Rubygem-staypuft: HA: nova-metadata VIP/listener is missing on port 8775 in haproxy.cfg | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
Component: | openstack-foreman-installer | Assignee: | Jason Guiditta <jguiditt> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 (RHEL 7) | CC: | aberezin, bperkins, cwolfe, dnavale, mburns, morazi, rhos-maint, yeylon |
Target Milestone: | ga | ||
Target Release: | Installer | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-foreman-installer-2.0.20-1.el6ost | Doc Type: | Bug Fix |
Doc Text: |
The nova-metadata parameter was not enabled for HA deployments, so it did not function as expected.
This fix enables service in the haproxy configuration file and binds listener to the correct address. As a result, nova-metadata service runs as expected for a HA deployment.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 18:06:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leonid Natapov
2014-07-25 09:24:32 UTC
Hmm, we have this in the puppet code already, but it is commented out, due to some problem I forget. We can re-enable it and see how it works, maybe it was another havana issue that is no longer relevant. Patch posted: https://github.com/redhat-openstack/astapor/pull/336 openstack-foreman-installer-2.0.20-1.el6ost listen nova-metadata bind 192.168.0.97:8775 mode tcp option tcplog server mac047d7b627d5a.example.com 192.168.0.2:8775 check server mac047d7b685a04.example.com 192.168.0.5:8775 check server mac047d7b61754e.example.com 192.168.0.3:8775 check Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html |