Project

General

Profile

Actions

Bug #47665

closed

rbd-nbd: unmap ignores namespace when searching device by image spec

Added by Mykola Golub over 3 years ago. Updated over 3 years ago.

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

0%

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

Description

When unmapping an image by the image spec, the rbd-nbd ignores the namespace when searching for the nbd device, which may result in unmapping an image from a wrong namespace (if you have a chance of mapping images with the same name but from different namespaces.

% rbd-nbd map rbd/test
/dev/nbd0
% rbd-nbd map rbd/ns/test
/dev/nbd1
% rbd-nbd list-mapped
id    pool  namespace  image  snap  device   
6327  rbd              test   -     /dev/nbd0
6365  rbd   ns         test   -     /dev/nbd1
% rbd-nbd unmap rbd/ns/test
% rbd-nbd list-mapped
id    pool  namespace  image  snap  device   
6365  rbd   ns         test   -     /dev/nbd1


Related issues 2 (0 open2 closed)

Copied to rbd - Backport #47703: nautilus: rbd-nbd: unmap ignores namespace when searching device by image specResolvedNathan CutlerActions
Copied to rbd - Backport #47704: octopus: rbd-nbd: unmap ignores namespace when searching device by image specResolvedNathan CutlerActions
Actions #1

Updated by Mykola Golub over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 37429
Actions #2

Updated by Jason Dillaman over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #3

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47703: nautilus: rbd-nbd: unmap ignores namespace when searching device by image spec added
Actions #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47704: octopus: rbd-nbd: unmap ignores namespace when searching device by image spec added
Actions #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".

Actions

Also available in: Atom PDF