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.
DescriptionVladimir Vasilev
2014-09-23 13:53:57 UTC
Description of problem:
I have RHEV as Compute Resource. When I create new host from Satellite and put "vm01" for Name it's created in RHEV as "vm01-virt-eng-brq-redhat-com" (looks like taken from my subnet Domain which is virt.eng.brq.redhat.com).
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Add RHEV as Compute Resource
2. Add New Host with name "vm01" and desired network/os/etc.
3. Login to RHEV and see the actual name.
Actual results:
vm01-subnet (for example vm01-virt-eng-brq-redhat-com)
Expected results:
vm01
Additional info:
Also in Satellite -> All Hosts it's displayed as "vm01.virt.eng.brq.redhat.com". In that case the column should be Hostname and not Name.
Comment 1RHEL Program Management
2014-09-23 14:03:24 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
FQDNs are used throughout, a host's name refers to the FQDN so this is correct.
Set use_shortname_for_vms to true under Adminster > Settings > Provisioning if you wish to override the compute resource naming behaviour, but it's not recommended.