<div dir="ltr"><div>I read the bug description (<a href="https://bugs.launchpad.net/quantum/+bug/1091605" target="_blank" style="font-size:13px;font-family:arial,sans-serif">https://bugs.launchpad.net/quantum/+bug/1091605</a>) and the fix (<a href="https://review.openstack.org/#/c/18302/">https://review.openstack.org/#/c/18302/</a>). But I don't understand who is the responsible to call the script on the startup.</div>
<div><br></div><div>Should I put it on something like rc.local? Or is quantum plugins' responsibility to run the utility?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/3/1 Sylvain Bauza <span dir="ltr"><<a href="mailto:sylvain.bauza@digimind.com" target="_blank">sylvain.bauza@digimind.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>There is a known bug for the network
bridges, when rebooting : <br>
<a href="https://bugs.launchpad.net/quantum/+bug/1091605" target="_blank">https://bugs.launchpad.net/quantum/+bug/1091605</a><br>
<br>
Try to delete/recreate your br-int/br-ex and then restart
openvswitch_plugin/l3/dhcp agents, it should fix the issue.<br>
<br>
-Sylvain<br>
<br>
Le 01/03/2013 15:04, The King in Yellow a écrit :<br>
</div>
<blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>In my case, it actually appears that my vms aren't up--
the instances panel says they are up, but looking at the
console, it appears they aren't getting an IP address. This
is a new instance:<br>
<br>
<pre><span style="font-family:courier new,monospace">Begin: Running /scripts/init-bottom ... done.
[ 2.849416] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Thu, 28 Feb 2013 13:29:09 +0000. up 10.41 seconds
no instance data found in start-local
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo : 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 . . fa:16:3e:e0:17:f0
route_info failed
Waiting for network configuration...
</span>
</pre>
It looks like it made an OVS port, though. This is on the
compute node, openvswitch-agent.log:<br>
<br>
<br>
<span style="font-family:courier new,monospace">2013-02-28
08:34:19 DEBUG [quantum.agent.linux.utils] <br>
Command: ['sudo', '/usr/bin/quantum-rootwrap',
'/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2',
'get', 'Interface', 'qvo4f36c3ea-5c', 'external_ids']<br>
Exit code: 0<br>
Stdout: '{attached-mac="fa:16:3e:e0:17:f0",
iface-id="4f36c3ea-5c49-4625-a830-0c81f27ba139",
iface-status=active,
vm-uuid="239d3051-255e-4213-9511-af0a82fcc744"}\n'<br>
Stderr: ''<br>
2013-02-28 08:34:19 DEBUG [quantum.agent.linux.utils]
Running command: sudo /usr/bin/quantum-rootwrap
/etc/quantum/rootwrap.conf ovs-vsctl --timeout=2 get
Interface qvo62721ee8-08 external_ids<br>
2013-02-28 08:34:19 DEBUG [quantum.agent.linux.utils] <br>
:<br>
root@os-compute-01:/var/log/quantum# ovs-vsctl show<br>
3a52a17f-9846-4b32-b309-b49faf91bfc4<br>
Bridge br-int<br>
Port "qvo62721ee8-08"<br>
tag: 1<br>
Interface "qvo62721ee8-08"<br>
Port "qvo1ed73bcc-9d"<br>
tag: 1<br>
Interface "qvo1ed73bcc-9d"<br>
Port "qvoce0c94a9-ef"<br>
tag: 1<br>
Interface "qvoce0c94a9-ef"<br>
Port "qvo135e78dd-8e"<br>
tag: 4095<br>
Interface "qvo135e78dd-8e"<br>
Port "qvof37b7a55-a3"<br>
tag: 1<br>
Interface "qvof37b7a55-a3"
<div><br>
Port br-int<br>
Interface br-int<br>
type: internal<br>
Port patch-tun<br>
Interface patch-tun<br>
type: patch<br>
options: {peer=patch-int}<br>
</div>
Port "qvoaed25b41-9c"<br>
tag: 1<br>
Interface "qvoaed25b41-9c"<br>
Port "qvo4f36c3ea-5c"<br>
tag: 1<br>
Interface "qvo4f36c3ea-5c"<br>
Bridge br-tun
<div><br>
Port patch-int<br>
Interface patch-int<br>
type: patch<br>
options: {peer=patch-tun}<br>
</div>
Port "gre-1"<br>
Interface "gre-1"<br>
type: gre<br>
options: {in_key=flow, out_key=flow,
remote_ip="10.10.10.1"}
<div><br>
Port br-tun<br>
Interface br-tun<br>
type: internal<br>
ovs_version: "1.4.0+build0"<br>
</div>
root@os-compute-01:/var/log/quantum#</span><br>
<br>
<br>
</div>
I supposed it should be getting address via DHCP from
quantum-dhcp-agent on the network node? It was running,
nothing regarding this MAC in the logs. I restarted
quantum-dhcp-agent and rebooted, no change.<br>
<br>
</div>
In fact, I got two CirrOS vms up, logged on the console and
manually IPed them (<a href="http://10.5.5.10/24" target="_blank">10.5.5.10/24</a> and <a href="http://10.5.5.11/24" target="_blank">10.5.5.11/24</a>),
and they can't ping each other. I would expect them to, right?
They should both be connected to OVS switch br-int, right?<br>
<div>
<br>
Any pointers?</div>
<div class="gmail_extra"><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><div class="im"><pre>_______________________________________________
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a>
</pre>
</div></blockquote>
<br>
</div>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Filipe Manco<br><div><a href="http://about.me/fmanco" target="_blank">about.me/fmanco</a></div></div>
</div>