Project

General

Profile

Bug #47840

[object-map] ignore missing object map on disable request

Added by Jason Dillaman over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

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

Description

If the object map does not exist, don't prevent the object-map feature from being disabled.


Related issues

Copied to rbd - Backport #47889: octopus: [object-map] ignore missing object map on disable request Resolved
Copied to rbd - Backport #47890: nautilus: [object-map] ignore missing object map on disable request Resolved

History

#1 Updated by Jason Dillaman over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 37643

#2 Updated by Mykola Golub over 3 years ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47889: octopus: [object-map] ignore missing object map on disable request added

#4 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47890: nautilus: [object-map] ignore missing object map on disable request added

#5 Updated by Nathan Cutler over 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF