Project

General

Profile

Actions
Copy link

Bug #11786

closed

mon: MonitorDBStore iterator's get_next_key() returns wrong keys

Added by Joao Eduardo Luis almost 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% Done:

0%

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

Description

specifically, the first key of the iterator is always returned first, regardless of it's prefix being passed on to the iterator's prefixes.

Fix incoming.

Related issues 2 (0 open — 2 closed)

Copied to Ceph - Backport #12483: mon: MonitorDBStore iterator's get_next_key() returns wrong keysResolvedJoao Eduardo LuisActions
Copied to Ceph - Backport #12484: mon: MonitorDBStore iterator's get_next_key() returns wrong keysResolvedJoao Eduardo Luis05/27/2015Actions
Actions
Copy link
 #1

Updated by Joao Eduardo Luis almost 9 years ago

  • Status changed from 12 to Fix Under Review
Actions
Copy link
 #2

Updated by Joao Eduardo Luis almost 9 years ago

  • Status changed from Fix Under Review to Pending Backport

need to check how far back we need to backport this.

Actions
Copy link
 #3

Updated by Joao Eduardo Luis over 8 years ago

  • Backport set to firefly, hammer

commit to cherry-pick is 2cc7aee1abe40453093306c8fef2312b650dff5d

cherry-pick is trivial.

wip-11786.firefly has firefly backport (https://github.com/ceph/ceph/pull/5360)
wip-11786.hammer has hammer backport (https://github.com/ceph/ceph/pull/5361)

Actions
Copy link
 #4

Updated by Loïc Dachary over 8 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF