Hi,
I have managed to find the problem :). I have spent the whole day on
this :(.
I was running devstack and the code executes ovs_quantum_agent.py.
Whilst going through the mailing mails I came upon this mail and saw
that you are calling quantum-openvswitch-agent.
I'll post a fix soon.
Hi All,
I am running the latest quantum code base. I am seeing an issue in which the
openvswitch agent is not automatically assigning the vlans to the tap
interfaces of my new instances. If I restart the agent, it fixes the problem.
Has anyone seen this issue?.
#quantum port-list
| True
Hi Joy,
I did noticed a bug in ovs_lib.py but it would cause q-agt to crash. Did
the agent crash?
Aaron
On Thu, Aug 30, 2012 at 2:48 PM, Naveen Joy (najoy) na...@cisco.com wrote:
Hi All,
** **
I am running the latest quantum code base. I am seeing an issue in which
the openvswitch
Hi Aaron,
The agent has not crashed.
#sudo status quantum-openvswitch-agent
quantum-openvswitch-agent start/running, process 20208
However, the agent is not binding the port to the vlan unless I restart it.
The log_file setting in the ovs_quantum_plugin.ini file also doesn't seem to
work.
Hi Dan,
This issue happens only when rpc = True and it happens consistently. When rpc
=False, everything is fine. Thanks for this pointer!. Also, I am just
spinning up a single VM though the horizon interface without using any scripts.
Naveen
-Original Message-
From: Dan
5 matches
Mail list logo
