Bug 650179
| Summary: | rhevm bridge came up instead of breth0 after fail to configure network | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Mohua Li <moli> | ||||||
| Component: | ovirt-node | Assignee: | Joey Boggs <jboggs> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.5.z | CC: | apevec, jboggs, leiwang, lilu, llim, mburns, mshao, ovirt-maint, ycui | ||||||
| Target Milestone: | rc | Keywords: | TestOnly | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
mburns reviewed -- no tech note needed
no code change, internal only
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 651798 (view as bug list) | Environment: | |||||||
| Last Closed: | 2012-02-21 05:03:01 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 458082 [details]
ovirt.log
Created attachment 458083 [details]
ifcfg-eth0
here is all the network configure file in /etc/sysconfig/network-scripts, [root@localhost 2431-32-4]# cat ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=none HWADDR=00:1F:29:05:B9:1C BRIDGE=rhevm [root@localhost 2431-32-4]# cat ifcfg-eth1 DEVICE=eth1 HWADDR=00:1f:29:05:b9:1d [root@localhost 2431-32-4]# cat ifcfg-rhevm DEVICE=rhevm TYPE=Bridge ONBOOT=yes BOOTPROTO=dhcp DELAY=0 PEERNTP=yes [root@localhost 2431-32-4]# and the network could get ip address *** Bug 651798 has been marked as a duplicate of this bug. *** Steps to Reproduce are not clear enough:
> 1.configure the storage(dirty partition, register to rhevm before)
How was reinstall forced? Did you boot with "firstboot" parameter?
I see in ovirt.log Uninstall was performed which is under Support menu for a reason. Reinstall should not require Uninstall, just choose the same disk, but it is important to force firstboot via parameter first.
yes, surely have parameter "firstboot" in kernel command line, the steps nothing special, just the usual steps, scenario 1, 1,boot to ovirt-node with firstboot parameter, 2,configure partition on the same disk (dirty, register to rhevm before), 3,configure network, then fail with the above error, but rhevm came up, as above fail, so we try uninstall first, scenario 2, 1,boot to ovirt-node with firstboot parameter, 2,support menu->uninstall, success, 3,configure partition, success, 4,configure network, then fail with the above error, but rhevm came up, this not always could reproduced, but have to say we met this often in our test still met this but in rhev-hypervisor 5.5-2.2-8.5, steps is the same as above, the reproducible rate is quite low in recently build(rhev-hypervisor, 5.5-2.2-8.5, 5.6-6.1),just met once in my test, so i think it's ok to move to 5.7, until we found the rule how it happen, According to the comment #9, as we still not find the rule how it happen, so move this bug to 5.7 first. Any problem, please feel free to move to 5.6 again, thanks. Marking TestOnly, please test
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
mburns reviewed -- no tech note needed
no code change, internal only
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. http://rhn.redhat.com/errata/RHSA-2012-0168.html |
Description of problem: after partition, check the network, no network yet, then choose o-c-network, Physical Networking Devices (*=PXE boot interface) Name Driver MAC *eth0 forcedeth 00:1f:29:05:b9:1c eth1 forcedeth 00:1f:29:05:b9:1d 1) eth0 4) NTP 2) eth1 5) Abort 3) DNS 6) Save And Return To Menu Choose an interface or a configuration option: Selected: eth0 Configure breth0 for use by eth0.. NIC is: ACTIVE Help identify eth0 by blinking the lights for 10 seconds ([Y]es or [N]o)? n Include VLAN support ([Y]es, [N]o or [A]bort)? n Enable IPv4 support ([S]tatic IP, [D]HCP or [A]bort)? d Is this correct ([Y]es, [N]o or [A]bort)? y Management Network Configuration ***** WARNING ***** Configuring the network will destroy all existing networking configuration on this system. ***** WARNING ***** Physical Networking Devices (*=PXE boot interface) Name Driver MAC *eth0 forcedeth 00:1f:29:05:b9:1c eth1 forcedeth 00:1f:29:05:b9:1d 1) eth0 4) NTP 2) eth1 5) Abort 3) DNS 6) Save And Return To Menu Choose an interface or a configuration option: Selected: Save And Return To Menu Nov 05 12:50:08 Configuring network Configuring network Nov 05 12:50:09 Network configured successfully Network configured successfully File persisted Successfully persisted /etc/sysconfig/network-scripts/ifcfg-breth0 File persisted Successfully persisted /etc/sysconfig/network-scripts/ifcfg-eth0 File persisted Successfully persisted /etc/sysconfig/network-scripts/ifcfg-eth1 File persisted Successfully persisted /etc/sysconfig/network-scripts/ifcfg-lo File persisted Successfully persisted /etc/ntp.conf Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface eth1: [ OK ] Bringing up interface breth0: Determining IP information for breth0... failed. [FAILED] Selected: Networking setup This node has already registered with the RHEV Manager. Networking can now only be configured via the RHEV Manager. Networking setup ABORTED. Selected: Support Menu Selected: Shell Selected: Exit support menu Selected: Networking setup This node has already registered with the RHEV Manager. Networking can now only be configured via the RHEV Manager. Networking setup ABORTED. Selected: Networking setup This node has already registered with the RHEV Manager. Networking can now only be configured via the RHEV Manager. Networking setup ABORTED. after configure network fail, rhevm bridge came up wiredly, Version-Release number of selected component (if applicable): rhev-hypervisor-5.5.2.2.8.2 How reproducible: met this several times in today's test Steps to Reproduce: 1.configure the storage(dirty partition, register to rhevm before) 2.choose configure network after partition done, 3.network configure fail expectly, 4.bridge rhevm came up but not breth0, Actual results: fail to configure the network, as rhevm bridge exist not breth0 Expected results: breth0 configure successfully but not rhevm show up, Additional info: