yahoo-eng-team team mailing list archive

[James Page <james.page@xxxxxxxxxx>]

** Changed in: cloud-archive/rocky
       Status: Fix Committed => Fix Released

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

Title:
  libvirtError exceptions during volume attach leave volume connected to
  host

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Fix Released
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Fix Committed
Status in OpenStack Compute (nova) rocky series:
  Fix Committed
Status in OpenStack Compute (nova) stein series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Bionic:
  Fix Released
Status in nova source package in Cosmic:
  Fix Released
Status in nova source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * This is an additional patch required for bug #1825882, when
  a libvirt exception that prevents the volume attachment to complete,
  the underlying volumes should be disconnected from the host.

  [Test Case]

  * Deploy any OpenStack version up to Pike , which includes ceph backed cinder
  * Create a guest VM (openstack server ...)
  * Create a test cinder volume

  $ openstack volume create test --size 10

  * Force a drop on ceph traffic. Run the following command on the nova
  hypervisor on which the server runs.

  $ iptables -A OUTPUT -d ceph-mon-addr -p tcp --dport 6800 -j DROP

  * Attach the volume to a running instance.

  $ openstack server add volume 7151f507-a6b7-4f6d-a4cc-fd223d9feb5d
  742ff117-21ae-4d1b-a52b-5b37955716ff

  * This should cause the volume attachment to fail

  $ virsh domblklist instance-xxxxx
  Target Source
  ------------------------------------------------
  vda nova/7151f507-a6b7-4f6d-a4cc-fd223d9feb5d_disk

  No volume should attached after this step.

  * If the behavior is fixed:

     * Check that  openstack server show , doesn't displays the
  displays the volume as attached.

  * If the behavior isn't fixed:

     * openstack server show <ID> , will display the volume in the
  volumes_attached property.

  [Expected result]

  * Volume attach fails and the volume is disconnected from the host.

  [Actual result]

  * Volume attach fails but remains connected to the host.

  [Regression Potential]

  * The patches have been cherry-picked from upstream which helps to
  reduce the regression potential of these fixes.

  [Other Info]

  * N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1826523/+subscriptions