On 20.11.2012 17:26, Gary Kotton wrote:
On 11/20/2012 06:56 PM, Nux! wrote:
> Right, hit some problems.
> After installing openvswitch, quantum, creating the int and ex
> bridges and following the instructions for a new compute node I can
> see it can successfully contacts the controller (nova-manage service
> list <- lists the new compute service), and it even attempts to build
> a VM but I'm getting the following:
>
> /var/log/nova/compute.log
>
> 2012-11-20 16:49:22 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for node2242
> 2012-11-20 16:49:22 ERROR nova.network.quantumv2 [-]
> _get_auth_token() failed
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2 Traceback (most
> recent call last):
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2 File
> "/usr/lib/python2.6/site-packages/nova/network/quantumv2/__init__.py",
> line 38, in _get_auth_token
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2
> httpclient.authenticate()
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2 File
> "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 199,
> in authenticate
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2 raise
> exceptions.Unauthorized(message=body)
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2 Unauthorized:
> [Errno 111] ECONNREFUSED
> 2012-11-20 16:49:22 TRACE nova.network.quantumv2
> 2012-11-20 16:47:16 TRACE nova.network.quantumv2
> 2012-11-20 16:47:33 INFO nova.virt.libvirt.driver
> [req-ffb7c7cf-8c40-4622-828e-7e6916f608cc
> 3c5b8ffd534347b2b30474b34f57dd3f 6cb0773ff31d480ab04ad9264bdb5f44]
> [instance: b0f4956b-6416-4270-8026-9c28ec927f42] Injecting key into
> image 727b6e19-988e-43b3-ba7c-014beafb6d29
>
> Who refuses the connection to quantum? :-/
In order for Nova to deploy a VM it needs to interface with Quantum.
Can you please check that the /etc/nova.conf is updated correctly.
This should have the keystone credentails for Quantum (you can
compare
with the nova.conf that you have on the controller node)
Yes, my network/quantum settings in nova.conf are the same as on the
controller...
>
> 2012-11-20 16:41:56.762+0000: 1497: info : libvirt version: 0.9.10,
> package: 21.el6_3.5 (CentOS BuildSystem <
http://bugs.centos.org>,
> 2012-10-11-13:57:12,
c6b9.bsys.dev.centos.org)
> 2012-11-20 16:41:56.762+0000: 1497: error :
> virNetDevBridgeCreate:224 : Unable to create bridge virbr0: Package
> not installed
> 2012-11-20 16:45:26.423+0000: 2488: info : libvirt version: 0.9.10,
> package: 21.el6_3.5 (CentOS BuildSystem <
http://bugs.centos.org>,
> 2012-10-11-13:57:12,
c6b9.bsys.dev.centos.org)
> 2012-11-20 16:45:26.423+0000: 2488: error : virNetDevBridgeSet:136 :
> Unable to set bridge virbr0 forward_delay: Operation not supported
> 2012-11-20 16:47:58.628+0000: 2482: error : virNetDevGetMTU:347 :
> Cannot get interface MTU on '': No such device
> 2012-11-20 16:47:58.653+0000: 2482: error : virNetDevGetIndex:657 :
> Unable to get index for interface vnet0: No such device
>
> Selinux is in permissive mode.
>
> What's wrong?
Did you not have this working a few days ago?
I did, on the controller, it works fine, but not on this compute node.
I'll try to dig some more, probably I misconfigured something.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro