How do I identify the Rook-Ceph disk in an Automation Suite cluster?
Issue Description
How do I identify the Rook-Ceph disk in an Automation Suite cluster?
Resolution
Rook-Ceph path typically does not appear in the output of the lsblk command. To identify the correct path, describe any of the OSD pods from Rook-Ceph. You will find the path details under the ROOK_BLOCK_PATH environment variable. In this case, the path is /dev/sdd.
You need to verify the correct path on all server nodes before proceeding with the disk expansion.
Example:
Environment:
ROOK_NODE_NAME: as2349-offline
ROOK_CLUSTER_ID: 09913f3e-f937-49a0-90b7-38ee6b4b4830
ROOK_CLUSTER_NAME: rook-ceph
ROOK_PRIVATE_IP: (v1:status.podIP)
ROOK_PUBLIC_IP: (v1:status.podIP)
POD_NAMESPACE: rook-ceph
ROOK_MON_ENDPOINTS: <set to the key 'data' of config map 'rook-ceph-mon-endpoints'> Optional: false
ROOK_CONFIG_DIR: /var/lib/rook
ROOK_CEPH_CONFIG_OVERRIDE: /etc/rook/config/override.conf
NODE_NAME: (v1:spec.nodeName)
ROOK_CRUSHMAP_ROOT: default
ROOK_CRUSHMAP_HOSTNAME: as2349-offline
CEPH_VOLUME_DEBUG: 1
CEPH_VOLUME_SKIP_RESTORECON: 1
DM_DISABLE_UDEV: 1
ROOK_OSDS_PER_DEVICE: 1
CONTAINER_IMAGE: localhost:30071/ceph/ceph:v17.2.6
POD_NAME: rook-ceph-osd-0-7678d75f4c-98brx (v1:metadata.name)
POD_MEMORY_LIMIT: node allocatable (limits.memory)
POD_MEMORY_REQUEST: 1073741824 (requests.memory)
POD_CPU_LIMIT: node allocatable (limits.cpu)
POD_CPU_REQUEST: 1 (requests.cpu)
CEPH_USE_RANDOM_NONCE: true
ROOK_OSD_RESTART_INTERVAL: 0
ROOK_OSD_UUID: 9e939839-8552-4f92-b690-bb6bc861a1ff
ROOK_OSD_ID: 0
ROOK_CEPH_MON_HOST: <set to the key 'mon_host' in secret 'rook-ceph-config'> Optional: false
CEPH_ARGS: -m $(ROOK_CEPH_MON_HOST)
ROOK_BLOCK_PATH: /dev/sdd
ROOK_CV_MODE: raw
ROOK_OSD_DEVICE_CLASS: ssd
ROOK_POD_IP: (v1:status.podIP)