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

Cannot use optional with input artifacts/S3 #2990

Closed
3 of 4 tasks
alexec opened this issue May 10, 2020 · 0 comments · Fixed by #3019
Closed
3 of 4 tasks

Cannot use optional with input artifacts/S3 #2990

alexec opened this issue May 10, 2020 · 0 comments · Fixed by #3019
Assignees
Labels

Comments

@alexec
Copy link
Contributor

alexec commented May 10, 2020

Checklist:

  • I've included the version. - master
  • I've included reproduction steps.
  • I've included the workflow YAML.
  • I've included the logs.

What happened:

Started a step with an input artifact where the bucket does not exist, step failed.

What you expected to happen:

Artifact was marked optional - should pass.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Argo version:
$ argo version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

  • workflow result:
argo --loglevel DEBUG get <workflowname>
  • executor logs:
kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait
  • workflow-controller logs:
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Logs

argo get <workflowname>
kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Message from the maintainers:

If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@alexec alexec self-assigned this May 10, 2020
alexec added a commit to alexec/argo-workflows that referenced this issue May 12, 2020
@alexec alexec linked a pull request May 12, 2020 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant