Prow: Fix commenter and checkconfig command

[lentzi90]

We have prow jobs that fail with

{"component":"entrypoint","error":"could not start the process: fork/exec /app/robots/commenter/app.binary: no such file or directory","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2023-10-24T17:46:51Z"}

There was a change in upstream that we missed when bumping the image tags.
See https://github.com/kubernetes/test-infra/pull/25384/files

[lentzi90]

/test check-prow-config

[lentzi90]

/override test-ubuntu-integration-main

[metal3-io-bot]

@lentzi90: Overrode contexts on behalf of lentzi90: test-ubuntu-integration-main

In response to this:

/override test-ubuntu-integration-main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[smoshiur1237]

/lgtm

[smoshiur1237]

Good catch, how did we miss it?

[lentzi90]

The check-prow-config that run on the PR that changed the image tags did not use the new image 😅
Then we have just not checked the periodic stale jobs. We should probably add some alerting for that

[lentzi90]

I have applied this in the cluster now (that is why the second check-prow-config was successful)

[lentzi90]

I'm going to self approve this since it is such a small change and prow is broken without it
/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90, smoshiur1237

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lentzi90]

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

[metal3-io-bot]

@lentzi90: Updated the config configmap in namespace prow at cluster default using the following files:

• key config.yaml using file prow/manifests/overlays/metal3/config.yaml

In response to this:

We have prow jobs that fail with

{"component":"entrypoint","error":"could not start the process: fork/exec /app/robots/commenter/app.binary: no such file or directory","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2023-10-24T17:46:51Z"}

There was a change in upstream that we missed when bumping the image tags.
See https://github.com/kubernetes/test-infra/pull/25384/files

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.