Bug 1507412 - Using Swift healthcheck api to determine swift is configured
Summary: Using Swift healthcheck api to determine swift is configured
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tempestconf
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Chandan Kumar
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On: 1622011
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-30 08:13 UTC by Chandan Kumar
Modified: 2019-01-11 11:49 UTC (History)
1 user (show)

Fixed In Version: python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:48:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 568869 0 None MERGED Use healthcheck api to determine swift service 2020-02-26 06:49:44 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:49:03 UTC

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
Note You need to log in before you can comment on or make changes to this bug.