Bug 1819288

Summary:	Drop ownership of kubernetes-nmstate CRDs
Product:	Container Native Virtualization (CNV)	Reporter:	Petr Horáček <phoracek>
Component:	Networking	Assignee:	Petr Horáček <phoracek>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	2.3.0	CC:	cnv-qe-bugs, ncredi, pelauter
Target Milestone:	---
Target Release:	2.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cluster-network-addons-operator-container-v2.3.0-27	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 19:10:58 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 Petr Horáček 2020-03-31 15:59:16 UTC

Description of problem:
In the next version of CNV, the ownership of kubernetes-nmstate objects will be transferred to a different operator. In order to prepare for this change, we have to drop our own ownerships now.

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

How reproducible:
Always

Steps to Reproduce:
1. Deploy CNV
2. Check NodeNetworkConfigurationPolicy, NodeNetworkConfigurationEnactment and NodeNetworkState CRDs
3. See their ownershipReference

Actual results:
They are bound to NetworkAddonsConfig.

Expected results:
There should be no ownership reference.

Comment 4 errata-xmlrpc 2020-05-04 19:10:58 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/RHEA-2020:2011