openstack team mailing list archive

[Ashutosh Narayan <aashutoshnarayan@xxxxxxxxx>]

Hi Eric,

Yes, I was able to create volumes after adding a new disk to the instance.
I then created a physical volume followed by volume group and all went fine
after that.

Thank you,

On Thu, May 9, 2013 at 3:55 PM, <Eric_E_Smith@xxxxxxxx> wrote:

> If you have a disk or partition that you can use to create that volume
> group then it might very well start working.  ****
>
> ** **
>
> *From:* Ashutosh Narayan [mailto:aashutoshnarayan@xxxxxxxxx]
> *Sent:* Thursday, May 09, 2013 5:20 AM
> *To:* Smith, Eric E
> *Cc:* openstack@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Openstack] [Grizzly] Unable to create volumes****
>
> ** **
>
> Hi Eric,****
>
> ** **
>
> Output of *pvscan *throws - "No matching physical volumes found"****
>
>
> Where else can I see ?****
>
> On Thu, May 9, 2013 at 3:40 PM, <Eric_E_Smith@xxxxxxxx> wrote:****
>
> Does pvscan show any disks assigned to the “cinder-volumes” volume group
> on any of your cinder nodes?  That’s the default volume group used for new
> volume creation.  ****
>
>  ****
>
> *From:* Openstack [mailto:openstack-bounces+eric_e_smith=
> dell.com@xxxxxxxxxxxxxxxxxxx] *On Behalf Of *Ashutosh Narayan
> *Sent:* Thursday, May 09, 2013 4:58 AM
> *To:* OpenStack
> *Subject:* [Openstack] [Grizzly] Unable to create volumes****
>
>  ****
>
> Hi folks,****
>
>  ****
>
> Am all set to launch an instance after getting good****
>
> response from this mailing list for most of my queries.****
>
> I am now facing issues in creating volumes from the****
>
> dashboard. Here is volume log file for reference :****
>
>  ****
>
> 2013-05-09 15:24:49    ERROR [cinder.service] Unhandled exception****
>
> Traceback (most recent call last):****
>
>   File "/usr/lib/python2.6/site-packages/cinder/service.py", line 224, in
> _start_child****
>
>     self._child_process(wrap.server)****
>
>   File "/usr/lib/python2.6/site-packages/cinder/service.py", line 201, in
> _child_process****
>
>     launcher.run_server(server)****
>
>   File "/usr/lib/python2.6/site-packages/cinder/service.py", line 95, in
> run_server****
>
>     server.start()****
>
>   File "/usr/lib/python2.6/site-packages/cinder/service.py", line 342, in
> start****
>
>     self.manager.init_host()****
>
>   File "/usr/lib/python2.6/site-packages/cinder/volume/manager.py", line
> 143, in init_host****
>
>     self.driver.check_for_setup_error()****
>
>   File "/usr/lib/python2.6/site-packages/cinder/volume/drivers/lvm.py",
> line 78, 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****
>
>  ****
>
> It says - volume group cinder-volume does not exist.****
>
> But /etc/cinder/cinder.conf has volume group set to cinder-volumes.****
>
> Here is a snippet of cinder.conf :****
>
> [..]****
>
> verbose=False****
>
> rabbit_port=5672****
>
> rabbit_password=****
>
> volume_group=cinder-volumes****
>
> rabbit_host=127.0.0.1****
>
> iscsi_ip_address=192.168.105.67****
>
> [..]****
>
>  ****
>
> Any pointers on how to trouble shoot this issue.****
>
> I have also followed this bug -
> https://bugs.launchpad.net/openstack-manuals/+bug/1078353****
>
>  ****
>
> Thank you,****
>
>  ****
>
> -- ****
>
> Ashutosh Narayan
>
> http://ashutoshn.wordpress.com/****
>
>
>
> ****
>
> ** **
>
> --
> Ashutosh Narayan
>
> http://ashutoshn.wordpress.com/****
>



-- 
Ashutosh Narayan

http://ashutoshn.wordpress.com/