Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 651798

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-nodeAssignee: Mike Burns <mburns>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 5.6CC: apevec, leiwang, lilu, llim, mshao, ovirt-maint, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 650179 Environment:
Last Closed: 2010-11-10 10:30:46 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:

Description Mohua Li 2010-11-10 10:25:14 UTC
as this bug also appear in rhev 5.6, so clone it, met this bug 1~2 times during 10 times try, 


+++ This bug was initially created as a clone of Bug #650179 +++

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:

--- Additional comment from moli on 2010-11-05 09:38:28 EDT ---

Created attachment 458082 [details]
ovirt.log

--- Additional comment from moli on 2010-11-05 09:38:57 EDT ---

Created attachment 458083 [details]
ifcfg-eth0

--- Additional comment from moli on 2010-11-05 09:40:47 EDT ---

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

Comment 1 Alan Pevec 2010-11-10 10:30:46 UTC
(In reply to comment #0)
> as this bug also appear in rhev 5.6, so clone it, met this bug 1~2 times during
> 10 times try, 
> 
> 
> +++ This bug was initially created as a clone of Bug #650179 +++

650179 is flagged 5.6 - all new issues need to be proposed against _next_ release first, when fixed there it will get proposed as Z-stream backport.

*** This bug has been marked as a duplicate of bug 650179 ***