Ask Your Question
0

cinder unable to attach volume to instances when used nfs driver

asked 2017-03-30 07:53:07 -0500

AbuAyesha gravatar image

I didn't see any errors in the log files. All the services are up and running fine. When I tried attach volume to instance saying status attaching and finally it is available state only. When I checked in the log Initialization of volume is success and immediately terminated volume successfully.

2017-03-30 08:49:36.175 6711 INFO cinder.volume.manager [req-3074bc12-4680-4788-8cd1-a9a2803c9a7b e4121c85c5104f05be55d2eedd305701 05568f5a7acd41a9833a523852f14a3b - - -] Initialize volume connection completed successfully. 2017-03-30 08:49:36.368 6711 INFO cinder.volume.manager [req-a5521e18-7898-4213-9cc3-6ecf277bbdbf e4121c85c5104f05be55d2eedd305701 05568f5a7acd41a9833a523852f14a3b - - -] Terminate volume connection completed successfully.

Below is for reference....

[root@controller-openstack ~(keystone_admin)]# nova volume-list WARNING: Command volume-list is deprecated and will be removed after Nova 13.0.0 is released. Use python-cinderclient or openstackclient instead. +--------------------------------------+-----------+--------------+------+-------------+-------------+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--------------------------------------+-----------+--------------+------+-------------+-------------+ | 2f475b76-76dc-4ae6-ada0-3841c8e71bda | available | | 1 | nfstype | | +--------------------------------------+-----------+--------------+------+-------------+-------------+ [root@controller-openstack ~(keystone_admin)]# nova volume-attach Gitlab-ElastiSearch1 2f475b76-76dc-4ae6-ada0-3841c8e71bda +----------+--------------------------------------+ | Property | Value | +----------+--------------------------------------+ | device | /dev/vdb | | id | 2f475b76-76dc-4ae6-ada0-3841c8e71bda | | serverId | 0a424eb6-e923-4271-90c8-9ea9b2a145b1 | | volumeId | 2f475b76-76dc-4ae6-ada0-3841c8e71bda | +----------+--------------------------------------+ [root@controller-openstack ~(keystone_admin)]# nova volume-list WARNING: Command volume-list is deprecated and will be removed after Nova 13.0.0 is released. Use python-cinderclient or openstackclient instead. +--------------------------------------+-----------+--------------+------+-------------+-------------+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--------------------------------------+-----------+--------------+------+-------------+-------------+ | 2f475b76-76dc-4ae6-ada0-3841c8e71bda | available | | 1 | nfstype | | +--------------------------------------+-----------+--------------+------+-------------+-------------+

Please do the needful.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-10-17 06:33:23 -0500

MustafaArif gravatar image

updated 2017-10-17 06:34:16 -0500

Please check if your compute nodes are able to access the nfs share by using showmount -e NFSIP This happens when your compute nodes are not able reach to your nfs share. Possible cause of this issue can be

  1. Firewall preventing the connection
  2. NFS server is not configured correctly
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-03-30 07:53:07 -0500

Seen: 198 times

Last updated: Oct 17 '17