Pádraig
Thanks.
core01 is the controller. ( Do I need to disable nova-cert on the controller? )
nova-manage service list
DEBUG nova.utils [req-0d242a3d-ede1-41fd-9064-2b6a0fb3e14d None None] backend <module
'nova.db.sqlalchemy.api' from
'/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.pyc'> from (pid=6653)
__get_backend /usr/lib/python2.7/site-packages/nova/utils.py:659
Binary Host Zone Status State
Updated_At
nova-compute core01 nova enabled :-)
2012-05-09 13:33:01
nova-scheduler core01 nova enabled :-)
2012-05-09 13:33:01
nova-volume core01 nova enabled :-)
2012-05-09 13:33:01
nova-cert core01 nova enabled :-)
2012-05-09 13:33:01
nova-network core01 nova enabled :-)
2012-05-09 13:33:01
nova-compute core00 nova enabled :-) 2012-05-09
13:32:59
nova-network core00 nova disabled XXX 2012-05-08
21:21:04
nova.conf on the second compute node:
[DEFAULT]
logdir = /var/log/nova
state_path = /var/lib/nova
lock_path = /var/lib/nova/tmp
dhcpbridge = /usr/bin/nova-dhcpbridge
dhcpbridge_flagfile = /etc/nova/nova.conf
force_dhcp_release = True
injected_network_template = /usr/share/nova/interfaces.template
libvirt_xml_template = /usr/share/nova/libvirt.xml.template
libvirt_nonblocking = True
vpn_client_template = /usr/share/nova/client.ovpn.template
credentials_template = /usr/share/nova/novarc.template
network_manager = nova.network.manager.FlatDHCPManager
iscsi_helper = tgtadm
#sql_connection = mysql://nova:nova@localhost/nova
connection_type = libvirt
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
rpc_backend = nova.rpc.impl_qpid
root_helper = sudo nova-rootwrap
#rabbit_host = 172.20.0.51
sql_connection = mysql://nova:nova@172.20.0.51/nova
glance_api_servers =
http://172.20.0.51:9292
iscsi_ip_prefix = 172.20.0.51
ec2_api = 172.20.0.51
ec2_url =
http://172.20.0.51:8773/services/Cloud
fixed_range = 10.0.0.0/24
network_size = 256
qpid_hostname = 172.20.0.51
verbose = true
auth_strategy = keystone
----- Original Message -----
From: Pádraig Brady <P(a)draigBrady.com>
To: Ask Stack <askstack(a)yahoo.com>; Fedora Cloud SIG
<cloud(a)lists.fedoraproject.org>
Cc:
Sent: Tuesday, May 8, 2012 7:25 PM
Subject: Re: nova.rpc.amqp ValueError: too many values to unpack
On 05/09/2012 12:13 AM, Ask Stack wrote:
Instances can start on the first nova node (controller) fine.
I am having problems with the second nova computing node.
"nova-manage service list" shows "nova-compute" have smilies on both
nodes.
"euca-describe-images" shows the correct images.
however when I launch an instance, nova's compute log shows
TRACE nova.rpc.amqp File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 86, in
pick_glance_api_server
TRACE nova.rpc.amqp host, port_str = host_port.split(':')
TRACE nova.rpc.amqp ValueError: too many values to unpack
TRACE nova.rpc.amqp
This is on a fedora 16 environment. Both computers have the same rpm packages.
python-glance-2012.1-4.fc16.noarch
python-novaclient-2012.1-1.fc16.noarch
python-nova-2012.1-3.fc16.noarch
openstack-nova-2012.1-3.fc16.noarch
Sounds like a config error.
What's the value of this variable in /etc/nova/nova.conf?
###### (ListOpt) A list of the glance api servers available to nova ([hostname|ip]:port)
# glance_api_servers="$glance_host:$glance_port"
cheers,
Pádraig