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.

Sign up for GitHub

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

Jump to bottom

Bug with Hauler Registry (hauler serve vs hauler store serve) #129

Closed
zackbradys opened this issue Jul 15, 2023 · 5 comments · Fixed by #130
Closed

Bug with Hauler Registry (hauler serve vs hauler store serve) #129

zackbradys opened this issue Jul 15, 2023 · 5 comments · Fixed by #130

Comments

@zackbradys
Copy link
Member

zackbradys commented Jul 15, 2023 •
edited
Loading

Hauler Version:

GitVersion:  devel
GitCommit:   unknown
BuildDate:   unknown
GoVersion:   go1.17.6
Compiler:    gc
Platform:    linux/amd64

System CPU architecture, OS, and Version:

NAME="Rocky Linux"
VERSION="9.2 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.2"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.2 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.2"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.2"

Describe the Bug:
When serving a registry from the store with hauler store serve, it successfully creates the docker registry v2 directory structure (registry/docker/registry/v2/...), but fails to serve the registry and gives a manifest error.

After this completes/errors, you can run hauler serve registry --root registry and it will successful serve the registry from the docker registry v2 directory structure, but this command alone does not create the structure from the store.

Steps To Reproduce:

[root@rancher-offline hauler]# hauler store load rancher-offline.tar.zst

5:13PM INF loading content from [rancher-offline.tar.zst] to [store]

[root@rancher-offline hauler]# hauler store info

Reference                                Type   # Layers   Size
---------                                ----   --------   ----
### all content loaded into store and correctly listed here

[root@rancher-offline hauler]# hauler store serve
Error: failed commit on ref "manifest-index.docker.io/rancher/mirrored-calico-typha:v3.25.0@sha256:e7a890957f4ce2ceb5f250699421da473df11b8126c04ef25fd25f301f88e777": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-dns-node-cache:1.22.20-build20230406@sha256:ba15671e4aa696f4b418058d9951f57e4c61d8caad758543ab571011cd1937f9": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/nginx-ingress-controller:nginx-1.6.4-hardened4@sha256:4b798bb49dd2a3887a857eb163b2313e6c54b850f957768efd6b09ca36c99a1c": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-ib-sriov-cni:v1.0.2-build20221014@sha256:6d6aa5e134bf06a42776e51efa32154a217927a8de9d7df9aadb82cf5f412a85": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-sig-storage-csi-resizer:v1.7.0@sha256:0beca355bd9ed2d9e91a13d5c0567f58c7dc5da509be369eb5b869043d6ae44e": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-sig-storage-csi-provisioner:v3.4.0@sha256:e9c4aca7ae07fff9fc23615e49b9961f52748e4aa09e89bd8f03cbfa2e82bc3f": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/longhornio-csi-resizer:v1.2.0@sha256:8b9b64cb2efae245ced42f833a9f65effe2f5bfaf07c0579843a164da4636524": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-coredns:v1.10.1-build20230406@sha256:8df3dc8760d988449284aae152e48e7836a5e67d9cc66d846b93e6c3a380e099": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-sriov-network-operator:v1.2.0-build20221014@sha256:7307a0a6bfa2450d7e0ae4e7211e4133b0119ccc41484d67850b6a72b36f8d5d": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-sriov-network-config-daemon:v1.2.0-build20221014@sha256:9d086e61430bae76d3a4d7e3c6f48c5e823f98005b3f93a02912d51eb64d284d": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-sig-storage-csi-attacher:v4.2.0@sha256:bef07b73a7f4a5bfdb1979eb132972c574efaed0f792c95ddc8e8f79765e472a": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-sig-storage-csi-node-driver-registrar:v2.7.0@sha256:545a5b9a4f96f8c5450e4b3f56293638144ca1c2cea625749c4e9800254f563e": unexpected status: 400 Bad Request; failed commit on ref "unknown-sha256:3ec03ad8cd241eaf2e55eff3818de3ee0c0ddafc044b22d012c05fb65765d196": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/longhornio-csi-attacher:v3.2.1@sha256:9a468dee1e8e6574dc34df52cea8695e1c7eaff13848e02c9877e79666a80d4a": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-sriov-network-resources-injector:v1.5-build20221014@sha256:4cdb657bfccb89c4bf38592020d4396c4c9fae5219a3b91fc98a11592745b267": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-cluster-autoscaler:v1.8.6-build20230406@sha256:846665a7ec13ecc2da825621301fc6ad4ddb9dc63936e0ddf925db03c06a133c": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-cilium-hubble-ui-backend:v0.11.0@sha256:6791ff55b4548f5ff75bc6199ca3433dc33322914ff72e2a72ba83456747a7d1": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-etcd:v3.5.7-k3s1-build20230406@sha256:b0eebb20b7845da035ffa5f10ac2c842a724f2a6cfaa9ce24805b57493be8045": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-calico-cni:v3.25.0@sha256:1f5fce3e088a5a76893d49bc017ab062672fded76064f1dc3d156e356441438e": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-sriov-cni:v2.6.3-build20221014@sha256:4f24bc1e2ea8011bb00424703db384c1c2c8fa218b375bcca293ea75beee553d": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-sriov-network-webhook:v1.2.0-build20221014@sha256:2ff061bf65e83dd274076ab68d1482f08b96559a9202f0338bd6bc4f6d5a43b7": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/hardened-cni-plugins:v1.0.1-build20221011@sha256:493d1ba39dfbf2b4ff8581bf0cc4670a3f48090d20aea6959093683462ad3b40": unexpected status: 400 Bad Request; failed commit on ref "manifest-index.docker.io/rancher/mirrored-cloud-provider-vsphere-csi-release-driver:v3.0.1@sha256:6b100ee31b6bbd92e3cef1ab6616335ae3e721d23a419fd53a5864812a18b44b": unexpected status: 400 Bad Request

