Inaccurate docstring test_boot_cloned_encrypted_volume

Bug #2006594 reported by Sofia Enriquez
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Toheeb Oyekola

Bug Description

We need to update the docstring to accurately describe the two steps that are being performed. The first step is to destroy the instance, and the second step is to create an encrypted clone using the source_volid and then boot another instance from that cloned volume.

First in L125 the volume is not detached but the instance is destroyed. Second the test says that the test performs two clone operations. A non-encrypted clone and then an encrypted clone operation. Only the second is accurate, since the test only create a clone from the same volume type than the source volume which is encrypted. [1]

We need to update the docstring to something like this:

- Destroy instance
- Create encrypted clone using source_volid
- Boot another instance from cloned volume


Revision history for this message
Toheeb Oyekola (toheeb) wrote :

Can this bug be assigned to me, so I can work on it?

Revision history for this message
Sofia Enriquez (lsofia-enriquez) wrote :

Yes Toheeb Oyekola (toheeb), Please work on this bug! Thank you!

Changed in cinder-tempest-plugin:
assignee: nobody → Toheeb Oyekola (toheeb)
Revision history for this message
Sofia Enriquez (lsofia-enriquez) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder-tempest-plugin 1.9.0

This issue was fixed in the openstack/cinder-tempest-plugin 1.9.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.