Le 19/02/2013 13:31, Gary Kotton a écrit :
The problem is as follows:
When you reboot the host the openvswitch will create the interfaces on
restart. this causes problems with the dhcp and the l3 agents.
the solution to this is to run the quantum-ovs-cleanup utility on
reboot prior to the dhcp
On 02/19/2013 03:47 PM, Sylvain Bauza wrote:
Le 19/02/2013 13:31, Gary Kotton a écrit :
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following "Provided Router/single tenancy" setup.
So, at reboot, my tap/qg/qr network inte
Le 19/02/2013 13:31, Gary Kotton a écrit :
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following "Provided Router/single tenancy" setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: mtu 150
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following "Provided Router/single tenancy" setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: mtu 1500 qdisc noop state DOWN
link/ether fe:10
Hi,
I progressed in investigating the bug. I forgot to mention I was
following "Provided Router/single tenancy" setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: mtu 1500 qdisc noop state DOWN
link/ether fe:10:8c:d8:d8:ca brd ff:ff:ff:ff:ff:ff
inet 19
Hi,
I'll try to be clear. I do follow a classic setup for Quantum with 2
NICs and a GRE tunnel in between nodes with br-int/br-tun.
Everything is fine at first install, but when rebooting the network node
(including quantum-ovs-plugin-agent, quantum-l3-agent and
quantum-dhcp-agent), I notice
6 matches
Mail list logo