Bug 1905746 - Subscription manual approval test is flaky
Summary: Subscription manual approval test is flaky
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.6.z
Assignee: Vu Dinh
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On: 1905640
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-09 00:07 UTC by OpenShift BugZilla Robot
Modified: 2020-12-21 13:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-21 13:24:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-lifecycle-manager pull 1898 0 None closed [release-4.6] Bug 1905746: fix(e2e): Fix subscription manual approval flaky test 2021-01-15 11:40:10 UTC
Red Hat Product Errata RHSA-2020:5614 0 None None None 2020-12-21 13:24:47 UTC

Description OpenShift BugZilla Robot 2020-12-09 00:07:22 UTC
+++ This bug was initially created as a clone of Bug #1905640 +++

Description of problem:
The current Subscription manual approve e2e test has an extra Apply code that needs to the InstallPlan being updated twice by accident. This causes the test case to be flaky.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 errata-xmlrpc 2020-12-21 13:24:19 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.6.9 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-2020:5614


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