Host VM goes unreachable after trove instance create

Bug #1336797 reported by Rajalakshmi Ganesan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Expired
Wishlist
Unassigned

Bug Description

Description: Base VM on which trove is installed goes unreachable on DB instance creation.

Steps to reproduce:

1. Setup Devstack with trove enabled.
2. Create a trove instance using the following command:
venkater@devstack-trove:~/devstack$ trove create ps_test 2 --size 1
+-------------------+--------------------------------------+
| Property | Value |
+-------------------+--------------------------------------+
| created | 2014-07-02T13:06:51 |
| datastore | mysql |
| datastore_version | 5.5 |
| flavor | 2 |
| id | b09b94fe-0dd6-47bf-966a-e66af4a019cf |
| name | ps_test |
| status | BUILD |
| updated | 2014-07-02T13:06:51 |
| volume | 1 |
+-------------------+--------------------------------------+
venkater@devstack-trove:~/devstack$
3. Wait for a while (about 10 seconds) and then ping the host VM on which trove was installed.

Expected Result:
The host VM should be reachable and we must be able to list the trove instance.

Actual Result:
The host VM becomes unreachable and we are unable to ping/ssh into the VM.

Please find the attached log of trove manager. (tr-tmgr)

Revision history for this message
Rajalakshmi Ganesan (rajalakshmi-ganesan) wrote :
Revision history for this message
Amrith Kumar (amrith) wrote :

Using your setup, are you able to launch a nova instance and then ssh into it?

Revision history for this message
Nikhil Manchanda (slicknik) wrote :

Hi Rajalakshmi:
Can you add the trove public key (can be found at https://github.com/openstack/trove-integration/blob/master/scripts/files/keys/authorized_keys) to the ~/.ssh/authorized_keys, and try again?

Thanks,
Nikhil

Revision history for this message
Rajalakshmi Ganesan (rajalakshmi-ganesan) wrote :

Hi Amrith,

No I am not able to launch a nova instance also. The VM goes unreachable even on launching a nova instance.

Regards,
Rajalakshmi Ganesan

Revision history for this message
Rajalakshmi Ganesan (rajalakshmi-ganesan) wrote :

Hi Nikhil,

Yes I added the public key you mentioned and tried to boot trove instance again. But still the VM goes unreachable after "trove create" command.

Regards,
Rajalakshmi Ganesan

Revision history for this message
Amrith Kumar (amrith) wrote :

Hi Rajalakshmi:

If you are unable to boot a nova instance, the issue isn't with trove. Trove depends on nova.

So, for debugging purposes, it would be best to first understand why nova won't launch an instance.

What do you see when you run these three commands?

nova list
nova flavor-list
glance image-list

Revision history for this message
Nikhil Manchanda (slicknik) wrote :

It looks like your actual eth0 IP is part of the FIXED_IP range that is being used in devstack. This seems like a networking misconfiguration. Please use a different FIXED_IP range for your devstack install.

Changed in trove:
status: New → Incomplete
Changed in trove:
importance: Undecided → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Trove because there has been no activity for 60 days.]

Changed in trove:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.