[release-1.37] update metadata to 1.37.2 release

[maschmid]

No description provided.

[maschmid]

that generated files failure shows diff

RUN /bin/opm render --skip-tls-verify -o yaml \
-       >> /configs/index.yaml
+      registry.ci.openshift.org/knative/serverless-bundle@sha256:515e93d4eb2309322b2bcf6d0035f53ea982097649a49ad63b275cecd9ac4c06 >> /configs/index.yaml

IMHO is wrong, that bundle contains a 1.38 build. I don't remember how do we normally handle this chicken/egg issue of updating version but not having a bundle with the correct version at the same time? (do we just force merge this one and then do another PR with make generated-files that will use a proper CI bundle ?

[maschmid]

/test 421-images

[maschmid]

/test 421-images

[maschmid]

/retest

[maschmid]

that generated files failure shows diff

RUN /bin/opm render --skip-tls-verify -o yaml \
-       >> /configs/index.yaml
+      registry.ci.openshift.org/knative/serverless-bundle@sha256:515e93d4eb2309322b2bcf6d0035f53ea982097649a49ad63b275cecd9ac4c06 >> /configs/index.yaml

IMHO is wrong, that bundle contains a 1.38 build. I don't remember how do we normally handle this chicken/egg issue of updating version but not having a bundle with the correct version at the same time? (do we just force merge this one and then do another PR with make generated-files that will use a proper CI bundle ?

Trying to fix that by not having the bundle there at all, and only adding the on-cluster-built bundle here: https://github.com/openshift-knative/serverless-operator/pull/4140/changes#diff-d6ee23a8f1c82d66144020b6ba63537a521631d860104bf14f1a2a6e717eb1d3R79

AFAIK, the index image as built in prow is not used anywhere, so it should not matter that that index image will not have the current bundle there at all. (but let's see)

(catalogsource.bash has two paths: one that uses the on-cluster build of index, and the other that uses the konflux index.. we should probabl just not build the index in prow at all)

(we can put it back once we have a bundle for 1.37.2 built in konflux)

[maschmid]

/test 421-test-upgrade

[maschmid]

/test 420-kitchensink-upgrade

[maschmid]

/test 420-kitchensink-upgrade

[maschmid]

Opening #4142 to fix that flaky " eventtransform.go:75: failed to create resource the server could not find the requested resource" kitchensink-upgrade problem in main first.

[maschmid]

INFO[2026-07-14T18:45:25Z] Step kitchensink-upgrade-ipi-install-install failed after 1h12m27s.

failed during cluster install

/test 420-kitchensink-upgrade

[maschmid]

/test 420-kitchensink-upgrade

install timeout again

[maschmid]

/test 420-kitchensink-upgrade

[maschmid]

Error from server (BadRequest): unable to wait for build serverless-bundle-2 to run: timed out waiting for the condition

/test 420-kitchensink-upgrade

[maschmid]

/test 420-kitchensink-upgrade

09:16:12.886 ERROR: Time out of 900 exceeded
09:16:12.889 ERROR: 🚨 Error (code: 71) occurred at ./hack/lib/scaleup.bash:46, with command: return 71

[maschmid]

Analysing the https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift-knative_serverless-operator/4140/pull-ci-openshift-knative-serverless-operator-release-1.37-420-kitchensink-upgrade/2077696949665927168 failure, Claude says:

The test would have passed if it waited ~2 more minutes.

increasing the timeout to 12 minutes then.

[maschmid]

level=error msg=failed to initialize the cluster: Cluster operators authentication, console, image-registry, ingress, monitoring are not available: timed out waiting for the condition

/test 420-kitchensink-upgrade

[dsimansk]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, maschmid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dsimansk,maschmid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment