Bug 2054605

Summary:	LVMVolumeGroupNodeStatus is not updated correctly
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	N Balachandran <nibalach>
Component:	lvm-operator	Assignee:	N Balachandran <nibalach>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shay Rozen <srozen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	jolmomar, lgangava, muagarwa, ocs-bugs, odf-bz-bot, sapillai
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-160	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 09:12:46 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 N Balachandran 2022-02-15 10:21:17 UTC

Description of problem (please be detailed as possible and provide log
snippets):

Deploy ODF LVM Operator and create the LVMCluster CR to create a VG. After the VG has been created, on adding a new device to the node and restarting the vgmanager pod, the new device is added to the vg but not updated in the LVMVolumeGroupNodeStatus or LVMCluster.Status.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?

Yes
Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 4 Shay Rozen 2022-03-02 12:03:01 UTC

New disk is in the resource.