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

Grafana Operator MANIFEST_UNKNOWN #44

Open
amayacitta opened this issue Oct 30, 2024 · 2 comments
Open

Grafana Operator MANIFEST_UNKNOWN #44

amayacitta opened this issue Oct 30, 2024 · 2 comments

Comments

@amayacitta
Copy link

hi guys, there is an issue with the Grafana Operator in your projects.registry.vmware.com container registry, the latest build as per the below URL kicks out an error that the manifest is unknown. I've tried this on two different environments, so think its a general issue. I tried searching the container registry but cant find the grafana-operator to try a different URL.

Can someone take a look at the below yaml manifest and check either the path or the SHA256 hash.

https://vsphere-tmm.github.io/Supervisor-Services/supervisor-services-labs/grafana-operator/v5.9.0/grafana-operator.yaml

The error (same across multiple environments) is:

Reason: ReconcileFailed. Message: vendir: Error: Syncing directory '0': Syncing directory '.' with imgpkgBundle contents: Fetching image: GET https://projects.registry.vmware.com/v2/vsphere-labs/grafana-operator/manifests/sha256:a74b04131c238e08ad4330bc04ac6d82ac00b38f90da48119fc2d95b5458f413: MANIFEST_UNKNOWN: The named manifest is not known to the registry.; map[manifest:vsphere-labs/grafana-operator] .

@amayacitta
Copy link
Author

amayacitta commented Nov 7, 2024

For anyone else out there, logged a commercial ticket with Broadcom. Engineering have confirmed the artifact is missing from the container registry. It's been looked at.

Seems this git repo isn't looked at often for issues. Hence the commercial ticket.

@papivot
Copy link
Collaborator

papivot commented Nov 8, 2024

@amayacitta This is being worked on. This artifact was missed when they migrated the registry artifacts from the VMware system to Broadcom's system. We are updating it soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants