Bug 1891124 - CP Conformance: CRD spec and status failures
Summary: CP Conformance: CRD spec and status failures
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
low
Target Milestone: ---
: 4.8.0
Assignee: Cesar Wong
QA Contact: Cesar Wong
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-23 20:16 UTC by Joseph Goergen
Modified: 2021-07-27 22:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 22:33:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 25742 0 None open Bug 1891124: Skip MCO CRD checks for ibmcloud provider in cli testing 2021-01-14 12:14:35 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:34:13 UTC

Description Joseph Goergen 2020-10-23 20:16:55 UTC 
Description of problem:
The conformance test
"[sig-cli] oc explain should contain proper spec+status for CRDs [Suite:openshift/conformance/parallel]"
fails on ROKS 4.5 due to no machine config operator.

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

How reproducible:
Deploy a ROKS 4.5 cluster without the machine config operator installed on it.

Steps to Reproduce:
1.
2.
3.

Actual results:
fail [github.com/openshift/origin/test/extended/cli/explain.go:358]: Unexpected error:
    <*errors.errorString | 0xc00041d000>: {
        s: "failed to explain [\"controllerconfigs\" \"--api-version=machineconfiguration.openshift.io/v1\"]: exit status 1",
    }
    failed to explain ["controllerconfigs" "--api-version=machineconfiguration.openshift.io/v1"]: exit status 1
occurred

Expected results:
Passed

Additional info:

This can be fixed by removing the machine-config-operator CRD from the cli test https://github.com/openshift/origin/blob/377fde66c4409a793838082fdd843f044311e374/test/extended/cli/explain.go#L103-L107
Comment 2 Antonio Murdaca 2020-11-09 18:33:30 UTC 
> 
> This can be fixed by removing the machine-config-operator CRD from the cli
> test
> https://github.com/openshift/origin/blob/
> 377fde66c4409a793838082fdd843f044311e374/test/extended/cli/explain.go#L103-
> L107

This must be conditionalized I guess or we'll drop this check from any other platform right? also, is there a plan for ROKS to use the MCO or we're sure that doesn't happen and we can safely drop this MCO check for this platform?
Comment 3 Antonio Murdaca 2020-11-17 08:25:46 UTC 
I'm closing this as it's not an MCO bug afaict.
Comment 4 Joseph Goergen 2020-11-17 14:07:51 UTC 
Didn't see that you responded. ROKS has no plan on supporting MCO at all
Comment 5 Cesar Wong 2020-12-07 14:41:46 UTC 
We should have a condition to check whether ROKS is being tested and skip the relevant CRD types.
Comment 9 Cesar Wong 2021-06-18 01:51:27 UTC 
Skipped properly in 4.8.0-0.nightly-2021-06-16-190035
Comment 11 errata-xmlrpc 2021-07-27 22:33:58 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.8.2 bug fix and security 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:2438
Note You need to log in before you can comment on or make changes to this bug.