Bug 1275226
| Summary: | TUI shows "; vdsmdummy; " after TUI/auto installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | wanghui <huiwa> |
| Component: | ovirt-node | Assignee: | Anatoly Litovsky <tlitovsk> |
| Status: | CLOSED ERRATA | QA Contact: | wanghui <huiwa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6.0 | CC: | bmcclain, cshao, cwu, fdeutsch, gklein, huiwa, huzhao, leiwang, lsurette, yaniwang, ycui, ykaul |
| Target Milestone: | ovirt-3.6.1 | ||
| Target Release: | 3.6.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-3.6.0-0.22.20151126git72acbb2.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-09 14:41:31 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: | |||
|
Description
wanghui
2015-10-26 10:04:32 UTC
Hui, please provide the complete kernel arguments you used for installation Hi Fabian, I just use the default parameters. Kernel command line: initrd=initrd0.img root=live:CDLABEL=rhev-hypervisor7-7.2-20151025.0 rootfstype=auto ro rd.live.image rd.live.check crashkernel=256M rd_NO_MULTIPATH rootflags=ro elevator=deadline install quiet max_loop=256 rhgb rd.luks=0 rd.md=0 rd.dm=0 nomodeset firstboot BOOT_IMAGE=vmlinuz0 Test version: rhev-hypervisor7-7.2-20151201.2 ovirt-node-3.6.0-0.23.20151201git5eed7af.el7ev.noarch Test step: 1. TUI/auto clean install rhev-hypervisor7-7.2-20151201.2 2. Check the Network page Test result: 1. It don't show ";vdsmdummy;" as the Device name in "Available System NICs" column now. So this issue is fixed in ovirt-node-3.6.0-0.23.20151201git5eed7af.el7ev.noarch. Change the status to verified. 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-2016-0378.html |