Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 886603 - Openstack Installer: packstack should handle both IP addresses and hostnames for all parameters available in its answer file.
Openstack Installer: packstack should handle both IP addresses and hostnames ...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
2.0 (Folsom)
Unspecified Linux
high Severity high
: snapshot3
: 2.1
Assigned To: Martin Magr
Nir Magnezi
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-12 11:29 EST by Nir Magnezi
Modified: 2016-04-26 19:32 EDT (History)
3 users (show)

See Also:
Fixed In Version: openstack-packstack-2012.2.2-0.9.dev406
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-21 14:22:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 21635 None None None Never
Red Hat Product Errata RHSA-2013:0671 normal SHIPPED_LIVE Moderate: openstack-packstack security and bug fix update 2013-03-21 18:22:21 EDT

  None (edit)
Description Nir Magnezi 2012-12-12 11:29:06 EST
Description of problem:
=======================
Packstack should handle both IP addresses and hostnames for all parameters available in it's answer file.
at the moment, not all of them are supported, due to the fact some of them must be converted to ip addresses before using then in the installation / configuration process.


Version-Release number of selected component (if applicable):
=============================================================
Folsom.
packstack version: openstack-packstack-2012.2.2-0.1.dev205.el6ost.noarch


How reproducible:
=================
Always.


Steps to Reproduce:
===================
1. Use packstack to install openstack, use hostnames with the following parameters:
CONFIG_NOVA_API_HOST
CONFIG_NOVA_NETWORK_HOST
MYSQL_HOST
CONFIG_SWIFT_STORAGE_HOSTS

 
Actual results:
===============
1. nova network will fail to start.
2. swift will fail to start.
3. Not sure what is the implication of using MYSQL_HOST with a hostname.


Expected results:
=================
1. nova network and swift should be fully functional.
Comment 2 Derek Higgins 2012-12-14 09:31:38 EST
This is now fixed upstream,

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

packstack now uses ip addresses in all place that were known to cause problems, even if a hostname was configured
Comment 3 Yaniv Kaul 2012-12-14 14:58:10 EST
I would rather it insists on IP address where one is required.
Comment 4 Martin Magr 2012-12-20 07:51:46 EST
The thing what patch above is doing is that if you insert hostname, it will automatically convert it to appropriate IP address and let user know. Is this OK for you Yaniv?
Comment 5 Yaniv Kaul 2012-12-23 12:05:03 EST
(In reply to comment #4)
> The thing what patch above is doing is that if you insert hostname, it will
> automatically convert it to appropriate IP address and let user know. Is
> this OK for you Yaniv?

No - if I've used a hostname, it's because I wanted to be flexible with my IP and not depend on it, rather on the hostname. If you convert transparently, the user will not be aware of it. He might later switch the host to a different IP and things will break.

I think it'd be nice if we allow what is possible today to do with hostname and fail explicitly the rest.
Comment 9 Nir Magnezi 2013-02-27 08:31:44 EST
Verified NVR: openstack-packstack-2012.2.2-1.0.dev408.el6ost.noarch

Verified that ALL[1] parameters can accept hostname as a value.

[1] Aside from SWIFT_* and NOVA_API and NOVA_NETWORK won't accept hostname, which are not able to do so.

Negative Tests:

Configured CONFIG_NOVA_API_HOST with a hostname:

Parameter CONFIG_NOVA_API_HOST failed validation: Given host is not in IP address format: <HOSTNAME>

Additional information:
 * ERROR : Failed handling answer file: Given host is not in IP address format: puma06.scl.lab.tlv.redhat.com
 * Please check log file /var/tmp/packstack/20130227-150555-FLMKaa/openstack-setup.log for more information


Configured CONFIG_NOVA_NETWORK_HOST with a hostname:

Welcome to Installer setup utility
Packstack changed given value  to required value /root/.ssh/id_rsa.pub
Parameter CONFIG_NOVA_NETWORK_HOST failed validation: Given host is not in IP address format: <HOSTNAME>

Additional information:
 * ERROR : Failed handling answer file: Given host is not in IP address format: puma06.scl.lab.tlv.redhat.com
 * Please check log file /var/tmp/packstack/20130227-150731-xpFGJD/openstack-setup.log for more information


Configured CONFIG_SWIFT_PROXY_HOSTS with a hostname:

Welcome to Installer setup utility
Packstack changed given value  to required value /root/.ssh/id_rsa.pub
Parameter CONFIG_SWIFT_PROXY_HOSTS failed validation: Given host is not in IP address format: <HOSTNAME>

Additional information:
 * ERROR : Failed handling answer file: Given host is not in IP address format: puma06.scl.lab.tlv.redhat.com
 * Please check log file /var/tmp/packstack/20130227-150854-a64el8/openstack-setup.log for more information


Configured CONFIG_SWIFT_STORAGE_HOSTS with a hostname:

Welcome to Installer setup utility
Packstack changed given value  to required value /root/.ssh/id_rsa.pub
Parameter CONFIG_SWIFT_STORAGE_HOSTS failed validation: Given host is not in IP address format: <HOSTNAME>

Additional information:
 * ERROR : Failed handling answer file: Given host is not in IP address format: puma06.scl.lab.tlv.redhat.com
 * Please check log file /var/tmp/packstack/20130227-150953-OVoFwx/openstack-setup.log for more information
Comment 12 errata-xmlrpc 2013-03-21 14:22:51 EDT
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/RHSA-2013-0671.html

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