this is either a f19 issue or a openvswitch issue as we don't
set/use/maintain the unix:/var/run/openvswitch/db.sock parameter
anywhere in the nova code base and hence have no "cleanup" code for
clearing up that file.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1266827
Title:
Instances fail to boot with error: /var/run/openvswitch/db.sock:
connection attempt failed
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Tested on RHEL6.5 with havana release
openstack-nova-compute-2013.2.1-1.el6.noarch.
Installed openstack via packstack allinone. Have not configured neutron for
external access. Using the default network.
Steps to reproduce:
1. Create a f19 glance image.
2. Boot an instance with the above image.
Fails with the following in nova/compute.log:
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] File
"/usr/lib/python2.6/site-packages/nova/network/linux_net.py", line 1280, in
create_ovs_vif_port
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] run_as_root=True)
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] File
"/usr/lib/python2.6/site-packages/nova/utils.py", line 177, in execute
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] return processutils.execute(*cmd,
**kwargs)
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] File
"/usr/lib/python2.6/site-packages/nova/openstack/common/processutils.py", line
178, in execute
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] cmd=' '.join(cmd))
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] ProcessExecutionError: Unexpected error
while running command.
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] Command: sudo nova-rootwrap
/etc/nova/rootwrap.conf ovs-vsctl -- --may-exist add-port br-int qvoab718ad4-cb
-- set Interface qvoab718ad4-cb
external-ids:iface-id=ab718ad4-cb35-4736-b57b-d4c2b002cb36
external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:f1:ae:df
external-ids:vm-uuid=787f6b8d-2851-41d2-9a2d-d7b5701c546f
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] Exit code: 1
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] Stdout: ''
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f] Stderr:
'2014-01-07T15:36:50Z|00002|reconnect|WARN|unix:/var/run/openvswitch/db.sock:
connection attempt failed (Connection refused)\novs-vsctl:
unix:/var/run/openvswitch/db.sock: database connection failed (Connection
refused)\n'
2014-01-07 21:07:10.245 32545 TRACE nova.compute.manager [instance:
787f6b8d-2851-41d2-9a2d-d7b5701c546f]
NOTE: This was a working setup. Have booted instances before with the same
image. No config changes have been made that could explain the failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1266827/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
