pull policy "if-not-present" yet still querying remote registry

[jmtd]

This is a little odd. s2i build --pull-policy if-not-present appears to query a remote registry for (at least) metadata even if the named image is present in the local registry.

Log excerpt from https://github.com/jboss-container-images/openjdk/actions/runs/6864309836/job/19052020240 (the original logs are enormous):

DEBUG Executing 's2i build --loglevel=5 --pull-policy if-not-present  --context-dir=undertow-servlet -r=master  https://github.com/jboss-openshift/openshift-quickstarts ubi9/openjdk-21:1.17 integ-ubi9/openjdk-21:1.17  ' command...
ERROR I1127 11:44:13.305506   19494 build.go:52] Running S2I version "v1.3.4"
ERROR I1127 11:44:13.306519   19494 util.go:58] Getting docker credentials for ubi9/openjdk-21:1.17
ERROR I1127 11:44:13.306544   19494 util.go:74] Using  credentials for pulling ubi9/openjdk-21:1.17
ERROR W1127 11:44:13.518495   19494 build.go:167] could not inspect the builder image for labels: reading manifest 1.17 in docker.io/ubi9/openjdk-21: errors:
ERROR denied: requested access to the resource is denied
ERROR unauthorized: authentication required
ERROR I1127 11:44:13.520728   19494 docker.go:491] Using locally available image "docker.io/ubi9/openjdk-21:latest"

Note that the named builder image ubi9/openjdk-17 exists in the local docker container storage, and the rest the S2I process works as expected using the local image.

Confirmed with 1.3.4 and 1.3.9.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[jmtd]

/remove-lifecycle rotten

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

[jmtd]

/reopen

I guess the bot didn’t like my fresh command

[openshift-ci]

@jmtd: Reopened this issue.

In response to this:

/reopen

I guess the bot didn’t like my fresh command

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.

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-sigs/prow repository.

[jmtd]

/reopen
/remove-lifecycle rotten
/lifecycle frozen

[openshift-ci]

@jmtd: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

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-sigs/prow repository.