yahoo-eng-team team mailing list archive

[Lee Yarwood <lyarwood@xxxxxxxxxx>]

Public bug reported:

Description
===========

$subject, the use of libvirt's virDomainBlockRebase API [1] currently
means that we can't swap between volumes that do not present a block
device or file on the compute host.

This is additionally blocked by the following conditional in Nova's
libvirt driver:

https://github.com/openstack/nova/blob/f454e1dec9580abf4605e071bdd678a40f492a49/nova/virt/libvirt/driver.py#L1854-L1865

This is however possible with the virDomainBlockCopy API [2] when the
domain is using the new -blockdev framework for detailing how disks are
attached to the guest.

[1] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockRebase
[2] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockCopy

Steps to reproduce
==================

* Launch an instance with a RBD volume attached.
* Try to swap to another volume.


Expected result
===============

Success using virDomainBlockCopy.


Actual result
=============

Failure using virDomainBlockRebase as no block device or file is
presented to the compute host.


Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

master

2. Which hypervisor did you use?
   (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
   What's the version of that?

libvirt + QEMU/KVM

2. Which storage type did you use?
   (For example: Ceph, LVM, GPFS, ...)
   What's the version of that?

Ceph

3. Which networking type did you use?
   (For example: nova-network, Neutron with OpenVSwitch, ...)

N/A

** Affects: nova
     Importance: High
     Assignee: Lee Yarwood (lyarwood)
         Status: In Progress


** Tags: ceph libvirt volumes

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

** Tags added: ceph libvirt volumes

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

Title:
  Unable to swap between RBD volumes using virDomainBlockRebase

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========

  $subject, the use of libvirt's virDomainBlockRebase API [1] currently
  means that we can't swap between volumes that do not present a block
  device or file on the compute host.

  This is additionally blocked by the following conditional in Nova's
  libvirt driver:

  https://github.com/openstack/nova/blob/f454e1dec9580abf4605e071bdd678a40f492a49/nova/virt/libvirt/driver.py#L1854-L1865

  This is however possible with the virDomainBlockCopy API [2] when the
  domain is using the new -blockdev framework for detailing how disks
  are attached to the guest.

  [1] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockRebase
  [2] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockCopy

  Steps to reproduce
  ==================

  * Launch an instance with a RBD volume attached.
  * Try to swap to another volume.

  
  Expected result
  ===============

  Success using virDomainBlockCopy.

  
  Actual result
  =============

  Failure using virDomainBlockRebase as no block device or file is
  presented to the compute host.

  
  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

  master

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

  libvirt + QEMU/KVM

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

  Ceph

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

  N/A

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