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

NoDiskConflicts predicate doesn't work for Persistent Volumes #29670

Closed
rootfs opened this issue Jul 27, 2016 · 6 comments
Closed

NoDiskConflicts predicate doesn't work for Persistent Volumes #29670

rootfs opened this issue Jul 27, 2016 · 6 comments
Labels
area/kubelet lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@rootfs
Copy link
Contributor

rootfs commented Jul 27, 2016

In its implementation, only basic volumes are inspected. Persistent volumes are skipped.
@rootfs rootfs mentioned this issue Aug 1, 2016
Closed
@rootfs rootfs mentioned this issue Aug 17, 2016
Merged
ericchiang pushed a commit to ericchiang/kubernetes that referenced this issue Aug 18, 2016
Merge pull request kubernetes#30817 from rootfs/nodiskconflict-doc
ff9980e 
Automatic merge from submit-queue

more explictly about NoDiskConflicts policy and applicable volume types

partially clarify kubernetes#29670

@kubernetes/sig-scheduling
xingzhou pushed a commit to xingzhou/kubernetes that referenced this issue Dec 15, 2016
Merge pull request kubernetes#30817 from rootfs/nodiskconflict-doc
b16f0e1 
Automatic merge from submit-queue

more explictly about NoDiskConflicts policy and applicable volume types

partially clarify kubernetes#29670

@kubernetes/sig-scheduling
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 31, 2017
@0xmichalis
Copy link
Contributor

/sig storage
/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. labels Jun 23, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 23, 2017
@rootfs
Copy link
Contributor Author

rootfs commented Jun 23, 2017

/assign @humblec

@k8s-ci-robot
Copy link
Contributor

@rootfs: GitHub didn't allow me to assign the following users: humblec.

Note that only kubernetes members can be assigned.

In response to this:

/assign @humblec

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 29, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 28, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/kubelet lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@0xmichalis @rootfs @k8s-github-robot @k8s-ci-robot @fejta-bot