bilelmsekni / OpenStack-Grizzly-Install-Guide

A full install guide for OpenStack Grizzly
352 stars 218 forks source link

Openvswitch agent is not able to work #60

Closed leon153 closed 11 years ago

leon153 commented 11 years ago

Hi, I met a quantum issue: After install any node, the quantum plugin openvswitch agent service would be working. (Commands “service quantum-plugin-openvswitch-agent status” and “quantum agent-liat” both show fine). However if I reboot the Ubuntu, then this service would be stopped, and couldn’t not enable anymore. Each time issue command “service quantum-plugin-openvswitch-agent start”, /var/log/quantum/openvswitch-agent.log would show: 2013-05-22 22:03:13 ERROR [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed to create OVS patch port. Cannot have tunneling enabled on this agent, since this version of OVS does not support tunnels or patch ports. Agent terminated!

Environment: Server: 3 UCS blade servers, B-series blade server. OS: Ubuntu precise (12.04.2 LTS) OpenStack version: Grizzly, quantum. Quantum plugin: openvswitch, with GRE I follow this document to install: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst Network environment: Control Node: eth0 (API network) (10.246.60.55), eth1(mgmt) (192.168.0.1), eth2(VM network) (192.168.100.1) Network Node: eth0 (External network) (10.246.60.56), eth1 (192.168.0.2), eth2 (192.168.100.2) Compute Node: eth0 (just for my login)(10.246.60.57), eth1 (192.168.0.3), eth2 (192.168.100.3)

Hasn't anyone encountered same issue?

hrushig commented 11 years ago

I did encounter this issue and still searching for the write solution. It looks like there is some debian mismatch issue seen recently. I have workaround for now:

On Reboot, the ip addr does not show OpenVswitch bridges

root@computenode1:~# ovs-vsctl show

May 22 10:44:56|00001|stream_unix|ERR|/tmp/stream-unix.7459.0: connection to /var/run/openvswitch/db.sock failed: No such file or directory

May 22 10:44:56|00002|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)

May 22 10:44:57|00003|stream_unix|ERR|/tmp/stream-unix.7459.1: connection to /var/run/openvswitch/db.sock failed: No such file or directory

May 22 10:44:57|00004|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)

To fix the issue

Set the date correctly date MMDDHHMM

Uninstall the following modules apt-get remove openvswitch-switch openvswitch-datapath-dkms quantum-plugin-openvswitch-agent

Reboot apt-get install openvswitch-switch openvswitch-datapath-dkms quantum-plugin-openvswitch-agent

Reboot

From: leon153 [mailto:notifications@github.com] Sent: Wednesday, May 22, 2013 8:25 PM To: mseknibilel/OpenStack-Grizzly-Install-Guide Subject: [OpenStack-Grizzly-Install-Guide] Openvswitch agent is not able to work (#60)

Hi, I met a quantum issue: After install any node, the quantum plugin openvswitch agent service would be working. (Commands “service quantum-plugin-openvswitch-agent status” and “quantum agent-liat” both show fine). However if I reboot the Ubuntu, then this service would be stopped, and couldn’t not enable anymore. Each time issue command “service quantum-plugin-openvswitch-agent start”, /var/log/quantum/openvswitch-agent.log would show: 2013-05-22 22:03:13 ERROR [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed to create OVS patch port. Cannot have tunneling enabled on this agent, since this version of OVS does not support tunnels or patch ports. Agent terminated!

Environment: Server: 3 UCS blade servers, B-series blade server. OS: Ubuntu precise (12.04.2 LTS) OpenStack version: Grizzly, quantum. Quantum plugin: openvswitch, with GRE I follow this document to install: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst Network environment: Control Node: eth0 (API network) (10.246.60.55), eth1(mgmt) (192.168.0.1), eth2(VM network) (192.168.100.1) Network Node: eth0 (External network) (10.246.60.56), eth1 (192.168.0.2), eth2 (192.168.100.2) Compute Node: eth0 (just for my login)(10.246.60.57), eth1 (192.168.0.3), eth2 (192.168.100.3)

Hasn't anyone encountered same issue?

— Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/issues/60.

leon153 commented 11 years ago

Thanks for the workaround. It really works! Thanks again.

hrushig commented 11 years ago

Just figured out the right way to fix this. After doing apt-get update, apt-get upgrade and apt-get dist-upgrade, we must reboot the node. And, the continue applying the next steps.

educhoko91 commented 10 years ago

I'm having the same issue. I reboot the node after apt-get dist-upgrade. I can't get quantum-plugin-openvswitch-agent running.

[quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed to create OVS patch port. Cannot have tunneling enabled on this agent, since this version of OVS does not support tunnels or patch ports. Agent terminated!

Check https://ask.openstack.org/en/question/1427/ovs-plugin-error-failed-to-create-ovs-patch-port/

educhoko91 commented 10 years ago

Posibble solution run the command: service openvswitch-switch force-reload-kmod

sngirame commented 10 years ago

I have a 3 node PoC setup (controller,compute,network) with grizzly release on ubuntu 12.04. I am also facing the same issue. I tried the solution mentioned by hrushig & educhoko91 but its still not working.

R0peE commented 10 years ago

This is a kernel issue, try downgrading to 3.5.0-41, the reinstall the module

kmadac commented 10 years ago

Here is what helped me to me. Download openvswitch-datapath package from Raring and compile it:

# cd /tmp
# wget http://launchpadlibrarian.net/132679950/openvswitch-datapath-source_1.9.0-0ubuntu1_all.deb
# dpkg -i openvswitch-datapath-source_1.9.0-0ubuntu1_all.deb

# cd /lib/modules/`uname -r`/build/include/linux
# ln -s ../generated/uapi/linux/version.h .

# module-assistant auto-install openvswitch-datapath
YvesChan commented 10 years ago

@educhoko91 's solution did work! I know it's a kernel problem. I'm using Ubuntu 12.04.4, which kernel version is 3.11, but Grizzly version was only support to 2.6-3.5

Newer version of openstack is better...