Bug 1131639
| Summary: | Rubygem-Staypuft: Using different HW in the same deployment will fail the deployment because the NICs are named differently. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Mike Burns <mburns> |
| Component: | rhel-osp-installer | Assignee: | Mike Burns <mburns> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | aberezin, ajeain, dradez, lnatapov, mburns, mlopes, morazi, ohochman, rhos-maint, sasha, sclewis, sgordon, yeylon |
| Target Milestone: | z2 | Keywords: | TestOnly |
| Target Release: | Installer | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
This enhancement allows Red Hat Enterprise Linux OpenStack Platform installer to deploy controllers on heterogeneous hardware. This was added to support environments without consistent hardware.
Consequently, users can now configure the NICs on each host individually, or on a group of hosts together if they have the same NIC layout. In addition, the user interface enforces that the hosts can only be configured if the NIC layouts match.
|
Story Points: | --- |
| Clone Of: | 1126982 | Environment: | |
| Last Closed: | 2014-11-04 17:02:02 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: | 1126982 | ||
| Bug Blocks: | |||
|
Comment 4
Mike Burns
2014-10-01 17:42:30 UTC
This was resolved in A1, marking testonly Verified: rhel-osp-installer-0.4.1-2.el6ost.noarch The concern here was that the same NIC name was specified for for tenant or external network with the assumption that the same NIC name is used on all nodes. We now have NIC assignment per hosts. Already saw cases where NICs were named differently (VM based setup) and yet due to the fact that the assignment is done per host - the deployment succeeds. 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://rhn.redhat.com/errata/RHBA-2014-1800.html |