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.
DescriptionJulio Entrena Perez
2016-03-14 13:23:43 UTC
Description of problem:
When creating a new host ("hosta") in a RHEV compute resource using a specific domain ("example.com") the RHEV VM is named "hosta-example-com" rather than "hosta.example.com".
Version-Release number of selected component (if applicable):
6.1.7
How reproducible:
Always
Steps to Reproduce:
1. Create a new host ("hosta") on a RHEV compute resource using an existing template
2.
3.
Actual results:
RHEV VM is named "hosta-example-com"
Expected results:
RHEV VM is named "hosta.example.com"
Additional info:
Comment 1Julio Entrena Perez
2016-03-14 13:46:03 UTC
Comment 2Julio Entrena Perez
2016-03-17 10:43:42 UTC
In file /usr/share/foreman/app/models/compute_resources/foreman/model/ovirt.rb :
139 def create_vm(args = {})
* 140 #ovirt doesn't accept '.' in vm name.
* 141 args[:name] = args[:name].parameterize
142 if (image_id = args[:image_id])
Customer confirms that removing lines 140 and 141 results in VM names being created with dots (hosta.example.com).
Comment 3Julio Entrena Perez
2016-04-05 09:50:42 UTC
Increasing severity since this affects all RHEV VMs created from Satellite that include dots in the name.
Comment 12Lukáš Hellebrandt
2017-10-04 12:51:45 UTC
Verified with Sat6.3 snap 18.
Creating RHEV guests from Create Host dialog results in guests with dots in their name (rather than replacing dots with hyphens). The systems are indeed created also in Satellite and they can be power managed.
This seems to work, just note this actually changes behavior observable by customers and can, for example, break some of ther scripts. This is, however, expected as per comment 7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:0336
Description of problem: When creating a new host ("hosta") in a RHEV compute resource using a specific domain ("example.com") the RHEV VM is named "hosta-example-com" rather than "hosta.example.com". Version-Release number of selected component (if applicable): 6.1.7 How reproducible: Always Steps to Reproduce: 1. Create a new host ("hosta") on a RHEV compute resource using an existing template 2. 3. Actual results: RHEV VM is named "hosta-example-com" Expected results: RHEV VM is named "hosta.example.com" Additional info: