Consistent read doesn't work for just deleted item

Bug #1271207 reported by Ilya Sviridov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Fix Released
High
Illia Khudoshyn

Bug Description

According to test results

Traceback (most recent call last):
  File "/var/lib/jenkins/jobs/MagnetoDB_functional_test/workspace/tempest/api/keyvalue/test_items.py", line 70, in test_put_get_update_delete_item
    consistent_read=True))
  File "/usr/lib/python2.6/site-packages/testtools/testcase.py", line 322, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.6/site-packages/testtools/testcase.py", line 417, in assertThat
    raise MismatchError(matchee, matcher, mismatch, verbose)
MismatchError: !=:
reference = {}
actual = {u'Item': {u'forum': {u'S': u'forum1'},
           u'last_posted_by': {u'S': u'John'},
           u'message': {u'S': u'message_text'},
           u'replies': {u'N': u'1'},
           u'subject': {u'S': u'subject2'}}}

Changed in magnetodb:
importance: Undecided → High
milestone: none → 1.0.0
Changed in magnetodb:
assignee: nobody → Illia Khudoshyn (ikhudoshyn)
Changed in magnetodb:
status: New → In Progress
Changed in magnetodb:
status: In Progress → Fix Committed
Changed in magnetodb:
status: Fix Committed → Incomplete
Changed in magnetodb:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.