Bug 1862120

Summary: LocalVolumeSet should delay provisioning after discovery so it won't race with other provisioners.
Product: OpenShift Container Platform Reporter: Rohan CJ <rojoseph>
Component: StorageAssignee: Rohan CJ <rojoseph>
Storage sub component: Local Storage Operator QA Contact: Chao Yang <chaoyang>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, hekumar, jsafrane
Version: 4.6   
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:21:22 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:

Description Rohan CJ 2020-07-30 13:56:58 UTC
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:

Comment 1 Hemant Kumar 2020-09-11 13:51:32 UTC
We are still planning to fix this in 4.6 timeframe.

Comment 4 Rohan CJ 2020-10-01 08:38:49 UTC
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

Comment 6 Chao Yang 2020-10-10 05:34:08 UTC
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

Comment 8 errata-xmlrpc 2020-10-27 16:21:22 UTC
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