Open divyenpatel opened 7 years ago
This problem is happening because kops attaches certain taint with master and corresponding toleration is not present in the pod spec. At the same time test pick two ready nodes and attaches the 'vsphere_e2e_label=vsphere_e2e_8b21b01d-2c58-11e7-ae94-0242ac110002' label to those nodes.
Now we have conflicting situation- 1) Pod spec doesn't contain appropriate toleration. 2) Master node, by the virtue of having vsphere_e2e_label=vsphere_e2e_8b21b01d-2c58-11e7-ae94-0242ac110002 label attached to it, is one of the candidate nodes for the pod to be scheduled on.
One way to solve this is on the CI/CD side, so that we don't have to modify the tests that are not part of the kops repo, but the kubernetes repo. CI/CD work flow can explicitly disable scheduling on master and then proceed with labeling the node and pod creation test.
This issue was moved to kubernetes/kops#2730
pod creation with MatchNodeSelector is failing with "FailedScheduling pod (vsphere-e2e-j11sb) failed to fit in any node - fit failure summary on nodes : MatchNodeSelector (2), PodToleratesNodeTaints (1)"
Verified label -
vsphere_e2e_label=vsphere_e2e_8b21b01d-2c58-11e7-ae94-0242ac110002
is set on the master and node15 tests failed from this spec - https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/vsphere_volume_placement.go
pod spec: