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

Error submitting a SLURM job with no execution option #739

Closed
laurentganne opened this issue May 25, 2021 · 0 comments · Fixed by #740
Closed

Error submitting a SLURM job with no execution option #739

laurentganne opened this issue May 25, 2021 · 0 comments · Fixed by #740
Assignees
Labels
bug Something isn't working

Comments

@laurentganne
Copy link
Contributor

Attempting to run a workflow with a slurm job containing no execution option, the workflow fails with this error:

The workflow run step TrainingJobComp_submit ended on error: failed to build job information: invalid execution options datatype for attribute "execution_options" for node "TrainingJobComp": '' expected a map, got 'string'

Stack trace in yorc:

'' expected a map, got 'string'
invalid execution options datatype for attribute "execution_options" for node "TrainingJobComp"
github.com/ystia/yorc/v4/prov/slurm.(*executionCommon).buildJobInfo
	/var/jenkins_home/workspace/yorc/v4.0.5+premium/2@2/prov/slurm/execution.go:385
github.com/ystia/yorc/v4/prov/slurm.(*executionCommon).execute
	/var/jenkins_home/workspace/yorc/v4.0.5+premium/2@2/prov/slurm/execution.go:169
github.com/ystia/yorc/v4/prov/slurm.(*defaultExecutor).ExecOperation
@laurentganne laurentganne added the bug Something isn't working label May 25, 2021
@laurentganne laurentganne self-assigned this May 25, 2021
laurentganne added a commit that referenced this issue May 25, 2021
laurentganne added a commit that referenced this issue May 25, 2021
…cution-option

[Backport 4.0] Checking TOSCA value RawString() to see if property execution_option is defined
loicalbertin added a commit that referenced this issue Jun 11, 2021
…cution-option

[Backport 4.1] Checking TOSCA value RawString() to see if property execution_option is defined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant