Ask Your Question
0

Trove instance stuck at BUILD

asked 2015-12-12 19:34:05 -0500

xionglingfeng gravatar image

I installed Trove (liberty) on Ubuntu 15.04 from Ubuntu official repository. When I create an instance, it stucked at BUILD status. I checked log files in both controller node and Trove instance. Within the instance, trove-guestagent.log said:

2015-12-13 01:30:45.277 1561 DEBUG trove.conductor.api [-] Making async call to cast heartbeat for instance: None heartbeat /usr/lib/python2.7/dist-packages/trove/conductor/api.py:48

In the controller node, trove-conductor.log said:

2015-12-12 21:59:45.282 3306 ERROR oslo_messaging.rpc.dispatcher ModelNotFoundError: InstanceServiceStatus Not Found

I searched around, most threads said that the problem is guest_info is not injected to instance. But I do have /etc/trove/conf.d/guest_info.conf in my instance. tenant_id in the file is correct, but the funny thing is the guest_id does not match the instance UUID. Every time I create a new instance, guest_id changed, but never match the instance UUID in nova.

[DEFAULT]
guest_id=b3bfdf0e-33c5-4c09-9660-85c236352be0
datastore_manager=mysql
tenant_id=d79d7b229d8c4502a571d1c871c87b5f

Any suggestions?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2015-12-22 09:39:18 -0500

Lili Zhang gravatar image

updated 2016-06-02 03:22:00 -0500

First of all, guest_id is the instance id in Trove, not the instance id in Nova, since it is Trove taskmanager that injects it. Through trove command line "trove list", you will find that the listed instance id matches guest_id in the guest_info.conf.

Your problem may be caused by the fact that trove-guestagent cannot get guest_id, although it is there. If you check trove-guestagent.log and search guest_id in it, you may find its value as None. If so, fix the problem by adding /etc/trove/conf.d/guest_info.conf as a configuration file for running trove-guestagent. The details can be found below.

On the database guest image, edit the /etc/init/trove-guestagent.conf file as follows.

--exec /usr/bin/trove-guestagent -- --config-file=/etc/trove/conf.d/guest_info.conf --config-file=/etc/trove/trove-guestagent.conf ${DAEMON_ARGS}

Hope this is helpful.

edit flag offensive delete link more

Comments

both trove-conductor.log and trove-guestagent.log are already posted in thread. Thank you for your explanation about the guest_id part. The id is correct.

xionglingfeng gravatar imagexionglingfeng ( 2015-12-29 00:56:16 -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

Stats

Asked: 2015-12-12 19:34:05 -0500

Seen: 670 times

Last updated: Jun 02 '16