Description of problem: It's possible the daemon will use up free devices that have been attached for some other reason. We should add a delay that the device remains unused before assuming it is free. Version-Release number of selected component (if applicable): How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
We are still planning to fix this in 4.6 timeframe.
This might help when doing verification: `oc describe lvset <lvsetname>` will show relevant events. Note the time difference between DiscoveredNewDevice and FoundMatchingDisk is larger than 1m0s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal DiscoveredNewDevice 62s (x6 over 62s) localvolumeset-symlink-controller minikube - found possible matching disk, waiting 1m0s to claim Normal FoundMatchingDisk 2s (x3 over 2s) localvolumeset-symlink-controller minikube - symlinking matching disk
45m Normal DiscoveredNewDevice localvolumeset/lvs ip-10-0-144-158.us-east-2.compute.internal - found possible matching disk, waiting 1m0s to claim 44m Normal FoundMatchingDisk localvolumeset/lvs ip-10-0-144-158.us-east-2.compute.internal - symlinking matching disk oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-08-210814 True False 19h Cluster version is 4.6.0-0.nightly-2020-10-08-210814
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 (OpenShift Container Platform 4.6 GA Images), 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:4196