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.

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

Node Scheduling can't be removed #13527

Closed
Toonix opened this issue May 16, 2018 · 3 comments
Closed

Node Scheduling can't be removed #13527

Toonix opened this issue May 16, 2018 · 3 comments
Assignees
Labels
area/workload kind/bug Issues that are defects reported by users or that we know have reached a real release priority/0
Milestone

Comments

@Toonix
Copy link

Toonix commented May 16, 2018

When you set a node Scheduling, you can't remove it.

Automatically pick nodes for each pod matching scheduling rules:
Can't be removed form a deployment

Useful Info
Versions Rancher v2.0.0 UI: v2.0.41
Access local admin
Route containers.run
@tfiduccia
Copy link

Version - 2.0 master 5/16
Now when I switch to a specific node back to Automatically pick nodes, it never finishes the edit. The new pod is stuck in pending and the old pod stays active.
image

@sangeethah
Copy link
Contributor

Tested with v2.0.3-rc1

This issue is still reproducible.

When I remove the node scheduling rule as part of upgrade ,I dont see pods getting recreated.
Also when I view the workload details, the node scheduling rules are still present.

@sangeethah
Copy link
Contributor

Tested with v2.0.3-rc2

Create a workload with node scheduling enabled ( Run all pods for this workload on a specific node or Automatically pick nodes for each pod matching scheduling rules ).
Edit workload and remove the node scheduling rule.
Workload upgrade succeeds and pods get recreated as expected.
Node scheduling rules get removed in the workload after upgrade as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/workload kind/bug Issues that are defects reported by users or that we know have reached a real release priority/0
Projects
None yet
Development

No branches or pull requests

5 participants