Bug 1883343 - Re-enable skipped conformance tests for IBM Cloud
Summary: Re-enable skipped conformance tests for IBM Cloud
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ibm-roks-toolkit
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.6.0
Assignee: Cesar Wong
QA Contact: Xiaoli Tian
URL:
Whiteboard: IBMROKS
Depends On:
Blocks: 1883345
TreeView+ depends on / blocked
 
Reported: 2020-09-28 20:44 UTC by Cesar Wong
Modified: 2020-10-27 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1883345 (view as bug list)
Environment:
Last Closed: 2020-10-27 16:45:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 25220 0 None closed Re-enable skipped conformance tests for IBM Cloud 2020-10-05 13:17:37 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:46:14 UTC

Description Cesar Wong 2020-09-28 20:44:16 UTC 
Re-enabling selected tests now that associated bugs have been fixed and are in the Red Hat OpenShift on IBM Cloud v4.3 builds

[Feature:Prometheus][Conformance] Prometheus when installed on the cluster should provide ingress metrics
[Conformance][Area:Networking][Feature:Router] The HAProxy router should enable openshift-monitoring to pull metrics
[k8s.io] [sig-node] Pods Extended [k8s.io] Pod Container Status should never report success for a pending container
Comment 1 Cesar Wong 2020-09-28 20:45:47 UTC 
Verifying this bug directly, as it already merged, only affects extended tests, and is needed for backporting to previous releases.
Comment 4 errata-xmlrpc 2020-10-27 16:45:59 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 (OpenShift Container Platform 4.6 GA Images), 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:4196
Note You need to log in before you can comment on or make changes to this bug.