[root@rancher-offline hauler]# hauler serve registry --root registry
INFO[0000] Starting upload purge in 35m0s                go.version=go1.17.6 version=v3.0.0+unknown
WARN[0000] No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable.  go.version=go1.17.6 version=v3.0.0+unknown
INFO[0000] redis not configured                          go.version=go1.17.6 version=v3.0.0+unknown
INFO[0000] using inmemory blob descriptor cache          go.version=go1.17.6 version=v3.0.0+unknown
INFO[0000] listening on [::]:5000                        go.version=go1.17.6 version=v3.0.0+unknown

[root@rancher-offline rke2]# docker pull localhost:5000/rancher/rke2-runtime:v1.24.15-rke2r1
v1.24.15-rke2r1: Pulling from rancher/rke2-runtime
0be23f481e0b: Pull complete 
Digest: sha256:6abbec66f9dbed57cde7bd0990e4d99943d07d05a68fde75edf339ad975f5f02
Status: Downloaded newer image for localhost:5000/rancher/rke2-runtime:v1.24.15-rke2r1
localhost:5000/rancher/rke2-runtime:v1.24.15-rke2r1
@zackbradys
Copy link
Member Author

Have any ideas? @dweomer @bgulla

@zackbradys
Copy link
Member Author

Possibly related to Issue 12, but using the proposed work around in that issue does not resolve this issue.

@dweomer
Copy link
Contributor

dweomer commented Sep 28, 2023

to be addressed, see:

@dweomer dweomer linked a pull request Sep 28, 2023 that will close this issue
deprecation notices for dl and the non-store version of serve #130
Merged
3 tasks
@zackbradys
Copy link
Member Author

zackbradys commented Sep 28, 2023 •
edited
Loading

there still would be the issue that hauler store serve won't work completely, since both commands were a bit broke. i'm guessing it was a simple implementation error. @dweomer

@zackbradys
Copy link
Member Author

fixed in various recent merges!

@github-project-automation github-project-automation bot moved this to Pending Review in Hauler Feb 14, 2024
@zackbradys zackbradys moved this from Pending Review to Resolved in Hauler Feb 14, 2024
@github-project-automation github-project-automation bot moved this to Pending Review in Hauler Jul 17, 2024
@zackbradys zackbradys moved this from Pending Review to Resolved in Hauler Jul 17, 2024
@HoustonDad HoustonDad mentioned this issue Sep 4, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Hauler
Status: Resolved
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

deprecation notices for dl and the non-store version of serve hauler-dev/hauler
2 participants
@dweomer @zackbradys