OpenStack Heat

multiattach volume fails if status is attaching

Bug #1606464 reported by Rob Saunders
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
Undecided
Unassigned
OpenStack Heat no-milestone-taged-bugs

Bug Description

This is a duplicate of https://bugs.launchpad.net/heat/+bug/1395468 however that has expired unresolved and this still appears to be an issue.

These are the Heat resources in use:
 OS::Cinder::VolumeAttachment (x2)
 OS::Nova::Server (x2)
 OS::Cinder::Volume (x1)

When using heat and creating a cinder volume with multiattach=true, the stack create fails if second volume attachment detects that the first volume attachment is in an "attaching" state. The attachment reports an error as shown below:

Error: resources.vol_att_1: Failed to attach volume 0a767750-xxxx-xxxx-xxxx-1440adac7552 to server bd9c3696-xxxx-xxxx-xxxx-8f61525a1948 - Invalid volume: volume '0a767750-xxxx-xxxx-xxxx-1440adac7552' status must be 'available'. Currently in 'attaching' (HTTP 400) (Request-ID: req-1aa3aafe-xxxx-xxxx-xxxx-5140f168c407)

What should happen is that the second volume attachment waits until the first attachment is in a state of available, in-use, or failed before re-attempting to connect.

This occurs on Openstack Mitaka on CentOS7.0 with the following software:

openstack-cinder.noarch 1:8.0.0-1.el7 @centos-openstack-mitaka
openstack-heat-api.noarch 1:6.0.0-1.el7 @centos-openstack-mitaka
openstack-heat-api-cfn.noarch 1:6.0.0-1.el7 @centos-openstack-mitaka
openstack-heat-common.noarch 1:6.0.0-1.el7 @centos-openstack-mitaka
openstack-heat-engine.noarch 1:6.0.0-1.el7 @centos-openstack-mitaka
openstack-nova-api.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
openstack-nova-common.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
openstack-nova-compute.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
openstack-nova-conductor.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
openstack-nova-console.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
openstack-nova-novncproxy.noarch
openstack-nova-scheduler.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
python-cinder.noarch 1:8.0.0-1.el7 @centos-openstack-mitaka
python-cinderclient.noarch 1.6.0-1.el7 @centos-openstack-mitaka
python-heatclient.noarch 1.0.0-1.el7 @centos-openstack-mitaka
python-nova.noarch 1:13.1.0-1.el7 @centos-openstack-mitaka
python-novaclient.noarch 1:3.3.1-1.el7 @centos-openstack-mitaka

Attached: yaml template file

Revision history for this message
Rob Saunders (robsaundmisc) wrote :
Revision history for this message
huangtianhua (huangtianhua) wrote :

Although we support the property 'multiattach' for cinder volume resource, but nova has not support to attach a volume to several servers yet, so the error raised.

Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.