Bug 1402103

Summary:	[RFE] upload all FQDN with facts
Product:	Red Hat Enterprise Linux 7	Reporter:	John Sefler <jsefler>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	jsherril, khowell, redakkan, skallesh, wpoteat
Target Milestone:	pre-dev-freeze	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:29:01 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 John Sefler 2016-12-06 19:30:41 UTC

Description of problem:
Opening this RFE because I don't believe that RFE bug 1367128 is sufficient when the system is configured with different fqdn values across both ipv4 and ipv6 configurations.  As reported in bug 1401394, the fact for "network.fqdn" could be an ipv6 value even though hostname reports an ipv4 value.

For more background info, see https://bugzilla.redhat.com/show_bug.cgi?id=1401394#c2


Version-Release number of selected component (if applicable):
[root@ibm-z-24 ~]# rpm -q subscription-manager python-rhsm python
subscription-manager-1.18.5-1.el6.s390x
python-rhsm-1.18.5-1.el6.s390x
python-2.6.6-66.el6_8.s390x


How reproducible:


Steps to Reproduce:
On the following machine from beaker, we see that "hostname --fqdn" and fact "network.fqdn" do not match. 
https://beaker.engineering.redhat.com/view/ibm-z-24.rhts.eng.bos.redhat.com

**  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **
                 This System is reserved by redakkan.

 To return this system early. You can run the command: return2beaker.sh
  Ensure you have your logs off the system before returning to Beaker

 To extend your reservation time. You can run the command:
  extendtesttime.sh
 This is an interactive script. You will be prompted for how many
  hours you would like to extend the reservation.

 You should verify the watchdog was updated succesfully after
  you extend your reservation.
  https://beaker.engineering.redhat.com/recipes/3310366

 For ssh, kvm, serial and power control operations please look here:
  https://beaker.engineering.redhat.com/view/ibm-z-24.rhts.eng.bos.redhat.com

 For the default root password, see:
  https://beaker.engineering.redhat.com/prefs/

      Beaker Test information:
                         HOSTNAME=ibm-z-24.rhts.eng.bos.redhat.com
                            JOBID=1621450
                         RECIPEID=3310366
                    RESULT_SERVER=127.0.0.1:7086
                           DISTRO=RHEL-6.9-20161201.0
                     ARCHITECTURE=s390x

      Job Whiteboard: RHEL-6.9-20161201.0 Server s390x - VerifyFullyQualifiedDomainNameInFacts_Test

      Recipe Whiteboard: 
**  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **  **
[root@ibm-z-24 ~]# 
[root@ibm-z-24 ~]# hostname --fqdn
ibm-z-24.rhts.eng.bos.redhat.com
[root@ibm-z-24 ~]# 
[root@ibm-z-24 ~]# subscription-manager facts --list | grep fqdn
network.fqdn: ibm-z10-24.rhts.eng.bos.redhat.com
[root@ibm-z-24 ~]# 
[root@ibm-z-24 ~]# hostname --all-fqdn
ibm-z-24.rhts.eng.bos.redhat.com ibm-z10-24.rhts.eng.bos.redhat.com 
[root@ibm-z-24 ~]# 

Actual results:
above

Expected results:
an additional comma delimited fact following the precedence set from RFE bug 874735 that contains all the fully qualified domain names configured on this system across both ipv4 and ipv6...
network.fqdn_list: ibm-z-24.rhts.eng.bos.redhat.com, ibm-z10-24.rhts.eng.bos.redhat.com

Additional info:

Comment 4 Jan Kurik 2017-12-06 10:43:07 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/

Comment 5 Kevin Howell 2017-12-07 16:12:15 UTC

Still a valid request for subscription-manager generally. We'll look at it for RHEL7.

Comment 8 RHEL Program Management 2021-01-15 07:29:01 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.