Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1496963

Summary: [RFE] Provide an option to include FQDN in IDM topology graph
Product: Red Hat Enterprise Linux 7 Reporter: Russ Zaleski <rzaleski>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.4CC: batkisso, frenaud, mcarpent, mkosek, ndehadra, pasik, pvoborni, rcritten, tmihinto, tscherf, vmishra
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ipa-4.6.5-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:09:02 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: 1647919    
Attachments:
Description Flags
Screenshot for topology graph none

Description Russ Zaleski 2017-09-28 20:02:13 UTC
Description of problem:
The topology graph provided from the idm web ui does not provide the FQDN only the short hostname. Some customers may utilize multiple dns zones for hosts with the same short hostname. This makes the topology graph unclear and leads to unneeded confusion.

An option to show FQDN's could alleviate this.

Version-Release number of selected component (if applicable):
ipa-server-4.5
RHEL 7.4

How reproducible:
100%

Steps to Reproduce:
1. Have a topology that includes replicas with the same short hostname but different FQDN
2. Obtain the topology graph from the web ui
3. 

Actual results:
Only short hostnames are displayed on the topology graph

Expected results:


Additional info:

Comment 4 Petr Vobornik 2017-10-16 08:31:45 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/7206

Comment 12 Nikhil Dehadrai 2019-06-24 17:15:32 UTC
ipa-server: ipa-server-4.6.5-9.el7.x86_64

Verified that when multiple server exists in topology, topology graph provided from the idm web ui does now provides the FQDN instead of short hostname


Thus marking the status of bug to "VERIFIED" from comment#11 and above observation.

Comment 13 Nikhil Dehadrai 2019-06-24 17:16:16 UTC
Created attachment 1584108 [details]
Screenshot for topology graph

Comment 15 errata-xmlrpc 2019-08-06 13:09:02 UTC
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-2019:2241