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

Bug 2099507

Summary:	failure to update special-resource-lifecycle table during update Event
Product:	OpenShift Container Platform	Reporter:	yevgeny shnaidman <yshnaidm>
Component:	Special Resource Operator	Assignee:	yevgeny shnaidman <yshnaidm>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.10
Target Milestone:	---
Target Release:	4.10.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-11 15:27:56 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:	2100038
Bug Blocks:

Description yevgeny shnaidman 2022-06-21 06:54:17 UTC

Description of problem:

During update event, the filtering code is trying to update the special-resource-lifecycle table and fails with "the object has been modified" error. Since there is no retry in the filtering event and not error returning, the flow continues, without the table being updated. This later causes the problem with the upgrade of the daemonset with UpgradeStrategy set to OnDelete.

Solution: stop relying and using a special table just for that process. We can use the generation label and pod generation template label which are set and managed by the DS controller, which provides a more reliable mechanism

Comment 2 Udi Kalifon 2022-06-21 08:50:12 UTC

@yshnaidm What for example causes such an update event? How can I recreate this error in the current version (step-by-step instructions, please)?

Comment 4 Udi Kalifon 2022-06-29 10:59:43 UTC

Verified with a custom-built bundle from Yevgeny. Verified by deleting several pods to trigger the update.

Comment 7 errata-xmlrpc 2022-07-11 15:27:56 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.10.22 bug fix 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/RHBA-2022:5513

Comment 8 Red Hat Bugzilla 2023-09-15 01:56:04 UTC

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