Bug 1417859
Summary: | [RFE] Would like to able to set a hostname based on dns during auto discovery. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | vijsingh |
Component: | Discovery Plugin | Assignee: | Lukas Zapletal <lzap> |
Status: | CLOSED ERRATA | QA Contact: | Perry Gagne <pgagne> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.6 | CC: | bbuckingham, brian.bresina.ctr, cwelton, ehelms, jcallaha, jennifer.power.ctr, lzap, vijsingh |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://projects.theforeman.org/issues/18148 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:54:17 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
vijsingh
2017-01-31 10:29:52 UTC
Hello, we are tracking similar request to simply send DHCP "hostname" along with other facts and also DNS PTR name associated with a (static) IP. Any of the two new facts can be then used for discovered hostname instead of the default "macXXXX". Will this work for the user? Can you confirm? Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18148 has been resolved. This bug is scheduled for Satellite 6.3 as you can see in the flag: pm-rhel=sat-6.3.0. Since this is a new feature, it is not a candidate for backport into 6.2. QA notes, scenario A: use DHCP advertised hostname as discovered node name. - Setup DHCP server to have longer lease (6 hours for testing) - Restart DHCP server - Create a VM, install OS manualy, give it a hostname "mytest" - Reboot the system via DHCP and make sure the lease contains hostname option - Set "Hostname facts" to [nmprimary_dhcp4_option_host_name, discovery_bootif] (this is array of two options) - Set "Discovery prefix" to "xxx_" - Reboot the system into discovery while keeping the MAC address - The DHCP server advertise hostname "mytest" (from the lease) - The host should appear as "xxx_mytest" - Whole test scenario must be done within 6 hours QA notes, scenario B: use DHCP advertised hostname as provisioned system hostname. - Configure DHCP and install/boot a named OS with "myhost" hostname as in scenario A - Revert "Hostname facts" to default value - Revert "Discovery prefix" to default value - Reboot the system into discovery - The host should appear as "macAABBCCDDEEFF" (normally) - Create a discovery rule with some valid hostgroup that always matches - - Set hostname to: xxx_<%= @host.facts['nmprimary_dhcp4_option_host_name'] %> - Provision the discovered host via Auto provision - The provisioned system should be named: xxx_myhost Note both scenarios will only work when DHCP hostnames are unique. This is quite special Satellite 6 setup, I don't expect many customers to have this kind of setup. 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-2018:0336
|