Bug 1827414 - ROKS: enable openshift conformance tests to work with IBM ROKS clusters
Summary: ROKS: enable openshift conformance tests to work with IBM ROKS clusters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ibm-roks-toolkit
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Cesar Wong
QA Contact: Xiaoli Tian
URL:
Whiteboard: IBMROKS
Depends On:
Blocks: 1829958
TreeView+ depends on / blocked
 
Reported: 2020-04-23 20:45 UTC by Cesar Wong
Modified: 2020-07-13 17:31 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1829958 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:30:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24817 0 None closed Bug 1827414: e2e: Add ibmcloud provider, skips and fixes 2020-08-25 07:23:53 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:19 UTC

Description Cesar Wong 2020-04-23 20:45:21 UTC
Description of problem:
ROKS clusters are different from regular self-hosted clusters in that control plane components live outside of the cluster. Some conformance tests need to be adapted while others need to be skipped. 

How reproducible:
alwaysz

Steps to Reproduce:
1. Run openshift e2e conformance test against ROKS cluster

Actual results:
Test result contains several failures

Expected results:
Test passes

Comment 3 Cesar Wong 2020-04-30 16:26:15 UTC
This is an extended test-only change. The PR merged after passing extended tests.
https://github.com/openshift/origin/pull/24817
Moving to verified

Comment 4 errata-xmlrpc 2020-07-13 17:30:56 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


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