RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1158015 - Post installation, Cinder fails with an error: Volume group "cinder-volumes" not found
Summary: Post installation, Cinder fails with an error: Volume group "cinder-volumes" ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: Juno
Assignee: Martin Magr
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-28 10:06 UTC by Nir Magnezi
Modified: 2019-09-10 14:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:45:06 UTC
Embargoed:


Attachments (Terms of Use)
cinder traces (14.93 KB, text/plain)
2014-10-28 10:10 UTC, Nir Magnezi
no flags Details

Description Nir Magnezi 2014-10-28 10:06:22 UTC
Description of problem:
=======================
I used packstack[1] to deploy openstack.
cinder fails to create volumes with several errors:

1. IOError: Socket closed --> Seems related to AMQP
2. Stderr: u'  Volume group "cinder-volumes" not found\n  Skipping volume group cinder-volumes\n'


[1] openstack-packstack-2014.2-0.4.dev1266.g63d9c50.el7.centos.noarch

Version-Release number of selected component (if applicable):
=============================================================
RDO-Juno
openstack-cinder-2014.2-1.el7.centos.noarch

How reproducible:
=================
2/2

Steps to Reproduce:
===================
1. Post installation, Try to create a volume with cinder
   # cinder create 2

Actual results:
===============
# cinder show 9f1f7a2e-df2d-4649-8085-073cad8a0de2
+---------------------------------------+--------------------------------------+
|                Property               |                Value                 |
+---------------------------------------+--------------------------------------+
|              attachments              |                  []                  |
|           availability_zone           |                 nova                 |
|                bootable               |                false                 |
|               created_at              |      2014-10-28T09:07:07.000000      |
|          display_description          |                 None                 |
|              display_name             |               Test_Vol               |
|               encrypted               |                False                 |
|                   id                  | 9f1f7a2e-df2d-4649-8085-073cad8a0de2 |
|                metadata               |                  {}                  |
|         os-vol-host-attr:host         |                 None                 |
|     os-vol-mig-status-attr:migstat    |                 None                 |
|     os-vol-mig-status-attr:name_id    |                 None                 |
|      os-vol-tenant-attr:tenant_id     |   0975bd5a342145bba55e8b8d20495881   |
|   os-volume-replication:driver_data   |                 None                 |
| os-volume-replication:extended_status |                 None                 |
|                  size                 |                  1                   |
|              snapshot_id              |                 None                 |
|              source_volid             |                 None                 |
|                 status                |                error                 |
|              volume_type              |                 None                 |
+---------------------------------------+--------------------------------------+

Expected results:
=================
Cinder should be able to function with no issues.

Additional info:
================
Cinder related configs from packstack answer file (used defaults):
CONFIG_CINDER_INSTALL=y
CONFIG_CINDER_DB_PW=123456
CONFIG_CINDER_KS_PW=123456
CONFIG_CINDER_BACKEND=lvm
CONFIG_CINDER_VOLUMES_CREATE=y
CONFIG_CINDER_VOLUMES_SIZE=20G
CONFIG_CINDER_GLUSTER_MOUNTS=
CONFIG_CINDER_NFS_MOUNTS=
CONFIG_CINDER_NETAPP_LOGIN=
CONFIG_CINDER_NETAPP_PASSWORD=
CONFIG_CINDER_NETAPP_HOSTNAME=
CONFIG_CINDER_NETAPP_SERVER_PORT=80
CONFIG_CINDER_NETAPP_STORAGE_FAMILY=ontap_cluster
CONFIG_CINDER_NETAPP_TRANSPORT_TYPE=http
CONFIG_CINDER_NETAPP_STORAGE_PROTOCOL=nfs
CONFIG_CINDER_NETAPP_SIZE_MULTIPLIER=1.0
CONFIG_CINDER_NETAPP_EXPIRY_THRES_MINUTES=720
CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_START=20
CONFIG_CINDER_NETAPP_THRES_AVL_SIZE_PERC_STOP=60
CONFIG_CINDER_NETAPP_NFS_SHARES_CONFIG=
CONFIG_CINDER_NETAPP_VOLUME_LIST=
CONFIG_CINDER_NETAPP_VFILER=
CONFIG_CINDER_NETAPP_VSERVER=
CONFIG_CINDER_NETAPP_CONTROLLER_IPS=
CONFIG_CINDER_NETAPP_SA_PASSWORD=
CONFIG_CINDER_NETAPP_WEBSERVICE_PATH=/devmgr/v2
CONFIG_CINDER_NETAPP_STORAGE_POOLS=

Comment 1 Nir Magnezi 2014-10-28 10:08:07 UTC
Workaround: restarting cinder services seems to resolve it.

Comment 4 Nir Magnezi 2014-10-28 10:10:49 UTC
Created attachment 951345 [details]
cinder traces

Comment 5 Alan Pevec 2014-10-28 11:16:17 UTC
> 2. Stderr: u'  Volume group "cinder-volumes" not found\n  Skipping volume
> group cinder-volumes\n'

When does that happen, during installation or later i.e is this bug 1148552 or different issue?

Comment 6 Nir Magnezi 2014-10-28 12:47:37 UTC
(In reply to Alan Pevec from comment #5)
> > 2. Stderr: u'  Volume group "cinder-volumes" not found\n  Skipping volume
> > group cinder-volumes\n'
> 
> When does that happen, during installation or later i.e is this bug 1148552
> or different issue?

it happens after installation.
it Does not seem like bug #1148552, Comment #4 workaround solves it.

Comment 7 Eric Harney 2014-10-28 14:27:39 UTC
If cinder-volumes isn't found, that will cause the volume driver to be uninitialized at startup time, which is why the create volume request fails later.

If the cinder-volumes VG isn't present when the volume service starts, that sounds like a packstack issue -- it shouldn't start the service before creating the VG.

Comment 8 Chandan Kumar 2016-05-19 15:45:06 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.