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

Bug 1909122

Summary:	[OCP v46] Always update the default profilebundles on Compliance operator startup
Product:	OpenShift Container Platform	Reporter:	Prashant Dhamdhere <pdhamdhe>
Component:	Compliance Operator	Assignee:	Juan Antonio Osorio <josorior>
Status:	CLOSED ERRATA	QA Contact:	Prashant Dhamdhere <pdhamdhe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6.z	CC:	jhrozek, josorior, knewcome, mrogers, nkinder, xiyuan
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1909120	Environment:
Last Closed:	2021-01-19 13:53:52 UTC	Type:	---
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:	1909120
Bug Blocks:

Description Prashant Dhamdhere 2020-12-18 11:59:21 UTC

+++ This bug was initially created as a clone of Bug #1909120 +++

Description of problem:

Always update the default profilebundles on Compliance operator startup so that
when the operator upgrade happens the default profilebundles deployment rolls 
out and restart the operator which will check the updated contents and 
contentImage reference.

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

4.6.9-x86_64


How reproducible:

Always

Steps to Reproduce:

1. Deploy Compliance Operator
2. Check profilebundles deployment, contents and pods
3. Perform operator upgrade to the available version
4. Check profilebundles deployment, contents and pods
  

Actual results:
 
The default profilebundles deployment and contents are not getting updated when
the compliance operator upgrade gets performed.

Expected results:

The default profilebundles deployment, contents should get updated when the 
operator upgrade gets performed.
 
Additional info:

Comment 1 Nathan Kinder 2021-01-06 19:23:10 UTC

This has been fixed upstream for the 4.6 branch as a part of the following PR:

https://github.com/openshift/compliance-operator/pull/527

The specific commit for 4.6 is:

https://github.com/openshift/compliance-operator/commit/81a9b32355554bd2fd4ff46a81f08b654c217096

Comment 6 errata-xmlrpc 2021-01-19 13:53:52 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 (Moderate: OpenShift Container Platform 4.6 compliance-operator security and 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/RHSA-2021:0190