[Folsom] Conflict between nova-api and cinder-api

Bug #1073571 reported by Philippe Berthault
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Undecided
Unassigned
cinder (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

There is a socket conflict between nova-api and cinder-api.

When nova-api service is started first, then cinder-api can't be started because of the following error:
    error: [Errno 98] Address already in use

When cinder-api service is started first, then it's nova-api which can't be started with the same error.

Context: OpenStack Folsom on Ubuntu 12.10.

Revision history for this message
Thierry Carrez (ttx) wrote :

I'd say the issue lies with Cinder, and may be limited to Ubuntu packaging.

affects: nova → cinder
Revision history for this message
Vish Ishaya (vishvananda) wrote :

Cinder and nova-api-os-volume use the same port on purpose. You have to disable the volume api in nova if you want to use cinder.

As mentioned in point 10 here:

http://wiki.openstack.org/MigrateToCinder

You should make sure osapi_volume is ignored in your conf file.

enabled_apis=ec2,osapi_compute,metadata

Changed in cinder:
status: New → Invalid
James Page (james-page)
Changed in cinder (Ubuntu):
status: New → Invalid
Revision history for this message
Jeff Mitchell (jefferai) wrote :

I'm hitting this bug, but I both have enabled_apis defined in my nova.conf and I don't have osapi_volume in there:

enabled_apis=ec2,osapi_compute,metadata

Could there be some other issue specific to the Ubuntu packages?

Revision history for this message
Jeff Mitchell (jefferai) wrote :

I figured it out:

This documenation here: http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-openstack-compute-basics.html has an authentication section that has a [keystone_authtoken] group near the top of the file.

Unfortunately, that means that the rest of the file is all but ignored because the options are in the wrong group in the INI file -- including enabled_apis.

Moving the auth section to the bottom of the file fixed it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.