Hi Seyeong,

Thanks for the patches!

In the future, could you please add DEP-3 headers [1] to them?
(usually just 'Bug-Ubuntu:'/'Origin:' are needed on git patches)

Also, it's a good practice to name the patch files with the bug
prefix (this is style, not requirement, but it helps when there
is multiple bugs per upload, and with maintenance over time).

I have handled these in this upload, as the changes are minor.
Thanks again!

[1] https://dep-team.pages.debian.net/deps/dep3/

$ head -n2 debian/patches/lp1994521-*

Bug-Ubuntu: http://bugs.launchpad.net/bugs/1994521
Origin: https://review.opendev.org/c/openstack/cinder/+/907257

Bug-Ubuntu: http://bugs.launchpad.net/bugs/1994521
Origin: https://review.opendev.org/c/openstack/cinder/+/907258

** Description changed:

  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.
+ The customer has the required hardware for testing this.
  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.
  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 
  : hpe3parclient.exceptions.HTTPConflict: Conflict (HTTP 409) 32 - volume
  has a child

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to