-
Notifications
You must be signed in to change notification settings - Fork 952
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
Creating jobs through JobFlow and JobTemplate was unsuccessful #2983
Comments
what is the output of |
It will works after PR #2951 merged. You can validate it use that mr. |
This problem was solved, but I had other unexpected errors when I proceeded to the next step. When I execute the |
@Mufengzhe There is a error shows no permit to update status of JobFlow. Did you have add all the changed in that pr? |
The following is also need.
|
I tried, only need to add this for
|
Have fixed |
@lowang-bh: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
When I want to create JobFlow and JobTempate using examples in the
volcano/example/jobflow
directory of the volcano project, the JobTemplate and JobFlow are successfully created, but the job object resources under JobFlow are not created;And the log information in the controller is:Failed to create jobs of JobFlow default/test: jobs.batch.volcano.sh is forbidden: User "system:serviceaccount:volcano-system:volcano-controllers" cannot create resource "jobs" in API group "batch.volcano.sh" in the namespace "default"
What you expected to happen:
The jobs object under JobFlow is successfully created, and the resource information can be found by using
kubectl get po
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The configuration file in the example/jobflow directory is used
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: