Bug 1463325
Summary: | [RFE] Request for the Subscription manager to display the hostname it is registering as part of its output | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Prathamesh Chavan <prchavan> |
Component: | subscription-manager | Assignee: | Kevin Howell <khowell> |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
Severity: | medium | Docs Contact: | Filip Hanzelka <fhanzelk> |
Priority: | unspecified | ||
Version: | 7.3 | CC: | bbuckingham, fhanzelk, jcallaha, jhnidek, jsefler, khowell, prchavan, redakkan, rjerrido, skallesh |
Target Milestone: | pre-dev-freeze | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | subscription-manager-1.20.2-1 | Doc Type: | Release Note |
Doc Text: |
*subscription-manager* now displays the host name upon registration
Until now, the user needed to search for the effective host name for a given system, which is determined by different Satellite settings. With this update, the *subscription-manager* utility displays the host name upon the registration of the system.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 09:49:52 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
Prathamesh Chavan
2017-06-20 15:09:31 UTC
Moving to RHEL since that's where subscription-manager packages are released. Hello, It would be great if you could share the status of this bug. Thanks! Regards, Prathamesh Verifying on RHEL75 with following build: ======================================= subscription-manager-rhsm-certificates-1.20.5-1.el7.x86_64 subscription-manager-gui-1.20.5-1.el7.x86_64 subscription-manager-rhsm-1.20.5-1.el7.x86_64 subscription-manager-1.20.5-1.el7.x86_64 subscription-manager-initial-setup-addon-1.20.5-1.el7.x86_64 subscription-manager-plugin-container-1.20.5-1.el7.x86_64 1) Verifying the system's hostname is used to report "The registered system name" [root@dhcp35-157 ~]# hostname --fqdn dhcp35-157.lab.eng.blr.redhat.com [root@dhcp35-157 ~]# subscription-manager register Registering to: F21-candlepin.usersys.redhat.com:8443/candlepin Username: admin Password: Organization: admin The system has been registered with ID: 5cec7b0d-ba5d-4b9e-9cf9-4e9924f2a6f2 The registered system name is: dhcp35-157.lab.eng.blr.redhat.com ^^ observed that hostname matches "the registered system name " 2) Verifying that even with overrid'ed hostname facts value, subscription-manager register continues to use the system hostname [root@dhcp35-157 ~]# cat /etc/rhsm/facts/hostname.facts {"network.hostname":"testing-an-overridden-hostname-fact.redhat.com"} [root@dhcp35-157 ~]# subscription-manager facts --list | grep hostname network.hostname: testing-an-overridden-hostname-fact.redhat.com [root@dhcp35-157 ~]# hostname dhcp35-157.lab.eng.blr.redhat.com [root@dhcp35-157 ~]# subscription-manager register --username=admin --password=admin --org=admin Registering to: F21-candlepin.usersys.redhat.com:8443/candlepin The system has been registered with ID: 5966712c-c04d-4df0-8a66-59825d0d502f The registered system name is: dhcp35-157.lab.eng.blr.redhat.com ^^ observed that hostname continues to match "the registered system name " 3)Verify that when "--name" value given during registration , the provided name will be written to the terminal instead of hostname [root@dhcp35-157 ~]# subscription-manager register --username=admin --password=admin --org=admin --name=Verify1463325 Registering to: F21-candlepin.usersys.redhat.com:8443/candlepin The system has been registered with ID: 170f57d9-855c-4d78-bd00-f683bc8f6e7c The registered system name is: Verify1463325 --> matches the value provided in the register command [root@dhcp35-157 ~]# hostname dhcp35-157.lab.eng.blr.redhat.com Based on the above observations , marking the bug as "Verified" 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/RHBA-2018:0681 |