Ask Your Question

Ekalaya's profile - activity

2017-05-26 22:45:24 -0500 commented question Can't attach volume to an instance

hi @eblock. sorry for late reply. Please see updated question

2017-05-22 08:35:17 -0500 commented question Can't attach volume to an instance

@eblock. Yes, there is nothing in compute node, but if I check in cinder node, there are some volumes there (please see updated question). I can upload any images or create volume(s). The problem is attaching volume to an instance always fails.

2017-05-21 23:35:01 -0500 commented question Can't attach volume to an instance

@eblock, please see updated question

2017-05-14 00:02:28 -0500 received badge  Famous Question (source)
2017-05-14 00:02:23 -0500 received badge  Enthusiast
2017-05-12 20:32:48 -0500 commented question Can't attach volume to an instance

@eblock output of virsh secret-list

ubuntu@pumped-perch:~$ virsh secret-list
 UUID                                  Usage
--------------------------------------------------------------------------------
 514c9fca-8cbe-11e2-9c52-3bc8c7819472  ceph client.nova-compute-kvm secret
2017-05-12 10:19:57 -0500 answered a question Instance fails to launch when image is boot source

@brotherchris regarding to https://help.landscape.canonical.com/LDS/ReleaseNotes17.03 (https://help.landscape.canonical.com/...) your problem is one of the known-issues. I solved this issue by creating new image and launching instance with that new image. You have to uncheck 'create new volume' when launching the instance (ref: https://bugs.launchpad.net/landscape/+bug/1644923 (https://bugs.launchpad.net/landscape/...))

2017-05-11 23:16:23 -0500 received badge  Editor (source)
2017-05-11 19:56:36 -0500 commented question Instance fails to launch when image is boot source

@brotherchris you are awesome. thank you so much ! it works perfectly

2017-05-11 04:03:57 -0500 received badge  Notable Question (source)
2017-05-10 09:40:27 -0500 commented question Instance fails to launch when image is boot source

I am having the same problem and I don't know where have to find out. May I know how did you get nova.conf via Juju?

2017-05-10 09:37:05 -0500 received badge  Popular Question (source)
2017-05-10 04:44:22 -0500 commented question Can't attach volume to an instance

thank you @Bernd Bausch for your link. It's true our setup was automatic that's why I dont know much about how openstack and it's all technologies operate and relate each other

2017-05-10 04:10:30 -0500 commented question Can't attach volume to an instance

I will try debug logging facility later and report it here.

2017-05-10 01:32:18 -0500 commented question Can't attach volume to an instance

How can I turn debug logging facility on? I am sorry, I am new to openstack. Thank you for your comment

2017-05-09 08:17:05 -0500 answered a question Message No valid host was found. There are not enough hosts available. Code 500

I had same problem and managed to solve it by trying to launch instance without volume (in openstack dashboard choose 'No' in Create new volume option).

2017-05-09 08:17:04 -0500 asked a question Can't attach volume to an instance

I have managed to deploy Openstack on 6 machines using Landscape Autopilot. I can create instances (without volume) and other things.

It seems works well until I try to attach volume to an instance through Horizon or Openstack client CLI. It always failed. In Horizon, there are no error messages.

Similar problem happens when I try to create an instance with volume. In this case, there was an error message said:

"Error: Failed to perform requested operation on instance "xxxxxx" the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available]"

For additional informations I was using Ubuntu 16.04, MAAS version 2.1.3, Juju version 2.1.2 and conjure-up as tools to deploy Openstack.

Please help me. It has been 1 month since I managed to deploy Openstack, this problem has not been solved at all.

UPDATED
Here is the output of cinder service-list:

emtres01@maas:~$ cinder service-list 
+------------------+---------------------+------+---------+-------+ 
|      Binary      |         Host        | Zone |  Status | State |  
+------------------+---------------------+------+---------+-------+ 
| cinder-scheduler | juju-b6bb75-1-lxd-3 | nova | enabled |   up  | 
|  cinder-volume   |     cinder@CEPH     | nova | enabled |   up  | 
+------------------+---------------------+------+---------+-------+ 
emtres01@maas:~$

and here is the nova.log that showed up when I tried to attach volume to an instance

2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [req-c2ea4390-c703-4981-ad28-4dce61d6d7de ae67e9e8fc51406fb890389fd06e44af 18483cc44c884278b94bf3bb41421175 - - -] [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63] Failed to attach volume at mountpoint: /dev/vdb
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63] Traceback (most recent call last):
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 1232, in attach_volume
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]     guest.attach_device(conf, persistent=True, live=live)
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/guest.py", line 304, in attach_device
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]     device_xml = conf.to_xml()
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/config.py", line 77, in to_xml
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]     root = self.format_dom()
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/config.py", line 765, in format_dom
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]     uuid=self.auth_secret_uuid))
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "src/lxml/lxml.etree.pyx", line 2998, in lxml.etree.Element (src/lxml/lxml.etree.c:80607)
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "src/lxml/apihelpers.pxi", line 135, in lxml.etree._makeElement (src/lxml/lxml.etree.c:17604)
2017-05-13 01:46:26.346 374296 ERROR nova.virt.libvirt.driver [instance: 6d58f5b7-dbd0-4ae5-9c40-fd902a0d9a63]   File "src/lxml/apihelpers.pxi", line ...
(more)