Ask Your Question

Atreyee's profile - activity

2017-01-04 07:23:39 -0500 received badge  Good Question (source)
2016-12-06 06:12:45 -0500 received badge  Nice Question (source)
2013-08-21 05:40:41 -0500 received badge  Nice Answer (source)
2013-08-18 05:30:18 -0500 received badge  Nice Question (source)
2013-07-02 21:48:28 -0500 received badge  Famous Question (source)
2013-07-01 14:38:25 -0500 received badge  Famous Question (source)
2013-06-24 09:16:53 -0500 received badge  Notable Question (source)
2013-06-21 13:56:03 -0500 received badge  Popular Question (source)
2013-06-19 10:53:06 -0500 received badge  Notable Question (source)
2013-06-18 15:37:38 -0500 asked a question Cinder: Volumes are getting created with ERROR status

I have done the Grizzly instalaltion following the document available on : https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/master/OpenStack_Grizzly_Install_Guide.rst

========================

I have created a cinder volume from the UI and found that the status of the volume is ERROR.

Here is the output: root@agupta-Studio-1458:/etc/cinder# cinder list +--------------------------------------+--------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+--------+--------------+------+-------------+----------+-------------+ | d5b6480d-38ac-49c6-9365-e1780a672505 | error | v1 | 5 | None | false | |

+--------------------------------------+--------+--------------+------+-------------+----------+-------------+

When i look into the cinder-volumes log then i can see the following:

================== root@agupta-Studio-1458:/# cinder-volume --debug --verbose

2013-06-18 16:32:32 INFO [cinder.service] Starting 1 workers 2013-06-18 16:32:32 INFO [cinder.service] Started child 5341 2013-06-18 16:32:32 AUDIT [cinder.service] Starting cinder-volume node (version 2013.1.1) 2013-06-18 16:32:32 DEBUG [cinder.utils] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name 2013-06-18 16:32:33 ERROR [cinder.service] Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 224, in _start_child self._child_process(wrap.server) File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 201, in _child_process launcher.run_server(server) File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 95, in run_server server.start() File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 342, in start self.manager.init_host() File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 143, in init_host self.driver.check_for_setup_error() File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py", line 81, in check_for_setup_error raise exception.VolumeBackendAPIException(data=exception_message) VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: volume group cinder-volumes doesn't exist 2013-06-18 16:32:33 INFO [cinder.service] Child 5341 exited with status 2 2013-06-18 16:32:33 INFO [cinder.service] Started child 5345 2013-06-18 16:32:33 AUDIT [cinder.service] Starting cinder-volume node (version 2013.1.1) 2013-06-18 16:32:33 DEBUG [cinder.utils] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name 2013-06-18 16:32:33 ERROR [cinder.service] Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 224, in _start_child self._child_process(wrap.server) File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 201, in _child_process launcher.run_server(server) File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 95, in run_server server.start() File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 342, in start self.manager.init_host() File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 143, in init_host self.driver.check_for_setup_error() File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py", line 81, in check_for_setup_error raise exception.VolumeBackendAPIException(data=exception_message) VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: volume group cinder-volumes doesn't exist

=============

Please let me know if i am missing something or this could be a potential bug ?

Regards Atreyee

2013-06-17 19:14:22 -0500 received badge  Student (source)
2013-06-17 19:13:55 -0500 received badge  Self-Learner (source)
2013-06-17 19:13:55 -0500 received badge  Teacher (source)
2013-06-17 16:53:33 -0500 received badge  Popular Question (source)
2013-06-17 16:53:22 -0500 answered a question Unable to login into Horizon (Error 500)

I have changed the COMPRESS_OFFLINE = False in the /etc/openstack-dashboard/local_settings.py and rebooted the machine.

2013-06-17 09:50:01 -0500 answered a question Unable to login into Horizon (Error 500)

The problem resolved with the reboot after changing the parameter
COMPRESS_OFFLINE = False in the /etc/openstack-dashboard/local_settings.py and rebooted the machine.

2013-06-16 22:59:00 -0500 asked a question Unable to login into Horizon (Error 500)

I am installing the Openstack Grizzly and after configuring all the steps when i am trying to connect to the "IP_ADDRESS/horizon" then i am getting the internal server error 500.

I have changed the COMPRESS_OFFLINE = False in the /etc/openstack-dashboard/local_settings.py file but that also didn't solve the problem.

I couldn't fine much into the apache server log apart from the missing favicon.ico file. This file is not there in my machine so is that is the potential cause? I am using the this guide to install Grizzly:

Please let me know if there is some work around or i am missing anything.