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

Bug 1507412

Summary:	Using Swift healthcheck api to determine swift is configured
Product:	Red Hat OpenStack	Reporter:	Chandan Kumar <chkumar>
Component:	python-tempestconf	Assignee:	Chandan Kumar <chkumar>
Status:	CLOSED ERRATA	QA Contact:	Martin Kopec <mkopec>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	whayutin
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:48:21 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:
Bug Depends On:	1622011
Bug Blocks:

Description Chandan Kumar 2017-10-30 08:13:45 UTC

Swift healthcheck api can be used with python-tempestconf to determine whether swift is configured or not and what backends are used i.e Ceph.

Here is the upstream tracking bug: https://review.openstack.org/#/c/513808/
https://storyboard.openstack.org/#!/story/2001253

Comment 5 Martin Kopec 2018-08-14 06:24:09 UTC

The review containing the feature for determining if swift is configured has been merged to master branch.

Comment 9 Martin Kopec 2018-09-05 06:43:18 UTC

python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost package has been released and it contains a feature which determines if swift is configured.

The package is available in the latest puddle (2018-09-05.1).

Comment 11 errata-xmlrpc 2019-01-11 11:48:21 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:0045