Bug 2173586

Summary:	[ESXi][RFE][RHEL7.9]- ability to see FQDN under "DNS Name" in ESXi
Product:	Red Hat Enterprise Linux 7	Reporter:	Marian Jankular <mjankula>
Component:	open-vm-tools	Assignee:	Ani Sinha <anisinha>
Status:	CLOSED MIGRATED	QA Contact:	ldu <ldu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	bdas, boyang, cavery, jen, jsavanyo, jwolfe, ldu, yacao
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2174663 2174668 (view as bug list)		Environment:
Last Closed:	2023-09-22 15:44: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:
Bug Depends On:
Bug Blocks:	2174663, 2174668

Description Marian Jankular 2023-02-27 10:16:05 UTC

Description of problem:
[RFE] - ability to see FQDN under "DNS Name" in ESXi

Version-Release number of selected component (if applicable):
open-vm-tools-11.0.5-3.el7_9.4.x86_64

The customer would like to have the ability in betwen choosing hostname (hostname) and fqdn (hostname -f) in the open-vm-tools conf file similar to overriding the guest os with short-name/long-name in https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/tools.conf

I know that RHEL7 is already in Extended Life Phase however, this should not be a problem for VMware support that is developing the open-vm-tools.

The same RFE applies also to RHEL8 and RHEL9

Comment 3 ldu 2023-03-02 07:32:10 UTC

Clone this bug to RHEL 8 and RHEL 9.

Comment 6 RHEL Program Management 2023-09-22 15:43:14 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-22 15:44:01 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.