Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.17.14 internal registry default-route-openshift-image-registry.apps-crc.testing is not supported #1014

Open
lilyLuLiu opened this issue Feb 10, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@lilyLuLiu
Copy link

lilyLuLiu commented Feb 10, 2025

Step executing "oc image mirror registry.access.redhat.com/ubi8/httpd-24:latest=default-route-openshift-image-registry.apps-crc.testing/testproj/hello:test --insecure=true --filter-by-os=linux" succeeds: command 'oc image mirror registry.access.redhat.com/ubi8/httpd-24:latest=default-route-openshift-image-registry.apps-crc.testing/testproj/hello:test --insecure=true --filter-by-os=linux', expected to succeed, exited with exit code: 1
Command stdout:
Command stderr: default-route-openshift-image-registry.apps-crc.testing/
  testproj/hello
    blobs:
      registry.access.redhat.com/ubi8/httpd-24 sha256:c22d3da7eab163844b806a6e9d20dfdc98b6651a9a1a606203e3de94476c9cb4 19.01KiB
    .........
      registry.access.redhat.com/ubi8/httpd-24 sha256:1f83faba967886e1fcf0eed682ae6b5f51e4152ec0c4c7ec25b80664df154308 81.99MiB
    manifests:
      sha256:3d0a91d992639fcd58bd5ce3067f74187e88951d85485ea8abbf9b0a6d9259fa
      sha256:8960fa2b8e42f6a93e2eb08cbd273a027819fcc418e794029987bbe8e83c5f7f
      sha256:c07a4a0e9fb4f8707e87b8f5e17df16e030d17352172a40713f4403a51695b6d
      sha256:fbcc31fc83c856e67a6dd8531b9c12024faaf227d91c519b817326aa4e9a370a
      sha256:2c813ba39f1aaf42fdaab448111fc0c154286a0615798fd5235965a3f57e8527 -> test
  stats: shared=0 unique=16 size=652.8MiB ratio=1.00
phase 0:
  default-route-openshift-image-registry.apps-crc.testing testproj/hello blobs=16 mounts=0 manifests=5 shared=0
info: Planning completed in 2.03s
error: unable to upload blob sha256:e2ef002284bb22f409d95231a4ee42a3fe4e8216d08903c57f0cb3389a1a722f to default-route-openshift-image-registry.apps-crc.testing/testproj/hello: endpoint "https://default-route-openshift-image-registry.apps-crc.testing"/ does not support v2 API (got 503 Service Unavailable)
error: unable to upload blob sha256:9af5caa0c3656d6068a4d48381be295b8072f82bf99c2bb85f73b430d1409045 to default-route-openshift-image-registry.apps-crc.testing/testproj/hello: endpoint "https://default-route-openshift-image-registry.apps-crc.testing"/ does not support v2 API (got 503 Service Unavailable)
info: Mirroring completed in 0s (0B/s)
error: one or more errors occurred while uploading images
@praveenkumar praveenkumar self-assigned this Feb 10, 2025
@praveenkumar praveenkumar added the bug Something isn't working label Feb 10, 2025
@praveenkumar
Copy link
Member

Looks like somehow the registry spec is not updated with https://github.com/crc-org/snc/blob/release-4.17/snc.sh#L209 one and no route is created

$ oc get route -A
NAMESPACE                  NAME              HOST/PORT                                          PATH   SERVICES          PORT    TERMINATION            WILDCARD
openshift-authentication   oauth-openshift   oauth-openshift.apps-crc.testing                          oauth-openshift   6443    passthrough/Redirect   None
openshift-console          console           console-openshift-console.apps-crc.testing                console           https   reencrypt/Redirect     None
openshift-console          downloads         downloads-openshift-console.apps-crc.testing              downloads         http    edge/Redirect          None
openshift-ingress-canary   canary            canary-openshift-ingress-canary.apps-crc.testing          ingress-canary    8443    passthrough/Redirect   None

From the CI logs https://jenkins-csb-crc-crcqe.dno.corp.redhat.com/job/eng-crc-snc/404/console shows the patch is applied but not sure why it is not become part of registry. After manually apply the patch I can see the route. I am regenerating the bundle and try to figure out how to detect those patch in case something not applied before generating the bundle.

@lilyLuLiu
Copy link
Author

The tests pass with the new updated bundles on all platforms.

@praveenkumar
Copy link
Member

We might need to add step to check patches which we apply should be present to cluster before we start bundle process. Keeping it open as of now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants