Actions
Bug #49261
closedpubsub: FAIL: test radosgw-admin commands, AssertionError: 11 != 10
% Done:
0%
Source:
Tags:
multisite
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
2021-02-10T22:53:00.548 INFO:tasks.rgw_multisite_tests:====================================================================== 2021-02-10T22:53:00.548 INFO:tasks.rgw_multisite_tests:FAIL: test radosgw-admin commands 2021-02-10T22:53:00.548 INFO:tasks.rgw_multisite_tests:---------------------------------------------------------------------- 2021-02-10T22:53:00.550 INFO:tasks.rgw_multisite_tests:Traceback (most recent call last): 2021-02-10T22:53:00.550 INFO:tasks.rgw_multisite_tests: File "/home/teuthworker/src/git.ceph.com_git_teuthology_14fad31725ce3e5fc27890f2a8ef1f21c838d296/virtualenv/lib/python3.6/site-packages/nose/case.py", line 198, in runTest 2021-02-10T22:53:00.550 INFO:tasks.rgw_multisite_tests: self.test(*self.arg) 2021-02-10T22:53:00.550 INFO:tasks.rgw_multisite_tests: File "/home/teuthworker/src/git.ceph.com_ceph-c_efb97059277dfb6a8a132434209bebcb815a389c/qa/tasks/rgw_multi/tests_ps.py", line 3062, in test_ps_admin 2021-02-10T22:53:00.551 INFO:tasks.rgw_multisite_tests: assert_equal(len(parsed_result['events']), 10) 2021-02-10T22:53:00.551 INFO:tasks.rgw_multisite_tests:AssertionError: 11 != 10 2021-02-10T22:53:00.551 INFO:tasks.rgw_multisite_tests:-------------------- >> begin captured stdout << ---------------------
doesn't happen every time
Updated by Yuval Lifshitz about 3 years ago
- Assignee set to Yuval Lifshitz
- Pull request ID set to 39461
Updated by Yuval Lifshitz about 3 years ago
- Status changed from New to Fix Under Review
Updated by Casey Bodley about 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to pacific
Updated by Backport Bot about 3 years ago
- Copied to Backport #49295: pacific: pubsub: FAIL: test radosgw-admin commands, AssertionError: 11 != 10 added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Casey Bodley about 3 years ago
- Status changed from Resolved to Pending Backport
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions