rook/rook

Using encryptedDevice and host-based cluster, the OSD isn't resized when restarting it

クローズ

#13,262 opened on 2023/11/24

 (13 件のコメント) (2 件のリアクション) (1 人の担当者)Go (1,577 件のフォーク)batch import
bughelp wantedkeepalive

Repository metrics

Stars
 (7,606 個のスター)
PR merge metrics
 (平均マージ 2d 23h) (30d で 170 merged PRs)

説明

Is this a bug report or feature request?

  • Bug Report

Deviation from expected behavior:

  • Even after restarting the OSD deployments the size of the OSD is unchanged.

Expected behavior:

  • Resizing OSD by initContainers when the OSD is restarting.

How to reproduce it (minimal and precise):

  1. Setup the host-based cluster.
  2. Set spec.storage.config.encryptedDevice to true in CephCluster CR.
  3. Resize the disk that is using the OSD to larger than the OSD size.
  4. Restart the OSD.

File(s) to submit:

  • Cluster CR (custom resource), typically called cluster.yaml, if necessary

Logs to submit:

  • Crashing pod(s) logs, if necessary
    • The OSD pods are just starting fine.

Environment:

  • Rook version (use rook version inside of a Rook Pod):
    rook: v1.12.8
    go: go1.21.3
    
  • Storage backend version (e.g. for ceph do ceph -v):
    ceph version 17.2.6 (d7ff0d10654d2280e08f1ab989c7cdf3064446a5) quincy (stable)
    
  • Kubernetes version (use kubectl version):
    Client Version: v1.28.2
    Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
    Server Version: v1.28.3
    

コントリビューターガイド