Bug 1793750

Summary:	local-storage-operator does not update daemonset when new node is added to the selector
Product:	OpenShift Container Platform	Reporter:	Hemant Kumar <hekumar>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Liang Xia <lxia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.z	CC:	aos-bugs, jsafrane
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:
Clones:	1803265 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:25:48 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:	1798198
Bug Blocks:	1803265

Comment 3 Liang Xia 2020-02-04 03:32:35 UTC

Tested with,

$ oc get clusterversion ; oc get csv 
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.4.0-0.nightly-2020-02-03-005212   True        False         23h     Cluster version is 4.4.0-0.nightly-2020-02-03-005212
NAME                                        DISPLAY                  VERSION              REPLACES   PHASE
local-storage-operator.4.4.0-202001240656   Local Storage            4.4.0-202001240656              Succeeded


On a 3 masters and 3 nodes master,
The localvolume CR is created with one node, daemonset local-diskmaker and local-provisioner's desired value is 1, which is correct.
After adding a new node to above CR by edit the CR, the daemonset are not changed, still show desired value as 1, which is not correct, same issue as in the description.

Comment 6 Liang Xia 2020-02-14 06:48:49 UTC

Verified both local-diskmaker and local-provisioner's daemonset updated when there are nodes added to/removed from the selector.

local-storage-operator.4.4.0-202002131916
OpenShift Version 4.4.0-0.nightly-2020-02-13-212616

Comment 8 errata-xmlrpc 2020-05-04 11:25:48 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, 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

Comment 9 Red Hat Bugzilla 2023-09-14 05:50:30 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days