Volumesnapshot created from a cirros image can not be deleted with cli.

[Fernando Hernandez Gonzalez]

Brief Description
-----------------
Volume snapshot is created from a cirros, after created cli command is not deleting the snapshot neither with the snapshot id nor snapshot name.

Severity
--------
Major

Steps to Reproduce
------------------
From Horizon create a cirros image.
Once created go to the Actions drop down list and create a Volume.
Go to Project->Volumes->Volumes and check for the volume created from cirros
Once created go to the Actions drop down list and create a snapshot.
Go to Project->Volumes->Snapshot and check for the snapshot volume created.
Once snapshot from volume created go to the Actions drop down list launch and instance

Try to delete the volume and snapshot with cli command.
[wrsroot@controller-0 ~(keystone_admin)]$ source /etc/nova/openrc
[wrsroot@controller-0 ~(keystone_admin)]$ openstack volume snapshot delete 42daf9b6-0a26-4c74-b885-0fed69ce7b02 -v
START with options: [u'volume', u'snapshot', u'delete', u'42daf9b6-0a26-4c74-b885-0fed69ce7b02', u'-v']
command: volume snapshot delete -> openstackclient.volume.v2.volume_snapshot.DeleteVolumeSnapshot (auth=True)
Using auth plugin: password
END return value: 0
[wrsroot@controller-0 ~(keystone_admin)]$ openstack volume snapshot delete Volumefromcirros -v
START with options: [u'volume', u'snapshot', u'delete', u'Volumefromcirros', u'-v']
command: volume snapshot delete -> openstackclient.volume.v2.volume_snapshot.DeleteVolumeSnapshot (auth=True)
Using auth plugin: password
END return value: 0

Expected Behavior
------------------
Applying the cli command should delete the snapshot volume coming from cirros image.

Actual Behavior
----------------
Snapshot volume is not deleted.

Reproducibility
---------------
100%
System Configuration
--------------------
Virtual Multinodo External Storage - 2 Controllers + 2 computes + 2 storage

[Ghada Khalil (gkhalil)]

This is likely upstream openstack behavior. It's not likely that this is something unique to StarlingX.
If this is standard openstack behavior, we may choose not to change it. Further investigation is required.

I wouldn't mark this as stx.2018.10 gating -- it's a very specific test scenario. Marking as stx.2019.03 instead.

[Bruce Jones (brucej)]

Cindy please assign an engineer to work this bug, thanks! If this turns out to be a storage issue, have Vivian put someone from her team on it.

[haitao wang (hwang85)]

Confirmed that upstream OpenStack can delete volumnsnapshot.

[haitao wang (hwang85)]

Confirmed that volumesnapshot created from a cirros image can be deleted with cli, with command different with one described in 'steps to reproduce'.

After launching an instance, run following commands:

1. [wrsroot@controller-0 ~(keystone_admin)]$ source /etc/nova/openrc

2. [wrsroot@controller-0 ~(keystone_admin)]$ openstack volume snapshot delete <name of your snapshot> -v
Successfully delete snapshot in Project->Volumes->Snapshots.

3. [wrsroot@controller-0 ~(keystone_admin)]$ openstack volume snapshot delete Volumefromcirros –v
Failed to delete snapshot with name or ID ‘Volumefromcirros’ : No snapshots with a name or ID of ‘Volumefromcirros’ exists.

4. Change the command to [wrsroot@controller-0 ~(keystone_admin)]$ openstack volume delete Volumefromcirros –v

5. Successfully delete volume in Project->Volumes->Volumes.

Both snapshot and volume deleted successfully.