Bug 2093445 - ManagementState reconciliation breaks SR
Summary: ManagementState reconciliation breaks SR
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Special Resource Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.11.0
Assignee: Brett Thurber
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks: 2093444
TreeView+ depends on / blocked
 
Reported: 2022-06-03 17:52 UTC by Brett Thurber
Modified: 2022-08-10 11:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2093444
Environment:
Last Closed: 2022-08-10 11:16:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:16:45 UTC

Description Brett Thurber 2022-06-03 17:52:28 UTC
+++ This bug was initially created as a clone of Bug #2093444 +++

Description of problem:
Per Veritas:
we are facing issue in deploying InfoScale using SRO.
SRO with these changes does not reconcile the infoscale-vtas SR as we do not specify "ManagementState" to SR spec and thus in create function of predicate, func isSpecialResourceUnmanaged() returns false always which prevents creation of resources/helm chart.
func isSpecialResourceUnmanaged(obj client.Object) bool {
	sr, ok := obj.(*v1beta1.SpecialResource)
	if !ok {
		return false
	}
	return sr.Spec.ManagementState == operatorv1.Unmanaged
}
CreateFunc: func(e event.CreateEvent) bool {
obj := e.Object
			if IsSpecialResource(obj) {
-				return true
+				return isSpecialResourceUnmanaged(obj)
			}
We anticipate code should return true if isSpecialResourceUnmanaged(obj)=false
This change needs to be fixed for successful creation of SR resources.


Version-Release number of selected component (if applicable):
4.10

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 errata-xmlrpc 2022-08-10 11:16:16 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069


Note You need to log in before you can comment on or make changes to this bug.