Ask Your Question
0

cinder services abort with ArgsAlreadyParsedError (havana)

asked 2014-01-14 05:15:43 -0500

gklyne gravatar image

updated 2014-01-14 13:25:55 -0500

I'm an openstack n00b. I previously installed Folsom on the same system, but didn't use it, then ditched it to upgrade to Havana. I think I cleared out all the old installation files.

I'm trying to install an all-in-one (single node) OpenStack system following the instructions at http://docs.openstack.org/trunk/install-guide/install/apt/content/ , on Ubuntu 12.04 server. I'm using the Ubuntu Cloud Archive APT repository, per http://docs.openstack.org/trunk/install-guide/install/apt/content/basics-packages.html

I have keystone, glance and nova installed and apparently running OK. I can fire up and log in to a VM instance.

But when I get to installing cinder (per http://docs.openstack.org/trunk/install-guide/install/apt/content/ch_cinder.html ), I'm finding that the cinder-scheduler and cinder-volumes won't start. Both are failing with a similar error, with the last few lines of the log like this:

2014-01-14 10:48:21.041 5968 TRACE cinder.service   File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 1731, in register_cli_opt
2014-01-14 10:48:21.041 5968 TRACE cinder.service     raise ArgsAlreadyParsedError("cannot register CLI option")
2014-01-14 10:48:21.041 5968 TRACE cinder.service ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option
2014-01-14 10:48:21.041 5968 TRACE cinder.service 
2014-01-14 10:48:21.058 5935 INFO cinder.service [-] Child 5968 exited with status 2
2014-01-14 10:48:21.059 5935 INFO cinder.service [-] _wait_child 1
2014-01-14 10:48:21.059 5935 INFO cinder.service [-] wait wrap.failed True

When I run cinder, I (unsurprisingly) get an error - e.g.:

# cinder list
Could not find any suitable endpoint. Correct region?
ERROR:

I assume that's because the required services are not running.

I've run out of things to try, or places to look. Can anyone suggest any ideas to get me moving again?

Thanks!

#g.

/etc/cinder/cinder.conf is:

[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper = tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes

# The SQLAlchemy connection string used to connect to the
# database (string value)
sql_connection = mysql://cinderdbadmin:****@localhost/cinder

# RabbitMQ
rpc_backend = nova.rpc.impl_kombu
rabbit_host = seldon
rabbit_port = 5672
rabbit_userid = guest
rabbit_password = ****

[database]
# The SQLAlchemy connection string used to connect to the
# database (string value)
connection = mysql://cinderdbadmin:****@localhost/cinder

/etc/cinder/api-paste is:

#############
# OpenStack #
#############

[composite:osapi_volume]
use = call:cinder.api:root_app_factory
/: apiversions
/v1: openstack_volume_api_v1
/v2: openstack_volume_api_v2

[composite:openstack_volume_api_v1]
use = call:cinder.api.middleware.auth:pipeline_factory
noauth = faultwrap sizelimit noauth apiv1
keystone = faultwrap sizelimit authtoken keystonecontext apiv1
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext apiv1

[composite:openstack_volume_api_v2]
use = call:cinder.api.middleware.auth:pipeline_factory
noauth = faultwrap sizelimit noauth apiv2
keystone = faultwrap sizelimit authtoken keystonecontext apiv2
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext apiv2

[filter:faultwrap]
paste.filter_factory = cinder.api.middleware.fault:FaultWrapper.factory

[filter:noauth]
paste.filter_factory = cinder.api.middleware.auth:NoAuthMiddleware.factory

[filter:sizelimit]
paste.filter_factory = cinder.api.middleware.sizelimit:RequestBodySizeLimiter ...
(more)
edit retag flag offensive close merge delete

Comments

I found a partial fix. I had the rpc_backend wrong in cinder.conf. Now cinder-scheduler and cindor-api are starting, but I'm still seeing an (apparently non-fatal) "ArgsNotParsedError" in cinder-api log. I'm also still seeing the same error when running cinder list. Digging. I'm also seeing warnings logged as described at https://ask.openstack.org/en/question/7340/what-is-keymgrfixed_key-in-cinder/, but as far as I can tell these don't appear to be a fundamental problem.

gklyne gravatar imagegklyne ( 2014-01-20 01:54:46 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2014-01-20 05:58:15 -0500

gklyne gravatar image

updated 2014-01-20 06:00:52 -0500

My problems were caused by configuration file and Keystone data errors (surprise!)

  1. The failure to start of the Cinder services was caused by an incorrect rpc_backend value in cinder.conf

  2. The "Could not find any suitable endpoint. Correct region?" error was caused by incorrect and/or missing service and endpoint entries in Keystone. There were two problems in my setup: the cinder service entries had the wrong type (cut&paste error), and I had completely wiped my nova service+endpoint entries in Keystone, and had forgotten to reinstate them.

At this point, cinder list and nova list both give sensible empty responses.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-01-14 05:15:43 -0500

Seen: 871 times

Last updated: Jan 20 '14