Bug 1612361

Summary: [RFE] Release of APIv2 as Stable
Product: Red Hat OpenStack Reporter: Telles Nobrega <tenobreg>
Component: openstack-saharaAssignee: Telles Nobrega <tenobreg>
Status: CLOSED ERRATA QA Contact: Luigi Toscano <ltoscano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15.0 (Stein)CC: matt, mimccune, pgrist, scohen, srevivo
Target Milestone: Upstream M2Keywords: FutureFeature, TechPreview, Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-sahara-10.0.1-0.20190503161819.994ff8c.el8ost/ Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:16:49 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:

Description Telles Nobrega 2018-08-03 18:58:21 UTC
Description of problem:

Currently we have experimental support for APIv2 on Sahara. We need to upgrade that so Stable.

Comment 1 Telles Nobrega 2018-08-03 21:33:10 UTC
*** Bug 1612359 has been marked as a duplicate of this bug. ***

Comment 9 Luigi Toscano 2019-06-25 14:37:53 UTC
Forcing the usage of APIv2 results in a passing status of the relevant tests.

Verified on
openstack-sahara-api-10.0.1-0.20190503161819.994ff8c.el8ost.noarch
openstack-sahara-common-10.0.1-0.20190503161819.994ff8c.el8ost.noarch
puppet-sahara-14.4.1-0.20190420121202.abf76b2.el8ost.noarch
python3-sahara-10.0.1-0.20190503161819.994ff8c.el8ost.noarch
python3-sahara-plugin-ambari-1.0.1-0.20190503150400.75f8698.el8ost.noarch
python3-sahara-plugin-cdh-1.0.1-0.20190503160353.b73a04d.el8ost.noarch
python3-sahara-plugin-mapr-1.0.1-0.20190503160355.7f4e060.el8ost.noarch
python3-saharaclient-2.2.0-0.20190312151158.25043cb.el8ost.noarch

Comment 11 errata-xmlrpc 2019-09-21 11:16:49 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/RHEA-2019:2811