HA Proxy not able to start in H.2 due to Apache listening on 0.0.0.0

Bug #1307537 reported by Sameer Azad
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Cisco Openstack
Status tracked in Icehouse
Havana
Fix Released
High
Pradeep Kilambi
Icehouse
Fix Released
High
Pradeep Kilambi

Bug Description

HA Proxy Service not able to start in H.2 Compressed HA Install due to Apache listening on 0.0.0.0:80 instead of the Server Physical IP:80.

Scenario: H.2 Compressed HA Install

We are also not able to manually start HA Proxy service as it gets a bind exception due to Apache listening on the all ip address of 0.0.0.0.

We have run puppet apply multiple times and still see the issue.

The workaround for now is to manually modify the /etc/apache2/ports.conf file to replace 0.0.0.0 with the host IP and restart the Apache service on the controller node after every puppet run and disable puppet agent after install.

Changed in openstack-cisco:
milestone: none → h.3
Revision history for this message
Ken Schroeder (kschroed) wrote :

Add horizon::bind_address: "%{ipaddress_eth0}" to hiera_data/user.compressed_ha.yaml fixes this issue.

Revision history for this message
Ken Schroeder (kschroed) wrote :

More appropriately proper fix is likely adding an entry in data_mappings/enable_ha/true.yaml
bind_address:
   - horizon::bind_address

Revision history for this message
Pradeep Kilambi (pkilambi) wrote :
Changed in openstack-cisco:
status: Fix Committed → Fix Released
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.