Bug 781929 - network layout is incorrect when configure network with nic up
Summary: network layout is incorrect when configure network with nic up
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 768256
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-16 05:53 UTC by Guohua Ouyang
Modified: 2016-04-26 14:17 UTC (History)
13 users (show)

Fixed In Version: ovirt-node-2.3.0-5.el6
Doc Type: Bug Fix
Doc Text:
Previously, when re-configuring the Hypervisor's network settomgs, the previous values would not be removed correctly. Now, the previous network configuration values s are completely removed prior to applying new changes.
Clone Of: 768256
Environment:
Last Closed: 2012-07-19 14:17:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
/var/log/message (16.57 KB, text/plain)
2012-04-28 07:05 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Comment 1 Guohua Ouyang 2012-01-16 05:55:47 UTC
Tested on 6.2-20120106 build, also have this problem:

[root@unused admin]# brctl show
bridge name	bridge id		STP enabled	interfaces
breth0		8000.000000000000	no		
breth1		8000.00101866c286	no		eth1
breth3		8000.000000000000	no		
[root@unused admin]# ifconfig
breth0    Link encap:Ethernet  HWaddr 26:2A:3D:23:7F:95  
          inet6 addr: fe80::242a:3dff:fe23:7f95/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:2520 (2.4 KiB)

breth1    Link encap:Ethernet  HWaddr 00:10:18:66:C2:86  
          inet addr:10.66.105.83  Bcast:10.66.111.255  Mask:255.255.248.0
          inet6 addr: fe80::210:18ff:fe66:c286/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:801 errors:0 dropped:0 overruns:0 frame:0
          TX packets:221 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:75297 (73.5 KiB)  TX bytes:33221 (32.4 KiB)

breth3    Link encap:Ethernet  HWaddr D2:B4:4E:37:7F:A0  
          inet6 addr: fe80::d0b4:4eff:fe37:7fa0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:2862 (2.7 KiB)

eth1      Link encap:Ethernet  HWaddr 00:10:18:66:C2:86  
          inet6 addr: fe80::210:18ff:fe66:c286/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:855 errors:0 dropped:0 overruns:0 frame:0
          TX packets:221 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:96645 (94.3 KiB)  TX bytes:33697 (32.9 KiB)
          Interrupt:17 Memory:e4800000-e4ffffff

Comment 3 Mike Burns 2012-02-03 21:02:46 UTC
http://gerrit.ovirt.org/#change,1606

Comment 5 Fabian Deutsch 2012-04-19 10:16:04 UTC
This patch can help:

http://gerrit.ovirt.org/#change,3680

The patch removes all configuration files for the NICs and just ifups the
selected one. This prevents the creation of weird network setups.

Comment 8 Guohua Ouyang 2012-04-28 07:05:05 UTC
Created attachment 580939 [details]
/var/log/message

Tested on rhevh-6.3-20120426.2 build, the patch is good to remove all existed network files and to create new network files, but there are still two things need to handle:
1. It takes too long time (about 5 seconds) to detect the existed network info and pop up the sub page. 
2. After reconfigure the other nic, it's not up.  it seems due to dhclient is already running according to /var/log/message:
  dhclient[22242]: dhclient(18827) is already running - exiting.

Comment 13 Mike Burns 2012-06-13 17:08:23 UTC
    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:
Previously, when re-configuring the network, the previous configuration would not be cleaned up correctly.  Now, the previous network scripts are completely cleaned up prior to applying new changes.

Comment 14 Stephen Gordon 2012-06-14 15:01:45 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, when re-configuring the network, the previous configuration would not be cleaned up correctly.  Now, the previous network scripts are completely cleaned up prior to applying new changes.+Previously, when re-configuring the Hypervisor's network settomgs, the previous values would not be removed correctly. Now, the previous network configuration values s are completely removed prior to applying new changes.

Comment 16 errata-xmlrpc 2012-07-19 14:17:45 UTC
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/RHBA-2012-0741.html


Note You need to log in before you can comment on or make changes to this bug.