Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1887046

Summary:	Event for LSO need update to avoid confusion
Product:	OpenShift Container Platform	Reporter:	Chao Yang <chaoyang>
Component:	Storage	Assignee:	Fabio Bertinatto <fbertina>
Storage sub component:	Local Storage Operator	QA Contact:	Chao Yang <chaoyang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.6
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:24:43 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 Chao Yang 2020-10-10 10:53:23 UTC

Description of problem:
Event for LSO need update to avoid confusion

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-10-09-224055
local-storage-operator.4.6.0-202010061132.p0

How reproducible:
Always

Steps to Reproduce:
1.Install LSO
2.Create localvolumeset
3.Provision one pv
4.oc get event.
There is only one localvolume or localvolumeset, last event can cause some confusion.

9m58s       Normal   DiscoveredNewDevice            localvolumeset/lvs                                                   ip-10-0-136-242.us-east-2.compute.internal - found possible matching disk, waiting 1m0s to claim
8m58s       Normal   FoundMatchingDisk              localvolumeset/lvs                                                   ip-10-0-136-242.us-east-2.compute.internal - symlinking matching disk
7m58s       Normal   DeviceSymlinkExists            localvolumeset/lvs                                                   ip-10-0-136-242.us-east-2.compute.internal - this device is already matched by another LocalVolume or LocalVolumeSet


Actual results:
"this device is already matched by another LocalVolume or LocalVolumeSet" this event can cause confusion if there is only one localvolumeset 

Expected results:
Remove the word "another", it is better output the localvolume or localvolumeset name.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 3 Chao Yang 2020-11-04 06:21:20 UTC

Two event messages are created:
9m33s       Normal   DiscoveredNewDevice            localvolumeset/lvs                                                   ip-10-0-150-231.us-east-2.compute.internal - found possible matching disk, waiting 1m0s to claim
8m33s       Normal   FoundMatchingDisk              localvolumeset/lvs                                                   ip-10-0-150-231.us-east-2.compute.internal - symlinking matching disk

Comment 6 errata-xmlrpc 2021-02-24 15:24:43 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633