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

Bug 1821332

Summary:	[Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes [Suite:openshift/conformance/parallel]
Product:	OpenShift Container Platform	Reporter:	Lukasz Szaszkiewicz <lszaszki>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OLM	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1821334 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:25:34 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:
Bug Blocks:	1821334

Description Lukasz Szaszkiewicz 2020-04-06 15:23:48 UTC

The [1] marketplace test makes the "managed cluster " test to fail occasionally. It creates a short-lived pod in openshift-marketplace that is marked as failing (terminated && exitCode=2).

It was moved [2] into the "Serial" test suite for 4.5 and no longer causes disruption.

I am creating this BZ to back-port it to 4.4

 
[1] OCP-21728 check the publisher,display,labels of opsrc&csc
[2] https://github.com/openshift/origin/pull/21496

Comment 1 Lukasz Szaszkiewicz 2020-04-08 07:30:12 UTC

I am moving this issue to VERIFIED state as it doesn't face end consumers it only fixes a flaky e2e test.

Comment 3 errata-xmlrpc 2020-07-13 17:25:34 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:2409