Bug 1744453
Summary: | Need a clear event for local storage operator when not finding the device defined in localvolume | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
Component: | Storage | Assignee: | Christian Huffman <chuffman> |
Status: | CLOSED ERRATA | QA Contact: | Liang Xia <lxia> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.2.0 | CC: | aos-bugs, aos-storage-staff, jsafrane, lxia |
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-04 11:13:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1783863 | ||
Bug Blocks: |
Description
Qin Ping
2019-08-22 08:26:31 UTC
I've added an error whenever any disk cannot be found. Previously the node would not report an error if at least one disk was successfully found. For instance: > $ oc describe localvolume | grep Events -A 12 > Events: > Type Reason Age From Message > ---- ------ ---- ---- ------- > Warning ErrorFindingMatchingDisk 10m local-storage-diskmaker ip-10-0-137-243.us-east-2.compute.internal - unable to find matching disk /dev/xvdg > Warning ErrorFindingMatchingDisk 2m10s local-storage-diskmaker ip-10-0-150-160.us-east-2.compute.internal - unable to find matching disk /dev/xvdf > Warning ErrorFindingMatchingDisk 2m10s local-storage-diskmaker ip-10-0-150-160.us-east-2.compute.internal - unable to find matching disk /dev/xvdg > Warning ErrorFindingMatchingDisk 2m10s local-storage-diskmaker ip-10-0-150-160.us-east-2.compute.internal - found empty matching device list This is submitted at https://github.com/openshift/local-storage-operator/pull/51 . Verified with local-storage-operator.4.4.0-201912170523 on 4.4.0-0.nightly-2019-12-18-064553 $ oc describe localvolume | grep Events -A 12 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal FoundMatchingDisk 33m local-storage-diskmaker lxia19-48fdq-worker-dsf5s - found matching disk dm-1 Warning ErrorFindingMatchingDisk 33m local-storage-diskmaker lxia19-48fdq-worker-6fgxw - unable to add disk-id /dev/myvg01/mylv01 to local disk pool: unable to find device with id /dev/myvg01/mylv01 Warning ErrorFindingMatchingDisk 33m local-storage-diskmaker lxia19-48fdq-worker-6fgxw - found empty matching device list Warning ErrorFindingMatchingDisk 33m local-storage-diskmaker lxia19-48fdq-worker-2pj5w - unable to add disk-id /dev/myvg01/mylv01 to local disk pool: unable to find device with id /dev/myvg01/mylv01 Warning ErrorFindingMatchingDisk 33m local-storage-diskmaker lxia19-48fdq-worker-2pj5w - found empty matching device list Warning ErrorFindingMatchingDisk 2m17s local-storage-diskmaker lxia19-48fdq-worker-6fgxw - unable to find matching disk /dev/i-am-not-exist Warning ErrorFindingMatchingDisk 2m17s local-storage-diskmaker lxia19-48fdq-worker-6fgxw - unable to add disk-id /dev/myvg01/mylv01 to local disk pool: unable to find device with id /dev/myvg01/mylv01 Warning ErrorFindingMatchingDisk 2m17s local-storage-diskmaker lxia19-48fdq-worker-6fgxw - found empty matching device list Warning ErrorFindingMatchingDisk 2m4s local-storage-diskmaker lxia19-48fdq-worker-2pj5w - unable to find matching disk /dev/i-am-not-exist Warning ErrorFindingMatchingDisk 2m4s local-storage-diskmaker lxia19-48fdq-worker-2pj5w - unable to add disk-id /dev/myvg01/mylv01 to local disk pool: unable to find device with id /dev/myvg01/mylv01 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |