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.

Sign up for GitHub

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

Jump to bottom

[BUG] mountpod failed to make JUICEFS_MOUNT_PRIORITY_NAME take effect #677

Closed
molei20021 opened this issue Jun 21, 2023 · 1 comment
Closed

[BUG] mountpod failed to make JUICEFS_MOUNT_PRIORITY_NAME take effect #677

molei20021 opened this issue Jun 21, 2023 · 1 comment
Labels
kind/bug Something isn't working

Comments

@molei20021
Copy link
Contributor

What happened:
mountpod start fail:
Could not mount juicefs: pods "juicefs-k8s-sit-dcn-ai01-node0011-juicefs-35-notebook-msbzib" is forbidden: the string value of PreemptionPolicy (PreemptLowerPriority) must not be provided in pod spec; priority admission controller computed Never from the given PriorityClass name

What you expected to happen:
mountpod start success

How to reproduce it (as minimally and precisely as possible):
1.set csi-node env JUICEFS_MOUNT_PRIORITY_NAME = juicefs-pri-normal
2.create PriorityClass resource
apiVersion: scheduling.k8s.io/v1
description: juicefs-pri-normal
kind: PriorityClass
metadata:
name: juicefs-pri-normal
preemptionPolicy: Never
value: 0

Anything else we need to know?

Environment:

  • JuiceFS CSI Driver version : v0.19.0
  • Kubernetes version (e.g. kubectl version): v1.19.9
@molei20021 molei20021 added the kind/bug Something isn't working label Jun 21, 2023
@molei20021
Copy link
Contributor Author

fixed by #678

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@molei20021