-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Broken manifests #8188
Labels
Comments
@alexec Do you know more about the intent behind the manifest change? Was the idea to pin image version to v3.3.0 instead of latest and it's a typo? |
|
Fixing. |
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
Mar 23, 2022
…j#8188 (argoproj#8191) Signed-off-by: Alex Collins <alex_collins@intuit.com>
sarabala1979
pushed a commit
that referenced
this issue
Apr 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Summary
What happened/what you expected to happen?
I want to run hello-world and expect it to successfully complete
Instead when describing the pod I get "failed to resolve reference "quay.io/argoproj/argoexec:untagged"
What version are you running?
I use the latest cluster-install manifests rolled out by argo-cd
This bug does not occur if I pin version to before the following commit 2b5e4a1d2df7877d9b7b7fbedd7136a125a39c8d
It would seem that the above commit broke the manifests.
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: