Bug 1282927
| Summary: | Default entry in /etc/hostname is 'localhost.localdomain.localdomain' opposed to 'localhost.localdomain' | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Matthews <jmatthew> |
| Component: | Appliance | Assignee: | Nick Carboni <ncarboni> |
| Status: | CLOSED ERRATA | QA Contact: | Jeff Teehan <jteehan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5.0 | CC: | abellott, cpelland, gtanzill, jhardy, jkim, jmatthew, jmontleo, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | 5.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.5.0.12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-08 13:48:14 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1282895 | ||
|
Description
John Matthews
2015-11-17 19:50:07 UTC
What version of RHEV was the appliance deployed on? Was seen with RHEV 3.5.5-0.1.el6ev So it looks like cloudinit was doing something by default to change the hostname. As a first pass I was able to find a workaround on RHEV (3.4) where you can set the hostname at deploy time via the "Advanced Options -> Initial Run -> VM Hostname" box in the "New Virtual Machine" dialog, but this may not be a complete fix because this issue might also exist on other hypervisors. Also, I was able to configure cloudinit to never change the hostname, which fixed this issue, but also rendered the input referenced above at deploy time useless (it now has no effect); because of this I'm going to try to avoid this option for now. I'm still looking into setting a default hostname using cloudinit configuration so we can have the best of both worlds, but that may take a bit longer. If I find a way to do that, is there a desired default host name? Is "localhost.localdomain" what we would want? I'm assuming setting the hostname is one of the first things most people will be doing after they deploy anyway right? New commit detected on ManageIQ/manageiq-appliance/master: https://github.com/ManageIQ/manageiq-appliance/commit/1926c54093577c1c0542eea14dd80b086b9438ce commit 1926c54093577c1c0542eea14dd80b086b9438ce Author: Nick Carboni <ncarboni> AuthorDate: Tue Nov 17 16:02:44 2015 -0500 Commit: Nick Carboni <ncarboni> CommitDate: Thu Nov 19 13:50:01 2015 -0500 Remove cloud-init's ability to change the appliance hostname The altered hostname was not included in /etc/hosts causing us to not be able to resolve it when attempting to run `MiqSockUtil.getFullyQualifiedDomainName` The decision was made to disallow cloud-init from changing the hostname at all as to not conflict with our existing methods of changing the hostname using the appliance_console. https://bugzilla.redhat.com/show_bug.cgi?id=1282927 https://bugzilla.redhat.com/show_bug.cgi?id=1278904 COPY/etc/cloud/cloud.cfg.d/miq_cloud.cfg | 2 ++ 1 file changed, 2 insertions(+) Looks right. Tested on 5.5.0.12 For a menu, please type: appliance_console [root@10-16-6-73 ~]# cat /etc/hostname localhost.localdomain [root@10-16-6-73 ~]# 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. https://access.redhat.com/errata/RHSA-2015:2551 |