-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19.0
Description of problem:
see https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-no-capabilities/1914807258718408704
level=error msg=failed to initialize the cluster: Cluster operator ingress is not available
Installer exit with code 6
Version-Release number of selected component (if applicable):
4.19.0-0.ci-2025-04-22-160508
How reproducible:
100%
Steps to Reproduce:
1. check the job
2.
3.
Actual results:
install failed
checked ingress operator logs and found:
2025-04-22T23:42:05.502790147Z 2025-04-22T23:42:05.502Z ERROR operator.init.controller-runtime.source.EventHandler wait/loop.go:87 if kind is a CRD, it should be installed before calling Start {"kind": "Subscription.operators.coreos.com", "error": "failed to get restmapping: no matches for kind \"Subscription\" in version \"operators.coreos.com/v1alpha1\""}
Expected results:
Install succeeded
GatewayAPI tests passed or skipped if no `redhat-operators` catalogsource
Additional info:
slack thread: https://redhat-internal.slack.com/archives/CCH60A77E/p1745488083284879
seems the capabilities OperatorLifecycleManager and Marketplace are required by Ingress in 4.19
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is related to
-
NE-1986 Refactor cluster-ingress-operator's gatewayapi and gatewayclass controllers
-
- To Do
-
- links to