Bug 1328311
| Summary: | For RHEV+CFME deployment, hypervisor naming schema does not start from 1. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Julie <juwu> | ||||
| Component: | Installation - RHEV | Assignee: | Jesus M. Rodriguez <jesusr> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Dave Johnson <dajohnso> | ||||
| Severity: | unspecified | Docs Contact: | Dan Macpherson <dmacpher> | ||||
| Priority: | unspecified | ||||||
| Version: | 1.0 | CC: | bthurber, cchase, jesusr, tsanders | ||||
| Target Milestone: | ga | ||||||
| Target Release: | 1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1339808 (view as bug list) | Environment: | |||||
| Last Closed: | 2016-05-25 17:56:31 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1321046 | ||||||
| Attachments: |
|
||||||
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. (In reply to Jesus M. Rodriguez from comment #1) > 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. Hi Jesus, Thanks for explaining the behaviour. I have opened a docs bug (BZ#1339808) to make sure this information is captured in the procedure. Kind regards, Julie |
Created attachment 1148314 [details] hypervisor-naming-schema-error 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, ...