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

"volume node affinity conflict" #3

Closed
ghost opened this issue Jul 4, 2018 · 4 comments
Closed

"volume node affinity conflict" #3

ghost opened this issue Jul 4, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Jul 4, 2018

when i try to move a pod to another node (forced by adding nodeSelector) i get this error. Appearently the lvm-volume is not allowed to be accessed by the other node.
@wavezhang
Copy link
Owner

this plugin is for local lvm, so i add node affinity to pv

@ghost
Copy link
Author

ghost commented Jul 9, 2018

okay. but why do you use the lvm-metadata cluster service then?

@wavezhang
Copy link
Owner

You mean lvmd？Because provisioner need to remove lvm remotely

btw. I‘m considering add support for clvm’

@ghost
Copy link
Author

ghost commented Jul 10, 2018

Ok, i understand. So node affinity is a show-stopper for me.

Thank you kindly for your support though.

@ghost ghost closed this as completed Jul 10, 2018
@ghost ghost mentioned this issue Jul 10, 2018
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wavezhang