yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #06130
[Bug 1206925] Re: Creation of the qr interface fails sometimes
This is likely related to the L3 message ordering bug present in
Grizzly. This was addressed in the Havana release. If this shows up,
we can reopen this bug.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1206925
Title:
Creation of the qr interface fails sometimes
Status in OpenStack Neutron (virtual network service):
Won't Fix
Bug description:
Version: Grizzly 2013.1.1
I have a 3 nodes Grizzly setup with one Controller, Network and
Compute(KVM) node. I am using VLAN mode. My use case require me to
create network, create instances, terminate instances and terminate
networks. So I do a lot of network creation and deletion.
It works fine most of the time. But occasionally when an instance is
launched, the instance is unable to reach the external network. When
this happens I see that the 'qr-xxxxx' interface is not created as
shown below:
root@openstack-dev-network# ip netns exec qrouter-81c474cb-acad-42b4-bc78-875992fa33f6 route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.5.60.1 0.0.0.0 UG 0 0 0 qg-81e2a77d-71
1.1.1.0 0.0.0.0 255.255.252.0 U 0 0 0 qg-81e2a77d-71
root@openstack-dev-network #
I see the following error in /var/log/quantum/openvswitch-agent.log
Stderr: 'ovs-vsctl: no row "qr-fb582b82-f7" in table Interface\n'
2013-07-29 06:14:18 ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', 'get', 'Interface', 'qr-a4f24e08-aa', 'external_ids']. Exception:
Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'get', 'Interface', 'qr-a4f24e08-aa', 'external_ids']
Exit code: 1
Stdout: ''
Stderr: 'ovs-vsctl: no row "qr-a4f24e08-aa" in table Interface\n'
And on restarting the quantum services, the interface gets created and the instance is able to reach the external network.
root@openstack-dev-network:~# cd /etc/init.d/; for i in $( ls quantum-* ); do sudo service $i restart; done
quantum-dhcp-agent stop/waiting
quantum-dhcp-agent start/running, process 20872
quantum-l3-agent stop/waiting
quantum-l3-agent start/running, process 20885
quantum-metadata-agent stop/waiting
quantum-metadata-agent start/running, process 20894
quantum-plugin-openvswitch-agent stop/waiting
quantum-plugin-openvswitch-agent start/running, process 20903
root@openstack-dev-network:/etc/init.d#
root@openstack-dev-network# ip netns exec qrouter-81c474cb-acad-42b4-bc78-875992fa33f6 route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.5.60.1 0.0.0.0 UG 0 0 0 qg-81e2a77d-71
1.1.1.0 0.0.0.0 255.255.252.0 U 0 0 0 qg-81e2a77d-71
192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 qr-a4f24e08-aa
root@openstack-dev-network #
I do have the root_helper in /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini.
Regards,
Balu
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1206925/+subscriptions