OpenAPI SchemaError - 4.22.0-okd-scos.ec.8

[buschviper]

Hi everyone

I've ignited a quite fresh OKD cluster and I'm encountering a strange blocking issue, when I try to apply Helm charts (either via ArgoCD or directly with helm install).

ComparisonError: Failed to load target state: failed to get cluster version for cluster "https://kubernetes.default.svc": failed to get cluster info for "https://kubernetes.default.svc": error synchronizing cache state : failed to load open api schema while syncing cluster cache: error getting openapi resources: SchemaError(com.github.operator-framework.operator-lifecycle-manager.pkg.package-server.apis.operators.v1.PackageManifest.spec): unknown model in reference: "github.com~1operator-framework~1operator-lifecycle-manager~1pkg~1package-server~1apis~1operators~1v1.PackageManifestSpec"

Cluster connection state details:
failed to load open api schema while syncing cluster cache: error getting openapi resources: SchemaError(com.github.operator-framework.operator-lifecycle-manager.pkg.package-server.apis.operators.v1.PackageManifest.spec): unknown model in reference: "github.com~1operator-framework~1operator-lifecycle-manager~1pkg~1package-server~1apis~1operators~1v1.PackageManifestSpec"

I cannot ignore OpenAPI validation at this point as it happens right in the beginning during the cluster KubeAPI connection.

As I understand the issue, there must be one OLM repository delivering broken manifests. But how can I find and isolate this without completely removing OLM?

The only change I made to the cluster after ignition is the installation of an operator based ArgoCD instance (and setup of an htpasswd auth).

I'm on the update stream https://amd64.origin.releases.ci.openshift.org/graph with channel stable-scos-4 Here's the version history of the cluster:

Version | State | Started | Completed
4.22.0-okd-scos.ec.8 | Completed | 28. Feb. 2026, 22:05 | 28. Feb. 2026, 23:03
4.22.0-okd-scos.ec.7 | Completed | 28. Feb. 2026, 18:05 | 28. Feb. 2026, 19:14
4.22.0-okd-scos.ec.6 | Completed | 25. Feb. 2026, 09:30 | 28. Feb. 2026, 17:55
4.22.0-okd-scos.ec.4 | Completed | 24. Feb. 2026, 23:53 | 25. Feb. 2026, 00:56
4.22.0-okd-scos.ec.3 | Completed | 24. Feb. 2026, 22:32 | 24. Feb. 2026, 23:36
4.22.0-okd-scos.ec.2 | Completed | 24. Feb. 2026, 15:36 | 24. Feb. 2026, 22:23

I cannot find anything related in any open or closed issues, which makes me wonder if I'm the only one with such a problem...

Anyhow, all suggestions and ideas are welcome :)

[buschviper]

I'm closing my question as I re-ignited my cluster with 4.21.0-okd-scos.9 and it's working without the mentioned problems.