Your message dated Tue, 04 Mar 2014 19:17:59 +0800
with message-id <[email protected]>
and subject line Re: [PKG-Openstack-devel] Bug#740618: nova-network: instances
fail to start due to missing ovs-vsctl
has caused the Debian Bug report #740618,
regarding nova-network: instances fail to start due to missing ovs-vsctl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
740618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740618
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nova-network
Version: 2013.2.2-2
Severity: important
Hi,
During instance startup, I get:
./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE nova.compute.manager
[instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef] Command: sudo nova-rootwrap
/etc/nova/rootwrap.conf ovs-vsctl -- --may-exist add-port br-int gw-284f0323-d8
-- set Interface gw-284f0323-d8 type=internal -- set Interface gw-284f0323-d8
external-ids:iface-id=gw-284f0323-d8 -- set Interface gw-284f0323-d8
external-ids:iface-status=active -- set Interface gw-284f0323-d8
external-ids:attached-mac=fa:16:3e:32:2f:0a
./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE nova.compute.manager
[instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef] Exit code: 96
./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE nova.compute.manager
[instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef] Stdout: ''
./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE nova.compute.manager
[instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef] Stderr:
'/usr/bin/nova-rootwrap: Executable not found: ovs-vsctl (filter match =
ovs-vsctl)\n'
maybe a missing dependancy on openvswitch-switch?
- Lucas
--- End Message ---
--- Begin Message ---
On 03/04/2014 06:32 AM, Michael Rommel wrote:
> On Mar 3, 2014, at 17:56 , Lucas Nussbaum <[email protected]
> <mailto:[email protected]>> wrote:
>
>> Package: nova-network
>> Version: 2013.2.2-2
>> Severity: important
>>
>> Hi,
>>
>> During instance startup, I get:
>>
>> ./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE
>> nova.compute.manager [instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef]
>> Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --
>> --may-exist add-port br-int gw-284f0323-d8 -- set Interface
>> gw-284f0323-d8 type=internal -- set Interface gw-284f0323-d8
>> external-ids:iface-id=gw-284f0323-d8 -- set Interface gw-284f0323-d8
>> external-ids:iface-status=active -- set Interface gw-284f0323-d8
>> external-ids:attached-mac=fa:16:3e:32:2f:0a
>> ./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE
>> nova.compute.manager [instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef]
>> Exit code: 96
>> ./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE
>> nova.compute.manager [instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef]
>> Stdout: ''
>> ./nova/nova-compute.log:2014-03-03 16:48:07.790 2182 TRACE
>> nova.compute.manager [instance: 49d4e3ad-bef4-4139-83a4-179a4faa03ef]
>> Stderr: '/usr/bin/nova-rootwrap: Executable not found: ovs-vsctl
>> (filter match = ovs-vsctl)\n'
>>
>> maybe a missing dependancy on openvswitch-switch?
>>
>> - Lucas
> Hi,
>
> I am not sure whether nova-network uses OpenvSwitch. neutron is
> usually used in conjunction with ovs.
>
> Cheers,
>
> Michael.
As per what Michael wrote, nova-network doesn't use OVS. So it's very
likely that the log you provide above is due to a miss-configuration. By
default, nova is meant to be used with Neutron (and more specifically
with the OVS or with the ML2 plugin), not with nova-network. If you do
want to use nova-network, then you need to configure it properly.
I also do recommend using OVS 2.0.1 and kernel 3.12 from backports if
you want to use the ML2 plugin (so that you can use VXLAN, which is the
best way to provide network to compute nodes).
Cheers,
Thomas Goirand (zigo)
--- End Message ---
