K8s schedule pods to removed nodes
Bug #1472415 reported by
hongbin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Invalid
|
Undecided
|
hongbin |
Bug Description
Steps to reproduce:
* Create a k8s cluster with 2 nodes
$ magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 2
* Reduce the node count to 1
$ magnum bay-update k8sbay replace node_count=1
* Create 2 pods
$ magnum pod-create --manifest ./redis-master.yaml --bay k8sbay
$ magnum pod-create --manifest ./redis-proxy.yaml --bay k8sbay
Then, you should see one of the pods are scheduled to a removed nodes.
Changed in magnum: | |
assignee: | nobody → hongbin (hongbin034) |
Changed in magnum: | |
milestone: | none → mitaka-1 |
To post a comment you must log in.
This is actually a bug from k8s https:/ /github. com/GoogleCloud Platform/ kubernetes/ issues/ 7222 . The fix has been committed at May 2015. Possibly, we need to upgrade the fedora image to fix that.