Critical used to hide stack traces, we've fixed that fact. No idea what
the original bug was, but at least we could address these in the future.
** Changed in: nova
Status: Incomplete => 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/1193284
Title:
[nova-compute] list index out of range
Status in OpenStack Compute (Nova):
Invalid
Bug description:
OS: CentOS 6.4
Version: openstack Grizzly
I installed the openstack with yum. And I created a network use this command:
nova-manage network create ippool --bridge_interface=br100 192.168.0.0/24
1 250
When restart nova-compute service, I got an CRITICAL error:
2013-06-21 17:30:18 14836 INFO nova.compute.manager [-] Loading compute
driver 'libvirt.LibvirtDriver'
2013-06-21 17:30:18 14836 AUDIT nova.service [-] Starting compute node
(version 2012.2.3-1.el6)
2013-06-21 17:30:20 14836 CRITICAL nova [-] list index out of range
My nova.conf is:
...
# network
network_manager=nova.network.manager.FlatDHCPManager
my_ip=10.66.21.59
fixed_range=192.168.0.0/24
flat_network_bridge=br100
cc_host=192.168.0.1
network_size=8
routing_source_ip=192.168.0.1
...
nova-api/nova-network service started OK. Only nova-compute crashed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1193284/+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
