Project

General

Profile

Actions

Bug #44222

closed

c-v raw list should silence stderr

Added by Sébastien Han about 4 years ago. Updated about 4 years ago.

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

0%

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

Description

If 'ceph-bluestore-tool' fails on a device, the json output of the list
command will be messed up. Ignoring stderr of that command fixes this.

See:

[root@rook-ceph-osd-prepare-minikube-tvcbb /]# ceph-volume raw list
 stderr: unable to read label for /dev/vdd: (2) No such file or directory
{
    "0": {
        "ceph_fsid": "7ec3d9fd-ada3-4bcb-9f2b-8deea05fe480",
        "device": "/dev/vdb",
        "osd_id": 0,
        "osd_uuid": "979b298c-58c9-4220-96f2-d6ea6d7bdf61",
        "type": "bluestore" 
    },
    "1": {
        "ceph_fsid": "7ec3d9fd-ada3-4bcb-9f2b-8deea05fe480",
        "device": "/dev/vdc",
        "osd_id": 1,
        "osd_uuid": "702d550b-8d61-44b3-a863-9814cf767f0c",
        "type": "bluestore" 
    }
}

Related issues 2 (0 open2 closed)

Copied to ceph-volume - Backport #44226: nautilus: c-v raw list should silence stderrResolvedSébastien HanActions
Copied to ceph-volume - Backport #44227: mimic: c-v raw list should silence stderrResolvedJan FajerskiActions
Actions #1

Updated by Sébastien Han about 4 years ago

  • Pull request ID set to 33371
Actions #2

Updated by Jan Fajerski about 4 years ago

  • Backport set to nautilus, mimic
Actions #3

Updated by Jan Fajerski about 4 years ago

  • Status changed from New to Pending Backport
Actions #4

Updated by Jan Fajerski about 4 years ago

  • Copied to Backport #44226: nautilus: c-v raw list should silence stderr added
Actions #5

Updated by Jan Fajerski about 4 years ago

  • Copied to Backport #44227: mimic: c-v raw list should silence stderr added
Actions #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

Also available in: Atom PDF