We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
When I set overcommit plugin argument: overcommit-factor to '2' in configmap, like:
overcommit
overcommit-factor
And then volcano scheduler threw out a warning, and my configuration did not take effect.
I think the question was probably caused by type assertions in plugin argument interface:
volcano/pkg/scheduler/framework/arguments.go
Line 59 in 59e58c2
Current method could not convert int to float64.
int
float64
What you expected to happen:
Interger value can be readin as well.
How to reproduce it (as minimally and precisely as possible):
As below, and would also happen on other plugins.
Anything else we need to know?:
Environment:
kubectl version
uname -a
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What happened:
When I set
overcommit
plugin argument:overcommit-factor
to '2' in configmap, like:And then volcano scheduler threw out a warning, and my configuration did not take effect.
I think the question was probably caused by type assertions in plugin argument interface:
volcano/pkg/scheduler/framework/arguments.go
Line 59 in 59e58c2
Current method could not convert
int
tofloat64
.What you expected to happen:
Interger value can be readin as well.
How to reproduce it (as minimally and precisely as possible):
As below, and would also happen on other plugins.
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: