Skip to content

fix(docs): container-set-template workflow example #10452

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

Merged
merged 1 commit into from
Feb 6, 2023

Conversation

sxllwx
Copy link
Contributor

@sxllwx sxllwx commented Feb 2, 2023

no such file or directory appears when run the container-set-template in the example.

Signed-off-by: scott scottwangsxll@gmail.com

Fixes:

When I tried to run the container-set-template- workflow in the sample, I encountered the following error (and it can be reproduced).

Name:                container-set-template-qkrbz
Namespace:           argo
ServiceAccount:      unset (will run with the default ServiceAccount)
Status:              Error
Message:             Error (exit code 1): open /mainctrfs/workspace/message: no such file or directory
Conditions:
 PodRunning          False
 Completed           True
Created:             Thu Feb 02 17:59:42 +0800 (3 hours ago)
Started:             Thu Feb 02 17:59:42 +0800 (3 hours ago)
Finished:            Thu Feb 02 17:59:54 +0800 (3 hours ago)
Duration:            12 seconds
Progress:            3/4
ResourcesDuration:   10s*(100Mi memory),10s*(1 cpu)

STEP                             TEMPLATE  PODNAME                       DURATION  MESSAGE
 ⚠ container-set-template-qkrbz  main      container-set-template-qkrbz  9s        Error (exit code 1): open /mainctrfs/workspace/message: no such file or directory

Please do not open a pull request until you have checked ALL of these:

  • Create the PR as draft .
  • Run make pre-commit -B to fix codegen and lint problems.
  • Sign-off your commits (otherwise the DCO check will fail).
  • Use a conventional commit message (otherwise the commit message check will fail).
  • "Fixes #" is in both the PR title (for release notes) and this description (to automatically link and close the issue).
  • Add unit or e2e tests. Say how you tested your changes. If you changed the UI, attach screenshots.
  • Github checks are green.
  • Once required tests have passed, mark your PR "Ready for review".

If changes were requested, and you've made them, dismiss the review to get it reviewed again.

Sorry, something went wrong.

@sxllwx sxllwx marked this pull request as draft February 2, 2023 13:53
no such file or directory appears when run the container-set-template
in the example.

Signed-off-by: scott <scottwangsxll@gmail.com>
@sxllwx sxllwx force-pushed the fix/containerset-docs branch from 5418054 to d3d7dc6 Compare February 3, 2023 02:27
@sxllwx sxllwx marked this pull request as ready for review February 3, 2023 03:31
@terrytangyuan terrytangyuan merged commit 7d2a8c3 into argoproj:master Feb 6, 2023
@sxllwx sxllwx deleted the fix/containerset-docs branch February 6, 2023 14:44
isubasinghe pushed a commit to isubasinghe/argo-workflows that referenced this pull request Feb 9, 2023
Signed-off-by: scott <scottwangsxll@gmail.com>
GoshaDo pushed a commit to GoshaDo/argo-workflows that referenced this pull request Feb 9, 2023

Unverified

This user has not yet uploaded their public signing key.
Signed-off-by: scott <scottwangsxll@gmail.com>
Signed-off-by: goshado <goshatoo@gmail.com>
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

Successfully merging this pull request may close these issues.

None yet

2 participants