yahoo-eng-team team mailing list archive

[Bob Ball <1502929@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There is a bug when connecting to Cinder volumes over iSCSI with XenAPI
where a tapdisk is not correctly spawned.  This has been fixed in
https://github.com/xapi-
project/sm/commit/7a8a158493d03ceeb31bc8a43b7f213e74420bf0 however,
users of XenServer 6.5 need a workaround in Nova.

The impact of this is that, without the fix, XAPI is expecting a tapdisk
to be spawned, but the Storage Manager does not spawn one.  As such, the
VM will not be able to connect to this Cinder volume.

The correct fix in Nova is to emulate the above commit for users of
XenServer 6.5; i.e. set the backend-kind=vbd.  This will ensure that the
storage manager spawns a tapdisk, and that it can be attached in the
correct way

** Affects: nova
     Importance: Medium
     Assignee: Bob Ball (bob-ball)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Bob Ball (bob-ball)

** Changed in: nova
   Importance: Undecided => Medium

-- 
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/1502929

Title:
  XenServer 6.5 fails to attach to Cinder volumes

Status in OpenStack Compute (nova):
  New

Bug description:
  There is a bug when connecting to Cinder volumes over iSCSI with
  XenAPI where a tapdisk is not correctly spawned.  This has been fixed
  in https://github.com/xapi-
  project/sm/commit/7a8a158493d03ceeb31bc8a43b7f213e74420bf0 however,
  users of XenServer 6.5 need a workaround in Nova.

  The impact of this is that, without the fix, XAPI is expecting a
  tapdisk to be spawned, but the Storage Manager does not spawn one.  As
  such, the VM will not be able to connect to this Cinder volume.

  The correct fix in Nova is to emulate the above commit for users of
  XenServer 6.5; i.e. set the backend-kind=vbd.  This will ensure that
  the storage manager spawns a tapdisk, and that it can be attached in
  the correct way

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