Project

General

Profile

Actions
Copy link

Bug #22229

closed

omap: inconsistent omap header behavior when resetting object

Added by Yehuda Sadeh over 6 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Sending a compound operation:
- remove()
- create()
- populate omap header and key-values

If omap header did not exist before then it ends up with the correct data. If it existed it ends up empty.

Actions
Copy link
 #1

Updated by Yehuda Sadeh over 6 years ago

  • Status changed from New to Rejected

Ok, not a bug. At least not as described. Problem is that when popoulating the data we still read the old header, from before the delete(), so it affected the logic there.

Actions
Copy link

Also available in: Atom PDF