+++ This bug was initially created as a clone of Bug #1328311 +++
Description of problem:
Hypervisor naming schema does not start from 1.
Version-Release number of selected component (if applicable):
0411 QCI ISO
Steps to Reproduce:
1.Deploy RHEV
2.Assign a hypervisor node, and change the naming schema to hypervisorN.
Actual results:
The only hypervisor discovered and selected is named hypervisor3(see attached screen shot).
Expected results:
It should start from hypervisor1, hypervisor2, ...
--- Additional comment from Jesus M. Rodriguez on 2016-05-25 13:56:31 EDT ---
The number after the hypervisor name is not the order they are in the deployment. It is the database id assigned to them when they were discovered by foreman. We use this as an easy way to create an autogenerated unique name for the hypervisors. Other options available are use mac address which results in macAABBCCDDEE.example.com (where AABBCCDDEE is the mac address of the host), hypervisorN.example.com (where N is the database id assigned to the host), and freeform which let's the user enter in any name they want.
Use freeform is you want a more sequential name.
Revisiting this bug, and still think it makes more sense to make it clear in the UI than in the documentation so users are not confused with the option hyprevisorN.
Comment 7jmagen@redhat.com
2016-07-26 14:25:48 UTC
Verified with QCI-1.0-RHEL-7-20160809.t.1
The text now looks like:
Three host example
hypervisor45
hypervisor12
hypervisor310
hypervisor + {host_id}
Note the last one has the parameterized host_id.
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/RHEA-2016:1862