-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.12
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
No
-
None
-
None
-
None
-
OCP VE Sprint 242
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
LVM Storage can't find encrypted device
Version-Release number of selected component (if applicable):
OCP: 4.12.23 LVM Storage: 4.12.1
Steps to Reproduce:
1. Deploy an SNO cluster 4.12.23 and create an encrypted partition 'application' at install time:
apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: name: 98-disk-partitions-master labels: machineconfiguration.openshift.io/role: master spec: config: ignition: version: 3.2.0 storage: disks: - device: /dev/nvme0n1 wipeTable: false partitions: - sizeMiB: 204800 startMiB: 600000 label: application number: 5 - sizeMiB: 51200 startMiB: 804800 label: recovery number: 6 filesystems: - path: /var/recovery device: /dev/disk/by-partlabel/recovery format: xfs - device: /dev/mapper/application format: xfs label: application wipeFilesystem: true luks: - clevis: tpm2: true device: /dev/disk/by-partlabel/application name: application options: - --cipher - aes-cbc-essiv:sha256 wipeVolume: true systemd: units: - name: var-recovery.mount enabled: true contents: | [Unit] Before=local-fs.target [Mount] Where=/var/recovery What=/dev/disk/by-partlabel/recovery [Install] WantedBy=local-fs.target
2. Deploy LVM Storage 4.12.1
3. Configure the following LVMCluster resource to use 'application' partition:
apiVersion: v1 items: - apiVersion: lvm.topolvm.io/v1alpha1 kind: LVMCluster metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"lvm.topolvm.io/v1alpha1","kind":"LVMCluster","metadata":{"annotations":{},"name":"my-lvmcluster","namespace":"openshift-storage"},"spec":{"storage":{"deviceClasses":[{"deviceSelector":{"paths":["/dev/mapper/application"]},"name":"vg1","thinPoolConfig":{"name":"thin-pool-1","overprovisionRatio":10,"sizePercent":90}}]}}} creationTimestamp: "2023-08-09T14:36:00Z" finalizers: - lvmcluster.topolvm.io generation: 1 name: my-lvmcluster namespace: openshift-storage resourceVersion: "55592" uid: 4749138e-65c7-4927-a2de-09f00dbc2255 spec: storage: deviceClasses: - deviceSelector: paths: - /dev/mapper/application name: vg1 thinPoolConfig: name: thin-pool-1 overprovisionRatio: 10 sizePercent: 90 status: deviceClassStatuses: - name: vg1 nodeStatus: - devices: - /dev/mapper/application - /dev/nvme1n1 node: super1 reason: can not find device name /dev/mapper/application in the available block devices status: Degraded state: Degraded kind: List metadata: resourceVersion: ""
Actual results:
LVM Storage can't find the device
Expected results:
LVM Storage should find the device
Additional info:
If I wipe the partition manually using this command it works, the device is found and the error is resolved:
sgdisk --zap-all /dev/mapper/application
I'm not sure if that's a bug or just something that's missing in my config.
- relates to
-
OCPBUGS-10534 LVMCluster does not show an error when no suitable device is found
-
- Closed
-