Bug 1507650 - ceph_test_cls_log failure
Summary: ceph_test_cls_log failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
urgent
Target Milestone: rc
: 3.0
Assignee: Casey Bodley
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-30 19:57 UTC by Casey Bodley
Modified: 2017-12-05 23:49 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-12.2.1-36.el7cp Ubuntu: ceph_12.2.1-38redhat1xenial
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:49:35 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 21964 0 None None None 2017-10-30 19:57:49 UTC
Red Hat Product Errata RHBA-2017:3387 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-06 03:03:45 UTC

Description Casey Bodley 2017-10-30 19:57:50 UTC 
Description of problem:

Seen upstream from ceph_test_cls_log:

[ RUN      ] cls_rgw.test_log_add_same_time
/home/cbodley/ceph/src/test/cls_log/test_cls_log.cc:144: Failure
      Expected: 10
To be equal to: (int)entries.size()
      Which is: 1
[  FAILED  ] cls_rgw.test_log_add_same_time (1180 ms)


This test creates 10 log entries with the same timestamp, and relies on cls_cxx_subop_version() to generate unique keys for each. Due to a regression in the osd, each cls operation sees the same value from cls_cxx_subop_version(), so only one key is created/overwritten in this test.
Comment 11 errata-xmlrpc 2017-12-05 23:49:35 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/RHBA-2017:3387
Note You need to log in before you can comment on or make changes to this bug.