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.
1. Customer Name
The University of Sydney
2. What is the nature and description of the request?
a way to define macro for a short host name instead of FQDN
3. Why does the customer need this? (List the business requirements here)
Alias is the culprit. Output of the command hostname -s ( short ) is often used as an alias, this is a business case for an short name.
4. How would the customer like to achieve this? (List the functional requirements here)
define macro for a short host name instead of FQDN
5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
7. How quickly does this need resolved? (desired target release)
RHN Satellite 5.5
8. Does this request meet the RHEL Inclusion criteria (please review)
Yes
9. List the affected packages
Not sure
10. Would the customer be able to assist in testing this functionality if implemented?
Not Sure
This is addressed in Satellite 6. There are two unique facts which can be used in templates:
hostname
fqdn
If thee are not sufficient, customers can create custom facts and use those.