Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2184646

Summary: [RFE] Need the option to provision a host using Satellite with the uppercase hostname in VMWare
Product: Red Hat Satellite Reporter: Sneha Arya <snarya>
Component: ProvisioningAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.12.0CC: ahumbe, dsinglet, mhulan, saydas, shwsingh, sshtein, wpinheir
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA
Target Release: Unused   
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: 2024-06-06 16:12:16 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 Sneha Arya 2023-04-05 10:51:09 UTC
1. Proposed title of this feature request
- [RFE] Need the option to provision host using Satellite with the uppercase hostname in VMWare

2. Who is the customer behind the request?

Account: Zine ZIDANE (Account - 5927578)
TAM customer: No
CSM customer: No
Strategic: No

3. What is the nature and description of the request?
- Need the option to provision host using Satellite with the uppercase hostname in VMWare


4. Why does the customer need this? (List the business requirements here)
- When the customer fills the Hostname field in Satellite, during the host creation, he is putting it in uppercase, but in vsphere it's created in lowercase. What he wants is to be able to choose either the case for my vsphere machine's name or either a completely different name for example:

He is creating a host in satellite named "mylinux1" and in vsphere, the virtual machine could be named "MYLINUX1" or "redhat8" or whatever he chooses.

5. How would the customer like to achieve this? (List the functional requirements here)
- N/A

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- Once this feature will be implemented in Red Hat Satellite then one can provision a host with the name(uppercase/lowercase) as they choose.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
- No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
- No

9. Is the sales team involved in this request and do they have any additional input?
- No

10. List any affected packages or components.
- No

11. Would the customer be able to assist in testing this functionality if implemented?
- Yes

Comment 1 Brad Buckingham 2023-04-06 09:30:49 UTC
*** Bug 2184645 has been marked as a duplicate of this bug. ***

Comment 6 Eric Helms 2024-06-06 16:12:16 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 "SAT-" 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.