[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Dariusz Gadomski]

My understanding is as follows: it has been rejected upstream for yoga,
because it was too close to EOL. But according to [1] it has been merged
upstream for later releases. IMO the presence in later release is a good
justification to backport the fix to jammy.

What's your take on this Mauricio?

[1] https://review.opendev.org/c/openstack/cinder/+/882782

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1994521

Title:
  HPE3PAR: Failing to clone a volume having children

Status in Cinder:
  Fix Released
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Jammy:
  Incomplete
Status in cinder source package in Mantic:
  Fix Released
Status in cinder source package in Noble:
  Fix Released

Bug description:
  [Impact]

  The customer faced issue when they are using nova with 3par storage.
  they can't delete volume if there is children and it is attached to vm.

  it makes sense they can't delete it as the children has attachment but
  nova should expose proper error when trying deletion.

  [Test Case]
  Haven't tested this as there is no test 3par storage.
  Volume->Snapshot->Volume2
  Volume2 is attached to some VM.
  and can't delete Volume without proper error msg.

  [Where problems could occur]
  This is related to hpe3par storage.
  snapshot handling could be issue with this patch.
  deleting volume could be issue with this patch.

  [Others]

  Original Desc

  When we try to delete a snapshot, we flatten it's dependent volumes by copying them to a new volume and deleting the original one.
  We fail to copy the volume when it has children and it is not handled in the code.

  : hpe3parclient.exceptions.HTTPConflict: Conflict (HTTP 409) 32 -
  volume has a child

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