Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1812908

Summary: [RHOS-16] tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume failed when the self.device(vdb)value was in use(config_drive vfat in my case)
Product: Red Hat OpenStack Reporter: Martin Kopec <mkopec>
Component: openstack-tempestAssignee: Paras Babbar <pbabbar>
Status: CLOSED DUPLICATE QA Contact: Martin Kopec <mkopec>
Severity: high Docs Contact:
Priority: high    
Version: 16.0 (Train)CC: apevec, lhh, slinaber, udesale
Target Milestone: z2Keywords: AutomationBlocker, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tempest-23.0.0-0.20200423172313.d432237.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-30 14:43:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Kopec 2020-03-12 13:46:37 UTC
This bug was initially created as a copy of Bug #1777523

I am copying this bug because: 



Description of problem:
This bug is clone of https://bugs.launchpad.net/tempest/+bug/1852807 upstream


How reproducible:

whenever you have the deployment with config_Drive= true with vfat as driver type or you use the testcase with instance deployed with ephemeral disk


Steps to reproduce
1. deploy an instance with one already added vdb volume attached(Like I have used config drive format vfat that already took vdb volume)
2. run this testcase tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume
3. This will fail in assertNotIn mismatch error like below as it tries to validate that vdb is detached or not which is set by libvirt assumption

Actual results:
Testcase failed 

Expected results:
Testcase should have passed

Additional info:

Please look on this detailed upstream bug : https://bugs.launchpad.net/tempest/+bug/1852807

Comment 6 Martin Kopec 2020-09-30 14:43:23 UTC
This bug was originally meant for rhos-16, rhos-16.1 has been tracked by this https://bugzilla.redhat.com/show_bug.cgi?id=1777523. 
As this bug's target release has been changed to rhos-16.1, I can close this as duplicate of 1777523.

*** This bug has been marked as a duplicate of bug 1777523 ***