same behavior in ec2-api. Some attached volumes have empty attached

Request to cinder for attach volume -

and then this volume has status 'in-use' and empty attachments list.

** Also affects: ec2-api
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  Generic driver fails to attach Cinder volume to Nova VM

Status in Cinder:
Status in ec2-api:
Status in Manila:
  In Progress
Status in OpenStack Compute (nova):

Bug description:
  Starting from 14th of October, Friday. Our CI jobs (Manila) with
  Generic driver (Cinder as backend) started failing with traces [1].

  Investigation showed that problem appears when we get volume from Cinder with 
"in-use" status but with empty attachments.
  And Nova considers it as attached, but Cinder does not. And it is not 
attached indeed.
  After all, it is impossible to detach "in-use" volume [4].
  It is not stable bug. It is concurrency-based bug. If we can do something in 
Manila then wait some time after each operation we do...

  Test gerrit change [2] proves that commit to Cinder [3] is THE CAUSE
  of a bug.

  Also, bug was reproduced even before merge of [3] with "gate-rally-
  dsvm-cinder" CI job [4], but, I assume, no one has paid attention to
  this. And this job fails from time to time exactly because of this [3]

  Local testing shows that IF bug appears then volume never gets
  attached and list of attachments stays empty. And waiting between
  'create' (wait until 'available' status) and 'attach' commands does
  not help at all.

  How to reproduce:
  1) Create VM
  2) Create Volume
  3) Attach volume (2) to the VM (1)
  4) Repeat steps 1-3 while bug does not appear.



  ( )


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to