K8s schedule pods to removed nodes

Bug #1472415 reported by hongbin
6
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.

hongbin (hongbin034)
Changed in magnum:
assignee: nobody → hongbin (hongbin034)
Revision history for this message
hongbin (hongbin034) wrote :

This is actually a bug from k8s https://github.com/GoogleCloudPlatform/kubernetes/issues/7222 . The fix has been committed at May 2015. Possibly, we need to upgrade the fedora image to fix that.

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Revision history for this message
Jaycen Grant (jaycen-v-grant) wrote :

Pod commands have been removed.

Changed in magnum:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.