network_configuration_regression

Bug #1310549 reported by Sergey Vasilenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Sergey Vasilenko

Bug Description

After migration to Centos 6.5 we got regression in network setup stage.

Sometimes interface-up process got huge time.

On centos It looks like:

Notice: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-eth1]/L2_ovs_bridge[br-eth1]/ensure: created
Debug: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-eth1]/L2_ovs_bridge[br-eth1]: The container L23network::L2::Bridge[br-eth1] will propagate my refr
esh event
Debug: L23network::L2::Bridge[br-eth1]: The container Class[Advanced_node_netconfig] will propagate my refresh event
Debug: Executing '/usr/bin/ovs-vsctl list-ports br-eth1'
Debug: Executing '/usr/bin/ovs-vsctl port-to-br eth1'
Debug: Executing '/usr/bin/ovs-vsctl add-port br-eth1 eth1'
Notice: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Port[eth1]/L2_ovs_port[eth1]/ensure: created
Debug: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Port[eth1]/L2_ovs_port[eth1]: The container L23network::L2::Port[eth1] will propagate my refresh event
Debug: L23network::L2::Port[eth1]: The container Class[Advanced_node_netconfig] will propagate my refresh event
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-bond23'
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-bond23'
Notice: L2_ovs_bridge[br-bond23](provider=ovs): Bridge 'br-bond23' not exists, creating...
Debug: Executing '/usr/bin/ovs-vsctl add-br br-bond23'
Notice: L2_ovs_bridge[br-bond23](provider=ovs): bridge 'br-bond23' created.
Notice: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-bond23]/L2_ovs_bridge[br-bond23]/ensure: created
Debug: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-bond23]/L2_ovs_bridge[br-bond23]: The container L23network::L2::Bridge[br-bond23] will propagate my refresh event
Debug: L23network::L2::Bridge[br-bond23]: The container Class[Advanced_node_netconfig] will propagate my refresh event
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-ex'
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-ex'
Notice: L2_ovs_bridge[br-ex](provider=ovs): Bridge 'br-ex' not exists, creating...
Debug: Executing '/usr/bin/ovs-vsctl add-br br-ex'
Notice: L2_ovs_bridge[br-ex](provider=ovs): bridge 'br-ex' created.
Notice: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-ex]/L2_ovs_bridge[br-ex]/ensure: created
Debug: /Stage[netconfig]/Advanced_node_netconfig/L23network::L2::Bridge[br-ex]/L2_ovs_bridge[br-ex]: The container L23network::L2::Bridge[br-ex] will propagate my refresh event
Debug: L23network::L2::Bridge[br-ex]: The container Class[Advanced_node_netconfig] will propagate my refresh event
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-mgmt'
Debug: Executing '/usr/bin/ovs-vsctl br-exists br-mgmt'
Notice: L2_ovs_bridge[br-mgmt](provider=ovs): Bridge 'br-mgmt' not exists, creating...
Debug: Executing '/usr/bin/ovs-vsctl add-br br-mgmt'
Notice: L2_ovs_bridge[br-mgmt](provider=ovs): bridge 'br-mgmt' created.
Write failed: Broken pipe
13:11:57 (xenolog@primus) ~
$

Also it may afects Ubuntu.

Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.