Project

General

Profile

Actions
Copy link

Bug #65889

closed

wrong use of IoCtx::exec() in many places

Added by Yehuda Sadeh almost 2 years ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Yehuda Sadeh
Category:
-
Target version:
-
% Done:

0%

Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
56180
Tags (freeform):
Merge Commit:
13883f52f22d8ce2ac409507ae5a581bf0fca20d
Fixed In:
v19.3.0-6991-g13883f52f2
Released In:
v20.2.0~1311
Upkeep Timestamp:
2025-11-01T01:18:18+00:00

Description

A lot of the objclass exec calls use IoCtx::exec() inappropriately, where the calls use a read version of the API to call a write objclass method. This is broken when using local read affinity as the ops are then being sent to a non primary OSD.

Actions
Copy link
 #1

Updated by Ilya Dryomov about 1 year ago

  • Pull request ID set to 56180
Actions
Copy link
 #2

Updated by Ilya Dryomov about 1 year ago

  • Status changed from New to Resolved
  • Assignee set to Yehuda Sadeh
Actions
Copy link
 #4

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to 13883f52f22d8ce2ac409507ae5a581bf0fca20d
  • Fixed In set to v19.3.0-6991-g13883f52f22
  • Upkeep Timestamp set to 2025-07-11T11:08:55+00:00
Actions
Copy link
 #5

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v19.3.0-6991-g13883f52f22 to v19.3.0-6991-g13883f52f2
  • Upkeep Timestamp changed from 2025-07-11T11:08:55+00:00 to 2025-07-14T23:09:00+00:00
Actions
Copy link
 #6

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~1311
  • Upkeep Timestamp changed from 2025-07-14T23:09:00+00:00 to 2025-11-01T01:18:18+00:00
Actions
Copy link

Also available in: Atom PDF