Bug 1156343
| Summary: | auto-install will fail with bond_setup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yaning Wang <yaniwang> | ||||
| Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.5.0 | CC: | aberezin, aburden, cshao, ecohen, fdeutsch, gklein, hadong, huiwa, iheim, juwu, lsurette, rbarry, ycui | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | node | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Behavior changes in Red Hat Enterprise Linux 7 requires 'boot=' argument to configure bonds, which was causing auto-installation of the Red Hat Enterprise Virtualization Hypervisor 7 to fail when user specified 'boot_setup=' argument, as in Hypervisor 6. These bonding changes are now supported in the Hypervisor and auto-installation of the Hypervisor succeeds as expected with 'bond={bond_name}:{list_of_interfaces}' argument.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-02-11 21:05:07 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1094719 | ||||||
| Attachments: |
|
||||||
I'm not able to reproduce a dracut crash. Can you grab a rdsosreport, please? Ok, I was able to reproduce a hang. This is a behavior change in EL7, and appears to be the same bug as bz#1149694. There's a problem after the media check with unknown links. Appending "bond=bond01:ens3" (EL7 dracut) followed by bond_setup=bond01:ens3 works, but this isn't intuitive. We could also recognize bond=... in ovirt-init-functions and recommend that, but I'm not sure. Fabian, thoughts? We'll need a documentation update for this Note: Using bond= to configure bonds will only work on RHEV-H 7. RHEV-H 6 must continue to use bond_setup Hey Ryan, This bug is still on POST. Will this bug make it into downstream for 3.5 GA? It is not clear enough what needs to be documented in the release notes about this bug. If this bug still needs to be called out in the 3.5 GA release notes, please provide doc text in the doc text field. A bit more context than what's written in comment4 would be really helpful as well. Cheers, Julie Hey Julie - I'm not sure if this is going to make it into 3.5 or not, but I'll update the doctext. Tested on RHVH-H 7.0-20141212.0.el7ev ovirt-node-3.1.0-0.34.el7 Test steps: auto-install with kargs: 'BOOTIF=bond01 bond=bond01:em1,em2 storage_init= adminpw= firstboot' Actual Results: auto-install is success, bond created without error, can obtain IP correctly 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/RHEA-2015-0160.html |
Created attachment 950280 [details] console snapshot Description of problem: auto-install will fail with bond_setup Version-Release number of selected component (if applicable): rhev-hypervisor7-7.0-20141006.0.el7ev ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch.rpm How reproducible: 100% Steps to Reproduce: auto-install with kargs: 'BOOTIF=bond01 bond_setup=bond01:ens3 storage_init=ata adminpw=xxxxxx firstboot' Actual results: install process will fail in very early stage Expected results: should successfully installed. Additional info: