Following up on this issue. The root cause were errors in the cinder.conf file. Specifically using "connection" instead of "sql_connection" in the [DEFAULT] section. "connection" only works under the "[database]" section. The reason for these syntax errors: the script that generated etc/cinder/cinder.conf.sample in the 2013.2.3 release did not correctly place configuration options under subsections.
I have filed a bug: https://bugs.launchpad.net/cinder/+bug/1316684 On Fri, May 2, 2014 at 7:01 PM, Scott Devoid <[email protected]> wrote: > Hi all, > > I am having trouble deploying a second cinder-volume service on our Havana > system (2013.2.3). > $ cinder service-list > > +------------------+---------+------+---------+-------+----------------------------+ > | Binary | Host | Zone | Status | State | Updated_at > | > > +------------------+---------+------+---------+-------+----------------------------+ > | cinder-scheduler | u10-p | nova | enabled | down | > 2014-05-02T23:33:17.000000 | > | cinder-scheduler | u11-p | nova | enabled | up | > 2014-05-02T23:55:12.000000 | > | cinder-volume | v1-p | nova | enabled | up | > 2014-05-02T23:55:19.000000 | > > +------------------+---------+------+---------+-------+----------------------------+ > > New volume server is on v2-p. After configuring, I start up cinder-volume > and get this output from the logs http://paste.openstack.org/show/78467/ > > On the AMQP server "internal-rabbit" I see that the service creates some > queues: > $ rabbitmqctl list_queues -p /havana_h1 | grep cinder > cinder-scheduler:u11-p 0 > cinder-volume_fanout_9a146f9bf00a6b2898f3bd3abbc520f6 0 > cinder-volume:v2-p 0 > cinder-scheduler:u10-p 0 > cinder-scheduler 0 > cinder-volume:v1-p 0 > cinder-scheduler_fanout_ff6e60da1fe54ebc99a9c0af3f5e977a 0 > > However, the service does not appear in the database "services" table. > I've tested my MySQL and Keystone credentials and I am able to query both > from v2-p. > > I am not sure how to debug it from here, I've turned SQL's > "connection_debug=100" and turned on debugging and verbose logging. No > errors or messages that indicate the problem. :-/ > > Thanks for the help! > ~ Scott >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
