Bug 1797648 - 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)
Summary: tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_atta...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z11
: 13.0 (Queens)
Assignee: Paras Babbar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-03 14:51 UTC by Martin Kopec
Modified: 2022-08-18 17:16 UTC (History)
4 users (show)

Fixed In Version: openstack-tempest-18.0.0-13.el7ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-10 11:53:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1852807 0 None None None 2020-02-03 14:55:31 UTC
OpenStack gerrit 598075 0 None MERGED Do not pass device when calling compute.base.attach_volume 2020-05-13 20:19:59 UTC
OpenStack gerrit 694636 0 None MERGED Fix test_attach_detach_volume test case to not rely on user/libvirt supplied disk name 2020-05-13 20:19:59 UTC
OpenStack gerrit 698598 0 None MERGED Fix test_stamp_pattern to remove dependency of user supplied volume name 2020-05-13 20:19:59 UTC
Red Hat Issue Tracker OSP-3826 0 None None None 2022-08-18 17:16:08 UTC
Red Hat Product Errata RHBA-2020:0769 0 None None None 2020-03-10 11:53:36 UTC

Description Martin Kopec 2020-02-03 14:51:59 UTC
This bug was initially created as a copy of Bug #1777523

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 9 Martin Kopec 2020-02-17 08:29:46 UTC
The Fixed in version package contains the fix for this issue. Verified by an automated job which ran the tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume test successfully. The package is available in the RHOS repos via the latest symlink.

Comment 12 errata-xmlrpc 2020-03-10 11:53:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0769


Note You need to log in before you can comment on or make changes to this bug.