Bug 689007

Summary: [RFE] a way to define macro for a short host name instead of FQDN
Product: Red Hat Satellite Reporter: Chris Williams <cww>
Component: Configuration ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: bkearney, cperry
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-23 16:26:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 471260    

Description Chris Williams 2011-03-18 19:14:20 UTC
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

Comment 5 Bryan Kearney 2015-01-23 16:26:59 UTC
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.