Bug 1468758 - [RFE] Allow the host name field to be free text, pass it to RHV
Summary: [RFE] Allow the host name field to be free text, pass it to RHV
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: Unspecified
Hardware: Unspecified
OS: All
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-07 20:28 UTC by Pablo Hess
Modified: 2020-09-10 10:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-28 19:35:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pablo Hess 2017-07-07 20:28:07 UTC
1. Proposed title of this feature request

Allow the Name field on hosts to be set by the user to something other than the fqdn, and pass this Name to RHV when creating new hosts on RHV compute resources.




2. Who is the customer behind the request?

This information will be provided as a private comment.





3. What is the nature and description of the request?

When provisioning new hosts from Satellite to a RHV compute resource, the host fqdn is automatically used for the host name, so the RHV guest is named name-domain-tld or name.domain.tld. Customer would like to set other names to new hosts such as e.g. "webserver01" or "qa_ocpmaster" when creating new hosts on Satellite, and to have Satellite pass this name to RHV for the creation of RHV guest names.




4. Why does the customer need this? (List the business requirements here)

Customer's auditing software queries RHV guest names to run its audits, and checks those names against a database that has short names only.

The RHV guest name is derived from the host name Satellite gives it.
Satellite will always name new hosts with their fqdn.

RHV agent is able to provide short names, but not all RHV guests will have RHV agent installed on this customer's infrastructure.




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

On the webUI, clicking Hosts > New Host would allow the user to set the new host name unrelated to their fqdn. This new host name would be passed to RHV so the RHV guest name would be exactly the same as its Satellite name, i.e. a short name.



6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Customer has a RHV and Satellite sandbox environment where they can test this feature.



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?

No.
Customer is checking with the auditing team whether their software may extract the shortname from the host's fqdn so it will run on those hosts.



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

No.




10. List any affected packages or components.

Katello, RHV integration, all components that use the host name as fqdn.



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

Yes.

Comment 7 Bryan Kearney 2019-02-07 12:09:39 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 8 Bryan Kearney 2019-02-28 19:35:17 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


Note You need to log in before you can comment on or make changes to this bug.