openstack team mailing list archive

[Blair Zajac <blair@xxxxxxxxxxxx>]

I was running Folsom on Quantal with nova-network using a 
FlatDHCPManager and upgraded to Raring today, which upgrades to Grizzly. 
 After working through config files, trying to launch a 12.04.2 LTS 
instance, the VM console log shows:

Begin: Running /scripts/init-bottom ... done.
[    1.132108] Refined TSC clocksource calibration: 3292.523 MHz.
[    1.393917] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Sat, 13 Apr 2013 19:57:34 +0000. up 2.80 
seconds
no instance data found in start-local
ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
ci-info: eth0  : 1 192.168.1.2     255.255.255.0   fa:16:3e:26:db:b6
ci-info: route-0: 0.0.0.0         192.168.1.1     0.0.0.0         eth0   UG
ci-info: route-1: 192.168.1.0     0.0.0.0         255.255.255.0   eth0   U
cloud-init start running: Sat, 13 Apr 2013 19:57:38 +0000. up 6.03 seconds
2013-04-13 20:01:41,428 - util.py[WARNING]: 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2/120s]: url error [[Errno 113] No route to host]
...
2013-04-13 20:03:33,476 - util.py[WARNING]: 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[115/120s]: url error [[Errno 113] No route to host]
2013-04-13 20:03:38,481 - DataSourceEc2.py[CRITICAL]: giving up on md 
after 120 seconds

no instance data found in start


For the Grizzly upgrade, on any apt-get conflicts I got on the upgrade, 
I would install the pristine Grizzly conf file and then go back and 
applied the diff between Folsom's pristine conf and my Folsom conf.

The ci-info lines show it coming up with 192.168.1.2 but it should be 
with 192.168.2.2.  There's a router providing DHCP on the network that 
the host is on, so maybe that's where it's getting the 192.168.1.2 address?

I noticed that I have nova-api but there's also a nova-api-metadata 
package, but it 'breaks' nova-api and will uninstall nova-api.  Do I 
want to do that?

Thanks,
Blair


[DEFAULT]

# LOGS/STATE
verbose=True
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
rootwrap_config=/etc/nova/rootwrap.conf

# SCHEDULER
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

# VOLUMES
volume_api_class=nova.volume.cinder.API
osapi_volume_listen_port=5900
# MAKE SURE NO ENTRY FOR osapi_volume anywhere in nova.conf!!!
# Leaving out enabled_apis altogether is NOT sufficient, as it defaults
# to include osapi_volume
enabled_apis=ec2,osapi_compute,metadata
###volume_group = cinder-volumes

# DATABASE
sql_connection=mysql://os-nova:xxxx@localhost/os-nova

# COMPUTE
libvirt_type=kvm
compute_driver=libvirt.LibvirtDriver
instance_name_template=instance-%08x
api_paste_config=/etc/nova/api-paste.ini

# COMPUTE/APIS: if you have separate configs for separate services
# this flag is required for both nova-api and nova-compute
allow_resize_to_same_host=True

# APIS
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
#ec2_host=192.168.1.205
#ec2_dmz_host=192.168.1.205
s3_host=192.168.1.205
metadata_host=192.168.1.205
metadata_listen=0.0.0.0

# RABBITMQ
rabbit_host=192.168.1.205

# GLANCE
image_service=nova.image.glance.GlanceImageService
glance_api_servers=192.168.1.205:9292

# NETWORK
network_manager=nova.network.manager.FlatDHCPManager
force_dhcp_release=True
dhcpbridge=/usr/bin/nova-dhcpbridge
dhcpbridge_flagfile=/etc/nova/nova.conf
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
# Change my_ip to match each host
my_ip=192.168.1.205
public_interface=br100
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0
fixed_range=192.168.2.0/24

floating_range=192.168.1.224/28
auto_assign_floating_ip=True

# NOVNC CONSOLE
novncproxy_base_url=http://192.168.1.205:6080/vnc_auto.html
# Change vncserver_proxyclient_address and vncserver_listen to match 
each compute host
vncserver_proxyclient_address=192.168.1.205
vncserver_listen=192.168.1.205

# AUTHENTICATION
#ec2_url=http://192.168.1.205:8773/services/Cloud
#keystone_ec2_url=http://192.168.1.205:5000/v2.0/ec2tokens
use_deprecated_auth=false
auth_strategy=keystone
[keystone_authtoken]
auth_host=127.0.0.1
auth_port=35357
auth_protocol=http
admin_tenant_name=service
admin_user=nova
admin_password=xxxx
signing_dirname=/tmp/keystone-signing-nova
enabled_apis=ec2,osapi_compute,metadata