Bug 1120426
Summary: | rubygem-staypuft: HA deployment fails because rabbitmq-server failed to start on one of the hosts, because DNS resolution failed, because the hostname was all numeric | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Omri Hochman <ohochman> |
Component: | rubygem-staypuft | Assignee: | Mike Burns <mburns> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 (RHEL 6) | CC: | ajeain, dnavale, hbrock, mburns |
Target Milestone: | ga | Keywords: | TestOnly |
Target Release: | Installer | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Foreman discovery plugin generated a hostname from the host's MAC address. If the MAC address is all numeric, the resulting host name was all numeric. But all numeric hostnames are a violation of internet protocol and caused the glibc resolver to fail.
As a workaround, change the hostnames of the machines you discover to include at least one non-numeric character and as a result, the DNS resolution succeeds.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 18:05:36 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
Omri Hochman
2014-07-16 22:16:09 UTC
Marked as a known issue. Fix will be to update the discovery plugin to not ever assign an all-numeric hostname. Set known issue, removed blocker and exception, added GA3 flag. hosts should now be prefixed with mac Verified : ruby193-rubygem-staypuft-0.2.2-1.el6ost.noarch Unable to reproduce when using the Workaround: Change the hostnames of your discovered machines to include at least one non-numeric character Result: DNS resolution succeeds 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 |