Bug 2088533

Summary: CRDs for openshift.io should have subresource.status failes on sharedconfigmaps.sharedresource and sharedsecrets.sharedresource
Product: OpenShift Container Platform Reporter: Dennis Periquet <dperique>
Component: openshift-apiserverAssignee: Abu Kashem <akashem>
Status: CLOSED ERRATA QA Contact: Rahul Gangwar <rgangwar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11CC: gmontero, mfojtik, wking
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:13:14 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:

Description Dennis Periquet 2022-05-19 15:59:58 UTC
Description of problem:

sharedconfigmaps.sharedresource.openshift.io and sharedsecrets.sharedresource.openshift.io do not have a subresource.status field in their CRD so this test fails:

: [sig-arch][Early] CRDs for openshift.io should have subresource.status [Suite:openshift/conformance/parallel] expand_less	4s
{  fail [github.com/openshift/origin/test/extended/operators/check_crd_status.go:158]: May 19 13:52:01.582: CRD sharedconfigmaps.sharedresource.openshift.io has a status in the schema but no subresource.status
CRD sharedsecrets.sharedresource.openshift.io has a status in the schema but no subresource.status}


Example job: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cloud-provider-azure/27/pull-ci-openshift-cloud-provider-azure-master-e2e-azure-ccm/1527267196269498368

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


How reproducible:

Happens all the time.

Steps to Reproduce:
1.
2.
3.

Actual results:

The tests fail showing:

CRD sharedconfigmaps.sharedresource.openshift.io has a status in the schema but no subresource.status
CRD sharedsecrets.sharedresource.openshift.io has a status in the schema but no subresource.status

Expected results:

The test should pass

Additional info:

https://coreos.slack.com/archives/C01CQA76KMX/p1652975270321669?thread_ts=1652975216.903949&cid=C01CQA76KMX

Comment 1 Dennis Periquet 2022-05-19 16:34:53 UTC
Below is a search of the problem and I see it occurs on 4.11 and 4.12 the slack thread above indicates it would fail on 4.10.

https://search.ci.openshift.org/?search=CRDs+for+openshift.io&maxAge=48h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Comment 3 Rahul Gangwar 2022-05-30 04:26:01 UTC
Below test is passed in https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-vsphere-techpreview/1530987547314884608

: [sig-arch][Early] CRDs for openshift.io should have a status in the CRD schema [Suite:openshift/conformance/parallel]	5s

So moving the case to verified

Comment 5 errata-xmlrpc 2022-08-10 11:13:14 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.11.0 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-2022:5069