Ubuntu 12.04 nova-api fails to start and no error logging

Asked by David Butler

Question 11/5/2012

Nova-api is not starting on Ubuntu 12.04 or logging errors?

I have been working my way through the Openstack Install and Deploy Manual (http://docs.openstack.org/trunk/openstack-compute/install/content/) on a fresh install (10/05/2012) of Ubuntu 12.04, my 3rd or 4th attempt.

$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

$ uname -a
Linux PoC5 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I have setup endpoint for the services as using the %(tenant-id) method, e.g.

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0/ service-create --name=nova --type=compute --description="Nova Compute Service"
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | Nova Compute Service |
| id | e592904ff83147d18b823eecae62aaaa |
| name | nova |
| type | compute |
+-------------+----------------------------------+

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0/ endpoint-create --region RegionOne --service_id=e592904ff83147d18b823eecae62aaaa --publicurl='http://192.168.206.130:8774/v2/%(tenant_id)s' --internalurl='http://192.168.206.130:8774/v2/%(tenant_id)s' --adminurl='http://192.168.206.130:8774/v2/%(tenant_id)s'
+-------------+---------------------------------------------+
| Property | Value |
+-------------+---------------------------------------------+
| adminurl | http://192.168.206.130:8774/v2/%(tenant_id)s |
| id | 7d7d93cde2de4849814f4042197bc2aa |
| internalurl | http://192.168.206.130:8774/v2/%(tenant_id)s |
| publicurl | http://192.168.206.130:8774/v2/%(tenant_id)s |
| region | RegionOne |
| service_id | e592904ff83147d18b823eecae62aaaa |
+-------------+---------------------------------------------+

I can list the tenant id and endpoints for the service as follows:

$ keystone --token 012345SECRET99TOKEN012345 --endpoint http://192.168.206.130:35357/v2.0 tenant-list
+----------------------------------+---------------+---------+
| id | name | enabled |
+----------------------------------+---------------+---------+
| dd5a5ed306ff4ae2be0460e6968f80c5 | openstackDemo | True |
| ee0c4334c48e491a8a14defbe66ab7fe | service | True |
+----------------------------------+---------------+---------+

$ curl -d '{"auth": {"tenantName": "openstackDemo", "passwordCredentials":{"username": "adminUser", "password": "password"}}}' -H "Content-type: application/json" http://192.168.206.130:35357/v2.0/tokens | python -mjson.tool
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 2289 0 2174 100 115 16150 854 --:--:-- --:--:-- --:--:-- 16223
{
    "access": {
        "serviceCatalog": [
            {
                "endpoints": [
                    {
                        "adminURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5",
                        "internalURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5",
                        "publicURL": "http://192.168.206.130:8774/v2/dd5a5ed306ff4ae2be0460e6968f80c5",
                        "region": "RegionOne"
                    }
                ],
                "endpoints_links": [],
                "name": "nova",
                "type": "compute"
            },
  ......

curl -d '{"auth": {"tenantName": "service", "passwordCredentials":{"username": "nova", "password": "nova"}}}' -H "Content-type: application/json" http://192.168.206.130:35357/v2.0/tokens | python -mjson.tool
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 2257 0 2158 100 99 7826 359 --:--:-- --:--:-- --:--:-- 7847
{
    "access": {
        "serviceCatalog": [
            {
                "endpoints": [
                    {
                        "adminURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe",
                        "internalURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe",
                        "publicURL": "http://192.168.206.130:8774/v2/ee0c4334c48e491a8a14defbe66ab7fe",
                        "region": "RegionOne"
                    }
                ],
                "endpoints_links": [],
                "name": "nova",
                "type": "compute"
            },
  .....

For both the service and openstackDemo tenants, the teant ids matche the url endpoints.

Using the api-paste.ini from the manual (http://docs.openstack.org/trunk/openstack-compute/install/content/api-paste-ini-file.html) and the following nova.conf:

[DEFAULT]

# LOGS/STATE
--verbose=True
--debug=True
--logdir=/var/log/nova

# AUTHENTICATION
--auth_strategy=keystone

# SCHEDULER
--compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

# VOLUMES
--volume_group=nova-volumes
--volume_name_template=volume-%08x
--iscsi_helper=tgtadm

# DATABASE
--sql_connection=mysql://nova:password@192.168.206.130/nova

# COMPUTE
--libvirt_type=qemu
--connection_type=libvirt
--instance_name_template=instance-%08x
--api_paste_config=/etc/nova/api-paste.ini
--allow_resize_to_same_host=True

# APIS
--osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
--ec2_dmz_host=192.168.206.130
--s3_host=192.168.206.130

# RABBITMQ
--rabbit_host=localhost
--rabbit_password=password

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

# NETWORK
--network_manager=nova.network.manager.FlatDHCPManager
--force_dhcp_release=True
--dhcpbridge_flagfile=/etc/nova/nova.conf
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--my_ip=192.168.206.130
--public_interface=eth0
--vlan_interface=eth0
--flat_network_bridge=br100
--flat_interface=eth0
--fixed_range=192.168.30.0/24

# NOVNC CONSOLE
--novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html
--vncserver_proxyclient_address=192.168.206.130
--vncserver_listen=192.168.206.130

The nova-api will not start and no info is logged in /var/log/nova/ log files.

Has anyone else seen this?

Is there something fundamentally wrong with how I configured keystone or nova?

Are the ubuntu 12.04 repositories up to date for the openstack and python required versions?

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Armando Migliaccio
Solved:
Last query:
Last reply:
Revision history for this message
Best Armando Migliaccio (armando-migliaccio) said :
#1

try to use use_syslog=True or run nova-api in foreground.

Check that your rabbitmq is correct, as the default one is 'guest'

HTH

Revision history for this message
Charles (kayakyakr) said :
#2

Using upstart on Ubuntu ("service nova-api start") to run nova services, output is logged under /var/log/upstart/nova-____.log . Took me a bit to find that myself.

Revision history for this message
David Butler (david-butler) said :
#3

Cheers for the info.

My main problem was taht I followed the nova install procdure from the Openstack Install and Deploy Manual (http://docs.openstack.org/trunk/openstack-compute/install/content/).

The nova install procdure for ubuntu uses some some different nova componets.

When I followed the OpenStack Compute Starter Guide (http://docs.openstack.org/essex/openstack-compute/starter/content/), the nova components start OK and nova-manage shows working nova components.

Note:

1)

Revision history for this message
David Butler (david-butler) said :
#4

Thanks Armando Migliaccio, that solved my question.

Revision history for this message
David Butler (david-butler) said :
#5

Note:

The nova setup in OpenStack Compute Starter Guide (http://docs.openstack.org/essex/openstack-compute/starter/content/) uses the original nova.conf format (--version etc) and different passwords for all the services.

Revision history for this message
Armando Migliaccio (armando-migliaccio) said :
#6

Hi David,

I am glad you got it sorted. Maybe it's worth raising a bug against the docs, so that other people won't stumble on this again.

Cheers,
Armando

Revision history for this message
Lorin Hochstein (lorinh) said :
#7

As it turns out, The OpenStack Compute Starter Guide is not maintained by the docs team, it's maintained by CSS Corp. You can report bugs against the starter guide at https://bugs.launchpad.net/openstackbook

You can report bugs to the docs team at https://bugs.launchpad.net/openstack-manuals