Skip to content

LSODeviceLinkMismatch / LSONoStableLocalVolumePath #401

Description

@DanielFroehlich

After Updateing to 4.22 #390 we see a lot of warnings like

LSODeviceLinkMismatch

Local Storage operator has observed that pv local-pv-d60306a3 is using a symlink
that is not optimum for stability between reboots and OS upgrades. Consider updating
LocalVolumeDeviceLink policy to preferredSymlink to allow LSO to manage the symlink.
[View details](https://console-openshift-console.apps.isar.coe.muc.redhat.com/monitoring/alerts/3734418817?managed_cluster=2997ae23-5631-49ad-8f0b-1dcf4e528e00&prometheus=openshift-monitoring%2Fk8s&severity=warning&alertname=LSODeviceLinkMismatch&container=kube-rbac-proxy&endpoint=metrics&instance=10.129.25.50%3A9393&job=local-storage-diskmaker-metrics&name=local-pv-d60306a3&namespace=openshift-local-storage&persistent_volume=local-pv-d60306a3&pod=diskmaker-manager-2pjlt&policy=None&service=local-storage-diskmaker-metrics)

and

LSONoStableLocalVolumePath

Local Storage operator has observed that pv local-pv-a35797a9 is using a symlink
that is not optimum for stability between reboots and OS upgrades. Consider updating
LocalVolumeDeviceLink policy to preferredSymlink to allow LSO to manage the symlink.
[View details](https://console-openshift-console.apps.isar.coe.muc.redhat.com/monitoring/alerts/3734418817?managed_cluster=2997ae23-5631-49ad-8f0b-1dcf4e528e00&prometheus=openshift-monitoring%2Fk8s&severity=warning&alertname=LSODeviceLinkMismatch&container=kube-rbac-proxy&endpoint=metrics&instance=10.131.24.163%3A9393&job=local-storage-diskmaker-metrics&name=local-pv-a35797a9&namespace=openshift-local-storage&persistent_volume=local-pv-a35797a9&pod=diskmaker-manager-krqnc&policy=None&service=local-storage-diskmaker-metrics)

We probably need to review our LSO config

Metadata

Metadata

Assignees

Labels

Type

Fields

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions