Project

General

Profile

Actions

Feature #17010

closed

RBD default features should be negotiated with the OSD

Added by Jason Dillaman over 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Pull request ID:

Description

For example, attempting to create an image with a Jewel librbd client against a Hammer OSD will result in failure since the older OSD doesn't recognize the new default feature set. A new rbd class method should be created for retrieving the OSD's feature set in order to negotiate a compatible default feature set for a particular image.


Related issues 1 (0 open1 closed)

Copied to rbd - Backport #19805: jewel: RBD default features should be negotiated with the OSDResolvedJason DillamanActions
Actions #1

Updated by Mykola Golub over 7 years ago

  • Status changed from New to In Progress
  • Assignee set to Mykola Golub
Actions #2

Updated by Mykola Golub over 7 years ago

  • Status changed from In Progress to Fix Under Review
Actions #3

Updated by Jason Dillaman over 7 years ago

  • Status changed from Fix Under Review to Resolved
Actions #4

Updated by Jason Dillaman almost 7 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to jewel
Actions #5

Updated by Jason Dillaman almost 7 years ago

  • Copied to Backport #19805: jewel: RBD default features should be negotiated with the OSD added
Actions #6

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF