Bug 886541 - Can't mix 127.0.0.1 with host ipaddresses
Summary: Can't mix 127.0.0.1 with host ipaddresses
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Martin Magr
QA Contact: Nir Magnezi
URL:
Whiteboard:
: 890841 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-12 14:13 UTC by Derek Higgins
Modified: 2019-09-10 14:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-23 10:35:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 19867 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.