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] [JuiceFS] FUSE pod scheduled failed because of conflict port #2668

Closed
zwwhdls opened this issue Feb 28, 2023 · 0 comments · Fixed by #2669
Closed

[BUG] [JuiceFS] FUSE pod scheduled failed because of conflict port #2668

zwwhdls opened this issue Feb 28, 2023 · 0 comments · Fixed by #2669
Labels
bug Something isn't working

Comments

@zwwhdls
Copy link
Member

zwwhdls commented Feb 28, 2023

What is your environment(Kubernetes version, Fluid version, etc.)

Describe the bug
When there are two datasets in different namespaces, fuse pod can not be scheduled because of conflict port.

  Warning  FailedScheduling  8m11s (x1111 over 16h)  default-scheduler  0/14 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 13 node(s) didn't match Pod's node affinity/selector.

What you expect to happen:

How to reproduce it

Additional Information
@zwwhdls zwwhdls added the bug Something isn't working label Feb 28, 2023
@zwwhdls zwwhdls mentioned this issue Feb 28, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

allocate metrics port for multi runtime zwwhdls/fluid
1 participant
@zwwhdls