Bug 1710052
Summary: | [RHOS 15] Tempest test failure: test_list_extensions | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Archit Modi <amodi> | ||||
Component: | openstack-tempest | Assignee: | Artom Lifshitz <alifshit> | ||||
Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 15.0 (Stein) | CC: | alifshit, apevec, chkumar, dasmith, eglynn, jhakimra, kchamart, lhh, lyarwood, mbooth, mkopec, sbauza, sgordon, slinaber, udesale, vromanso | ||||
Target Milestone: | beta | Keywords: | Reopened, Triaged | ||||
Target Release: | 15.0 (Stein) | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | openstack-tempest-20.0.0-0.20190523153626.a955095.el8ost | Doc Type: | No Doc Update | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-09-21 11:22:03 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Archit Modi
2019-05-14 19:49:14 UTC
Given that API extensions are deprecated [1] I'm questioning the value of running the test_list_extensions test in downstream CI. We should not be setting [compute_feature_enabled]/api_extensions in tempest.conf. [1] https://developer.openstack.org/api-ref/compute/?expanded=list-extensions-detail#extensions-extensions-deprecated https://review.opendev.org/#/c/659601/ fixes the test mismatch issue on RHEL-8 RHOS-15, Can we reopen the bug? We will remove the above part? (In reply to Chandan Kumar from comment #4) > https://review.opendev.org/#/c/659601/ fixes the test mismatch issue on > RHEL-8 RHOS-15, Can we reopen the bug? We will remove the above part? I'm still not convinced about the value of running those extensions tests, but since the work to fix it has already been done, I don't see why we shouldn't track it properly. Do I just close this as UPSTREAM then, or we have an actual OSP build NVR to set? Hello Artom, We can add the following nvr https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=901681 -> openstack-tempest-20.0.0-0.20190523153626.a955095.el8ost for this bug. One more question, [compute_feature_enabled]/api_extensions is setted by python-tempestconf tool, we can remove it from there. From which release it is being deprecated? (We can open a python-tempestconf bug for the same) Thanks, Chandan Kumar > One more question, [compute_feature_enabled]/api_extensions is setted by > python-tempestconf tool, we can remove it from there. From which release it > is being deprecated? (We can open a python-tempestconf bug for the same) In Tempest the deprecation is from commit 5078e8b87de957f2aa0dcc6973a29fa0284f8d80 [1] from the end of 2016. In Nova it's from 75280e582e6d607b38bc2af9f51f80fd5135453c [2] from the beginning of 2016. Not sure what release that corresponds to, but I think we can safely remove extensions from python_tempestconf. [1] https://review.opendev.org/#/c/371612/ [2] https://review.opendev.org/#/c/310399/ Thanks Artom, Added the story here https://storyboard.openstack.org/#!/story/2005794, we are safe to remove it. The fix is available in the Fixed in version package. 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/RHEA-2019:2811 |