Project

General

Profile

Actions

Bug #62046

open

quincy: 'ceph device ls -f json' has empty path value

Added by Peter Razumovsky 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
orchestrator
Target version:
-
% Done:

0%

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

Description

Ceph 17.2.6, installed by Rook 1.11.4.

I have empty path in ceph 'device ls' for all osds despite of 'ceph osd metadata' contains valid device_paths for each osd.

For example, ceph device ls-by-host (ls and ls-by-daemon has the same issue):

$ ceph device ls-by-host cz7787-child-cl-storage-worker-efi-fw27m -f json-pretty

[
    {
        "devid": "ST2000NM0033-9ZM_Z1X02J9N",
        "location": [
            {
                "host": "cz7787-child-cl-storage-worker-efi-fw27m",
                "dev": "sdd",
                "path": "" 
            }
        ],
        "daemons": [
            "osd.5" 
        ]
    },
    {
        "devid": "ST2000NM0033-9ZM_Z1X6AKD3",
        "location": [
            {
                "host": "cz7787-child-cl-storage-worker-efi-fw27m",
                "dev": "sdc",
                "path": "" 
            }
        ],
        "daemons": [
            "osd.0" 
        ]
    }
]

Example of osd metadata for osd.5:

$ ceph osd metadata 5
{
    "id": 5,
    "arch": "x86_64",
    "back_addr": "[v2:10.12.0.6:6804/2813079967,v1:10.12.0.6:6805/2813079967]",
    "back_iface": "",
    "bluefs": "1",
    "bluefs_dedicated_db": "0",
    "bluefs_dedicated_wal": "0",
    "bluefs_single_shared_device": "1",
    "bluestore_bdev_access_mode": "blk",
    "bluestore_bdev_block_size": "4096",
    "bluestore_bdev_dev_node": "/dev/dm-1",
    "bluestore_bdev_devices": "sdd",
    "bluestore_bdev_driver": "KernelDevice",
    "bluestore_bdev_optimal_io_size": "0",
    "bluestore_bdev_partition_path": "/dev/dm-1",
    "bluestore_bdev_rotational": "1",
    "bluestore_bdev_size": "2000397795328",
    "bluestore_bdev_support_discard": "0",
    "bluestore_bdev_type": "hdd",
    "ceph_release": "quincy",
    "ceph_version": "ceph version 17.2.6 (d7ff0d10654d2280e08f1ab989c7cdf3064446a5) quincy (stable)",
    "ceph_version_short": "17.2.6",
    "ceph_version_when_created": "ceph version 17.2.6 (d7ff0d10654d2280e08f1ab989c7cdf3064446a5) quincy (stable)",
    "container_hostname": "cz7787-child-cl-storage-worker-efi-fw27m",
    "container_image": "127.0.0.1:44301/mirantis/ceph:v17.2.6-rel-5",
    "cpu": "Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz",
    "created_at": "2023-07-14T10:10:33.667829Z",
    "default_device_class": "hdd",
    "device_ids": "sdd=ST2000NM0033-9ZM_Z1X02J9N",
    "device_paths": "sdd=/dev/disk/by-path/pci-0000:00:1f.2-ata-4",
    "devices": "sdd",
    "distro": "centos",
    "distro_description": "CentOS Stream 9",
    "distro_version": "9",
    "front_addr": "[v2:10.12.1.6:6806/2813079967,v1:10.12.1.6:6807/2813079967]",
    "front_iface": "",
    "hb_back_addr": "[v2:10.12.0.6:6806/2813079967,v1:10.12.0.6:6807/2813079967]",
    "hb_front_addr": "[v2:10.12.1.6:6808/2813079967,v1:10.12.1.6:6809/2813079967]",
    "hostname": "cz7787-child-cl-storage-worker-efi-fw27m",
    "journal_rotational": "1",
    "kernel_description": "#167-Ubuntu SMP Mon May 15 17:35:05 UTC 2023",
    "kernel_version": "5.4.0-150-generic",
    "mem_swap_kb": "0",
    "mem_total_kb": "98779884",
    "network_numa_unknown_ifaces": "back_iface,front_iface",
    "objectstore_numa_unknown_devices": "sdd",
    "os": "Linux",
    "osd_data": "/var/lib/ceph/osd/ceph-5",
    "osd_objectstore": "bluestore",
    "osdspec_affinity": "",
    "pod_name": "rook-ceph-osd-5-858dc9d647-6wbxz",
    "pod_namespace": "rook-ceph",
    "rotational": "1" 
}

"device_paths": "sdd=/dev/disk/by-path/pci-0000:00:1f.2-ata-4",

Previously we used v16.2.11 and 'ceph device ls' returned non-empty paths (we're relying on device ls output in functional testing).

Rook community advices to file a bug because of probable "Ceph's rook orchestrator module" issue.

No data to display

Actions

Also available in: Atom PDF