yahoo-eng-team team mailing list archive

[Robert Collins <1398588@xxxxxxxxxxxxxxxxxx>]

Closing (its two weeks later and Patrick hasn't reported reproduction).
Please re-open if it is in fact still an issue.

** Changed in: nova
       Status: Incomplete => Invalid

** Changed in: cinder
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1398588

Title:
  volume_attach action registers volume attachment even on failure

Status in Cinder:
  Invalid
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When attaching volumes to instances, if the volume attachment fails, it is still noted as successful by the system in some cases.
  This is the information reflected when requesting the details of a servers volume attachments
  http://developer.openstack.org/api-ref-compute-v2-ext.html
  /v2/​{tenant_id}​/servers/​{server_id}​/os-volume_attachments
  Show volume attachment details

  In the example, I have 2 test servers and 1 test volume.
  I attach the volume to test_server1 and it is successful (though please see: https://bugs.launchpad.net/cinder/+bug/1398583)
  Next, I try to attach the same volume to test_server2.
  This call fails as expected, but the mountpoint / attachment is still registered.

  To demonstrate, I repeat the previous call.  It fails again, but this
  time due to the requested mountpoint being in-use vs. the volume being
  attached.

  I next make a call to list the volume attachments for test_server2.
  It lists volume attachments even though there are none and the Cinder
  api server does not register this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1398588/+subscriptions