Bug 1367126
Summary: | [RFE] upload FQDN with facts | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Justin Sherrill <jsherril> | |
Component: | subscription-manager | Assignee: | Kevin Howell <khowell> | |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> | |
Severity: | low | Docs Contact: | ||
Priority: | high | |||
Version: | 7.2 | CC: | ahumbe, aperotti, csnyder, khowell, redakkan, skallesh | |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged | |
Target Release: | 7.4 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1367128 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 19:18:42 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: | 1367128, 1395274 |
Description
Justin Sherrill
2016-08-15 15:46:37 UTC
Retested on ; subscription management server: 0.9.51.21-1 subscription management rules: 5.15.1 subscription-manager: 1.19.8-1.el7 python-rhsm: 1.19.5-1.el7 The test system is configured to have a short hostname along with FQDN # hostname bkr-hv03-guest06.dsal.lab.eng.bos.redhat.com # hostname -s bkr-hv03-guest06 # hostname -f bkr-hv03-guest06.dsal.lab.eng.bos.redhat.com Now verify the fact value of network.fqdn, # subscription-manager facts --list | grep fqdn network.fqdn: bkr-hv03-guest06.dsal.lab.eng.bos.redhat.com # subscription-manager facts --list | grep network network.fqdn: bkr-hv03-guest06.dsal.lab.eng.bos.redhat.com network.hostname: bkr-hv03-guest06.dsal.lab.eng.bos.redhat.com Observed that now fqdn fact value is collected along with the already existing fact network.hostname. Marking 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-2017:2083 |