Bug #47306
Updated by Ernesto Puerta over 3 years ago
<pre> 2020-09-03 18:03:07,331.331 INFO:__main__:---------------------------------------------------------------------- 2020-09-03 18:03:07,331.331 INFO:__main__:Traceback (most recent call last): 2020-09-03 18:03:07,331.331 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-api/qa/tasks/mgr/dashboard/test_rgw.py", line 288, in test_all 2020-09-03 18:03:07,331.331 INFO:__main__: self.assertEqual(len(data), 0) 2020-09-03 18:03:07,332.332 INFO:__main__:AssertionError: 1 != 0 2020-09-03 18:03:07,332.332 INFO:__main__: 2020-09-03 18:03:07,332.332 INFO:__main__:---------------------------------------------------------------------- 2020-09-03 18:03:07,332.332 INFO:__main__:Ran 193 tests in 2142.009s 2020-09-03 18:03:07,332.332 INFO:__main__: 2020-09-03 18:03:07,332.332 INFO:__main__: </pre> This error first appeared in PR https://github.com/ceph/ceph/pull/31663 (https://jenkins.ceph.com/job/ceph-api/2359/), which was merged with that error raising. All subsequent builds (99%) are consistently failing due to this. !failures.png! RGW team (Casey and and J. Eric Ivancich) launched a "revert PR":https://github.com/ceph/ceph/pull/36996 revert PR to verify whether this was the reason. The PR reverted resulted "in in the same failure":https://jenkins.ceph.com/job/ceph-api/2460/. failure. This may mean: * This error was NOT caused by this PR. Chances are that: a dependency update caused (Python libraries, ceph-build, ...). * This error WAS caused by this PR but 'reinforced' by a later PR (as other RGW PRs have happened later). To discard this situation, the revert should be applied right after the original one.