Description of problem: If the Rados Gateway is configured as object-store instead of swift the tools/config_tempest.py script will break
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install tempest
2. run config_tempest script with appropriate arguments.
Fails with exception:
CRITICAL tempest [-] ServiceError: Request on service 'object-store' with url 'http://192.168.190.246:8087/info' failed with code 404
TRACE tempest Traceback (most recent call last):
TRACE tempest File "tools/config_tempest.py", line 726, in <module>
TRACE tempest main()
TRACE tempest File "tools/config_tempest.py", line 140, in main
TRACE tempest clients.identity_region)
TRACE tempest File "/root/tempest/tempest/common/api_discovery.py", line 154, in discover
TRACE tempest services[name]['extensions'] = service.get_extensions()
TRACE tempest File "/root/tempest/tempest/common/api_discovery.py", line 111, in get_extensions
TRACE tempest top_level_path="info")
TRACE tempest File "/root/tempest/tempest/common/api_discovery.py", line 53, in do_get
TRACE tempest " with code %d" % (self.name, url, r.status))
TRACE tempest ServiceError: Request on service 'object-store' with url 'http://192.168.190.246:8087/info' failed with code 404
Script generates ./etc/tempest.conf
The reason this is happening is because RadowGW does not implement the /info api call.
need you help to have this BZ targeted for 7.0.
We need to handle it differently for short term and long term.
For long term Ceph RGW need to respond correctly so both config_tempest.py and for tempest swift tests. That will be Ceph bug. Neil, you decide which Ceph release it will land.
For short term, we need to fix config_tempest.py to "ignore" ceph swift responses. We should try to get it into CDN OSP7 bits ASAP. once we have a fix for config_tempest.py we can "apply" it in scripts for Tempest deployment on tempest VM.
*** Bug 1252600 has been marked as a duplicate of this bug. ***
There is barely any documentation about the /info API call:
Assigning this to one of our Swift devs as it's hard to know what to implement in lieu of proper documentation.
Merged upstream https://github.com/ceph/ceph/pull/10280
Matt will you be backporting this to jewel?
If so, http://tracker.ceph.com/issues/8945 should be marked "Backport: jewel".
If not, this BZ should be re-targeted to RHCS 3.
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.