Ask Your Question

Trove instance went to ERROR because of "chmod: cannot access '/etc/guest_info': No such file or directory"

asked 2015-10-27 11:06:38 -0500

Lili Zhang gravatar image

updated 2015-10-27 21:40:46 -0500

When I tried to launch a Trove database instance with the image built by DIB, the Trove instance went to ERROR, while its associated Nova instance went to ACTIVE. So I logged in that VM and found the following information in log files.

In /var/log/upstart/trove-guest.log, the error is as follows.

chmod: cannot access '/etc/guest_info': No such file or directory

I also looked at /var/log/boot.log and found the following, which really confused me. It seems that Trove Guest started successfully and then failed.

   * Starting Trove Guest^[[74G[ OK ]
    Cloud-init v. 0.7.5 running 'modules:config' at Tue, 27 Oct 2015 08:47:33 +0000. Up 151.77 seconds.
   * Starting Trove Guest^[[74G[^[[31mfail^[[39;49m]*

And on the guest VM, the Trove source code and database server package (here I used Vertica) can be found under ~/trove and /opt/vertica, respectively.

The following is some details about how OpenStack and Trove are installed, and also how Trove guest database image is built.

OpenStack environment: initially installed following OpenStack Installation Guide for Ubuntu - JUNO, and then upgraded to KILO. After upgrade, a Nova instance was launched successfully. And by checking "nova-manage --version", the output is "2015.1.1". So I made judgment that the upgrade was successful. There are the following service running on OpenStack: Keystone, Nova, Glance, Cinder, Horizon.

Trove: after upgrading OpenStack from JUNO to KILO, installed Trove, following Chapter " Add Database Service" in (OpenStack Installation Guide for Ubuntu - ICEHOUSE) and with updated configurations found in KILO. After installation, I executed "trove list" and got right output (a table with columns: ID, Name, Datastore, Datastore Version, Status, Flavor ID, Size). And by checking "trove-manage --version", the output is "2015.1.0". So I made the judgement that trove was installed successfully.

(I accidentally installed Trove using root role. I don't have the ability to judge whether that would have influence on the issue I encountered. Appreciate any comment on this.)

Trove guest database image creation: used DIB tool; the details can be found below.

-----Install pre-requisition:

# sudo apt-get install qemu-utils kpartx

-----Install diskimage-builder:

# sudo pip install diskimage-builder

-----Install trove-integration and tripleo-image-elements:

$ git clone

$ git clone

-----And then copy trove-integration/scripts/files/keys/ to ~/.ssh and change file permission. So Trove guest instance can be accessed via ssh.

-----Configure following environmental variables with local values.

export PATH_TROVE    
export SSH_DIR   
export GUEST_LOGDIR   

-----Create the image:

$ disk-image-create -a amd64 -o ~/images/ubuntu_vertica/ubuntu_vertica -x --qemu-img-options compat=0.10 ubuntu apt-sources vm heat-cfntools cloud-init-datasources ubuntu-guest ubuntu-vertica

-----And then register that image with GLANCE and update the datastore version.

Please feel free to let me know if you need any additional information. Thank you for your time ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

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

Lili Zhang gravatar image

In case others also have this problem, just provide the solution I figured out one month ago. It is a problem related to Nova in my OpenStack environment. See here.

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


Asked: 2015-10-27 04:17:53 -0500

Seen: 393 times

Last updated: Dec 22 '15