Bug 1777523 - [RHOS-16.1] 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: [RHOS-16.1] tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJS...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z2
: 16.1 (Train on RHEL 8.2)
Assignee: Paras Babbar
QA Contact: Martin Kopec
URL:
Whiteboard:
: 1812908 1827347 (view as bug list)
Depends On:
Blocks: 1826904 1827347
TreeView+ depends on / blocked
 
Reported: 2019-11-27 17:55 UTC by Paras Babbar
Modified: 2020-12-15 18:36 UTC (History)
9 users (show)

Fixed In Version: openstack-tempest-24.0.0-0.20200615173423.c73e6b1.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1827347 (view as bug list)
Environment:
Last Closed: 2020-12-15 18:35:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1852807 0 None None None 2019-11-27 19:59:30 UTC
OpenStack gerrit 694636 0 'None' MERGED Fix test_attach_detach_volume test case to not rely on user/libvirt supplied disk name 2020-12-14 16:53:07 UTC
OpenStack gerrit 698598 0 None MERGED Fix test_stamp_pattern to remove dependency of user supplied volume name 2020-12-14 16:52:38 UTC
Red Hat Product Errata RHEA-2020:5413 0 None None None 2020-12-15 18:36:45 UTC

Description Paras Babbar 2019-11-27 17:55:33 UTC 
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 1 Paras Babbar 2019-11-27 17:59:39 UTC 
I have added the partial fix: https://review.opendev.org/#/c/694636/ , 

there are couple more scenario test that needs some tuning  

[1] https://github.com/openstack/tempest/blob/887f99a288c1d2bef45356c916b317d37828e6ac/tempest/scenario/test_stamp_pattern.py#L101

[2] https://github.com/openstack/tempest/blob/67e07786189661151c73263a13a523865770bdde/tempest/scenario/test_minimum_basic.py#L71

as they both are also depend on volume_device_name params which is based on assumption.
Comment 2 Martin Kopec 2019-12-09 01:05:50 UTC 
Hi Paras,

I see your patch got merged, thanks for the contribution. Are you going to also have a look on the other scenario tests you mentioned that need some tuning?
Comment 3 Paras Babbar 2019-12-10 15:41:31 UTC 
Hi Martin, Yes I will plan on working on them later after this week!
Comment 4 Martin Kopec 2019-12-10 15:53:30 UTC 
Hi Paras,

that's great! Thanks.
I'm gonna assign this BZ to you then, if you need any help (reviewing, getting the fixes to a release, etc), let me know.
Comment 6 Martin Kopec 2020-02-04 15:56:39 UTC 
moving to POST as the changes are merged upstream
Comment 20 Martin Kopec 2020-04-24 15:22:44 UTC 
*** Bug 1827347 has been marked as a duplicate of this bug. ***
Comment 32 Martin Kopec 2020-09-30 14:43:23 UTC 
*** Bug 1812908 has been marked as a duplicate of this bug. ***
Comment 45 Martin Kopec 2020-11-25 21:11:54 UTC 
The Fixed in version package contains both fixes of this issue. My testing concluded the same. The Fixed in version package is included in a latest puddle available in the RHOS 16.1 repository.
Comment 53 errata-xmlrpc 2020-12-15 18:35:44 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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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/RHEA-2020:5413
Note You need to log in before you can comment on or make changes to this bug.