Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 886541

Summary: Can't mix 127.0.0.1 with host ipaddresses
Product: Red Hat OpenStack Reporter: Derek Higgins <derekh>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED WONTFIX QA Contact: Nir Magnezi <nmagnezi>
Severity: high Docs Contact:
Priority: high    
Version: 2.0 (Folsom)CC: aortega, ykaul
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-23 10:35:44 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 Derek Higgins 2012-12-12 14:13:15 UTC 
When configuring packstack, and installing on localhost along with other servers you can't use 127.0.0.1 along with external ipaddress(for the other servers)

the resulting openstack deployment doesn't work because some services are configured to point to 127.0.0.1 when they shouldn't be

e.g.
CONFIG_MYSQL_HOST=127.0.01
CONFIG_NOVA_COMPUTE_HOSTS=192.168.0.47
would result in a compute nodes that is pointing to itself for the db
sql_connection=mysql://nova:nova_default_password.0.1/nova

packstack should probably refuse to do this or attempt to convert 127.0.0.1 to a external ipaddress.
Comment 2 Derek Higgins 2012-12-14 14:30:20 UTC 
This is now fixed upstream

https://github.com/fedora-openstack/packstack/commit/713d1f4350d95b5eb145e51cd0d3bd325bf2ce17

packstack now refuses to run if the loopback and real network addresses are mixed
Comment 3 Derek Higgins 2013-01-16 22:41:02 UTC 
Another patch to change packstack to no longer default to 127.0.0.1
https://review.openstack.org/#/c/19867/

this will prevent this problem occurring
Comment 5 Derek Higgins 2013-01-19 09:28:23 UTC 
*** Bug 890841 has been marked as a duplicate of this bug. ***
Comment 7 Derek Higgins 2013-01-23 10:35:44 UTC 
Closing as wont fix, the commit in comment 5 ensures the default is no longer 127.0.0.1 

This should prevent this situation from occurring, anybody who changes it back to a loopback address should be considered an advanced user and should be aware of the situation that can occur if done incorrectly.