Project

General

Profile

Actions
Copy link

Bug #43969

closed

lvm list for single report is broken when passing vg/lv

Added by Guillaume Abrioux about 4 years ago. Updated about 4 years ago.

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

0%

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

Description

17957d9 introduced a regression in lvm list.

When passing a vg/lv path for generating a single report, it fails (and return '{}')
because the filter used in the lvs command isn't right. It uses the lv
name instead of the vg name because os.path.basename(device) is used
while it should be os.path.dirname(device)

Related issues 2 (0 open — 2 closed)

Copied to ceph-volume - Backport #43985: mimic: lvm list for single report is broken when passing vg/lvResolvedActions
Copied to ceph-volume - Backport #43986: nautilus: lvm list for single report is broken when passing vg/lvResolvedJan FajerskiActions
Actions
Copy link
 #1

Updated by Jan Fajerski about 4 years ago

  • Status changed from New to In Progress
  • Backport set to nautilus, mimic
  • Pull request ID set to 33077
Actions
Copy link
 #2

Updated by Jan Fajerski about 4 years ago

  • Status changed from In Progress to Pending Backport
Actions
Copy link
 #3

Updated by Jan Fajerski about 4 years ago

  • Regression changed from No to Yes

Introduced by #31700

Actions
Copy link
 #4

Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #43985: mimic: lvm list for single report is broken when passing vg/lv added
Actions
Copy link
 #5

Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #43986: nautilus: lvm list for single report is broken when passing vg/lv added
Actions
Copy link
 #6

Updated by Nathan Cutler about 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".

Actions
Copy link

Also available in: Atom PDF