Project

General

Profile

Bug #43966

simple scan on dmcrypt OSDs creates wrong keys in json file

Added by Jan Fajerski about 4 years ago. Updated almost 4 years ago.

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

0%

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

Description

simple scan on a luks encrypted OSD creates a json file that activate fails on. The problem is that the block* files in such an OSD carry a _dmcrypt suffix and scan uses the file name as a key.

Foe example:

{
    "active": "ok",
    "block.db_dmcrypt": {
        "path": "/tmp/tmp775s3nkl/block.db_dmcrypt",
        "uuid": "f58353af-d3a8-4e87-8a38-c5ec653428f3" 
    },
    "block.db_uuid": "f58353af-d3a8-4e87-8a38-c5ec653428f3",
    "block.wal_dmcrypt": {
        "path": "/tmp/tmp775s3nkl/block.wal_dmcrypt",
        "uuid": "ce959bb9-8ef2-4788-bdd7-d0edd700177f" 
    },
    "block.wal_uuid": "ce959bb9-8ef2-4788-bdd7-d0edd700177f",
    "block_dmcrypt": {
        "path": "/tmp/tmp775s3nkl/block_dmcrypt",
        "uuid": "50ed8ffe-0311-4213-9d4c-8aeac7cebb35" 
    },

...

Specifically activate fails on a missing block key. It also would ignore the block.db_dmcrypt and block.wal_dmcrypt keys.


Related issues

Copied to ceph-volume - Backport #44331: nautilus: simple scan on dmcrypt OSDs creates wrong keys in json file Resolved
Copied to ceph-volume - Backport #44332: mimic: simple scan on dmcrypt OSDs creates wrong keys in json file Resolved
Copied to ceph-volume - Backport #44333: luminous: simple scan on dmcrypt OSDs creates wrong keys in json file Resolved

History

#1 Updated by Jan Fajerski about 4 years ago

  • Pull request ID set to 33079

#2 Updated by Jan Fajerski about 4 years ago

  • Status changed from New to Fix Under Review

#3 Updated by Sebastian Wagner about 4 years ago

  • Description updated (diff)

#4 Updated by Jan Fajerski about 4 years ago

  • Status changed from Fix Under Review to Pending Backport

#5 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #44331: nautilus: simple scan on dmcrypt OSDs creates wrong keys in json file added

#6 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #44332: mimic: simple scan on dmcrypt OSDs creates wrong keys in json file added

#7 Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #44333: luminous: simple scan on dmcrypt OSDs creates wrong keys in json file added

#8 Updated by Nathan Cutler almost 4 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