+++ This bug was initially created as a clone of Bug #1602054 +++ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. Set up an AWS M5 node 2. Attach more than 27 EBS volumes to pods Actual results: The attaches fail. Expected results: Success. Additional info: See: https://github.com/kubernetes/kubernetes/issues/59015 Fixed in Kube 1.11 by: https://github.com/kubernetes/kubernetes/pull/64154 --- Additional comment from Hemant Kumar on 2018-07-17 14:38:40 EDT --- It may be possible to fix this --- Additional comment from Hemant Kumar on 2018-07-17 15:18:09 EDT --- Sorry my comment got submitted before I can finish typing. It is probably possible to fix this without needing volume limit feature in 3.9. It is not super clean I think but EC2 instance type is available as label in node Object and hence scheduler can potentially look at that label and deduce volume attach limit from it rather than going on with hardcoded values. I will try and open a PR for it. --- Additional comment from Hemant Kumar on 2018-07-19 15:38:03 EDT --- upstream PR - https://github.com/kubernetes/kubernetes/pull/66397
https://github.com/openshift/origin/pull/20439
M5/C5 server installation is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1625914
It is passed on openshift v3.11.0-0.32.0 kubernetes v1.11.0+d4cacc0 M5/C5 Instance can attach 35 ebs volumes. If create more than 25, pods could not running, error message is as below: Warning FailedScheduling 1m (x111 over 6m) default-scheduler 0/3 nodes are available: 1 node(s) exceed max volume count, 2 node(s) didn't match node selector.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652