Ask Your Question
0

trove instance stuck on build status

asked 2014-11-05 22:56:30 -0500

iqbal gravatar image

updated 2014-11-05 23:01:45 -0500

Hello stackers,

I try to configure trove on openstack juno with ubuntu 14.04, but when i try create instance, stuck on build status and got error log

ERROR trove.taskmanager.models [req-5b9e59de-086e-40c7-87da-35a69393ebdf 4b34d2aac92046e9adc54d0e661ec532 37dae8b619ee46a6951afaf0399bb187 - - -] Failed to send usage create-event for instance 87e49fd2-3333-4cdb-bd0d-bcc25036293f.
2014-11-06 11:42:22.161 2490 TRACE trove.taskmanager.models Unauthorized: Unauthorized (HTTP 401) (Request-ID: req-55b9a49f-3011-4f57-a45b-63d084742a63)
2014-11-06 11:47:49.417 2490 ERROR trove.openstack.common.periodic_task [req-5b9e59de-086e-40c7-87da-35a69393ebdf 4b34d2aac92046e9adc54d0e661ec532 37dae8b619ee46a6951afaf0399bb187 - - -] Error during Manager.publish_exists_event: The request you have made requires authentication. (HTTP 401)

Instance successfully created on nova but database instance still on build status.

I'm try to googling by my self but still can't fix that,

Thank you so much for your help

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2015-03-06 02:43:36 -0500

sailajap gravatar image

The trove instance is struck in BUILD state forever.Trove is installed manually and Openstack is installed with packstack on Centos7.

The below is the log in trove-guestagent.log file

2015-03-06 12:00:55.932 1122 CRITICAL root [-] Manager class not registered for datastore manager trove.guestagent start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name.

2015-03-06 12:00:56.044 1124 CRITICAL root [-] Manager class not registered for datastore manager trove.guestagent start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name.

2015-03-06 12:00:56.155 1126 CRITICAL root [-] Manager class not registered for datastore manager trove.guestagent start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name.

2015-03-06 12:00:56.265 1128 CRITICAL root [-] Manager class not registered for datastore manager trove.guestagent start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name.

2015-03-06 12:00:56.377 1130 CRITICAL root [-] Manager class not registered for datastore manager trove.guestagent start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name.

If there is no value set for datastore_manager then instead of 'trove.guestagent ' NONE is in the log file.

The below is the content in the trove-taskmanager log :

2015-03-06 01:56:37.117 8068 ERROR trove.openstack.common.periodic_task [req-43db8c18-294b-48c1-9cf8-ac208b72fa23 admin services - - -] Error during Manager.publish_exists_event: User 2f93bf68e5384c93a7bdd94a0a32f27e is unauthorized for tenant 088ab169b450476f93427d99efa4f9c9 (Disable debug mode to suppress these details.) (HTTP 401) 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task Traceback (most recent call last): 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task File "/usr/lib/python2.7/site-packages/trove/openstack/common/periodic_task.py", line 109, in run_periodic_tasks 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task task(self, context) 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task File "/usr/lib/python2.7/site-packages/trove/taskmanager/manager.py", line 157, in publish_exists_event 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task self.admin_context) 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task File "/usr/lib/python2.7/site-packages/trove/extensions/mgmt/instances/models.py", line 163, in publish_exist_events 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task notifications = transformer() 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task File "/usr/lib/python2.7/site-packages/trove/extensions/mgmt/instances/models.py", line 250, in __call__ 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task client=self.nova_client) 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task File "/usr/lib/python2.7/site-packages/trove/extensions/mgmt/instances/models.py", line 37, in load_mgmt_instances 2015-03-06 01:56:37.117 8068 TRACE trove.openstack.common.periodic_task mgmt_servers = client.servers.list(search_opts ... (more)

edit flag offensive delete link more
0

answered 2014-11-06 03:16:28 -0500

Check your configured RabbitMQ details once. It is unable to send the status like "VM came to ACTIVE state" to controller. So database entry is still in BUILD state. Check your keystone auth details and Rabbit MQ details.

edit flag offensive delete link more

Comments

I setup keystone on api-paste.ini [filter:authtoken], rabbit mq use correct config with valid host and password

iqbal gravatar imageiqbal ( 2014-11-06 03:56:18 -0500 )edit

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-11-05 22:56:30 -0500

Seen: 1,941 times

Last updated: Mar 06 '15