1. Proposed title of this feature request Allow multiple toleration values with the same key 3. What is the nature and description of the request? A bug in Kubernetes prior to version 1.15 breaks the use of multiple toleration values with the same key. This PR further describes the issue: https://github.com/kubernetes/kubernetes/pull/81732 (the implementation of the fix is different between Kubernetes versions). 10. List any affected packages or components. Scheduler Please let me know if any more information is required.
Mike is looking at it.
This bug hasn't had any engineering activity in the last ~30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it and remove the "LifecycleStale" keyword, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
The PR adding this has been approved but is constantly failing test pull-ci-openshift-origin-release-3.11-e2e-gcp. Is this test flaking?
Have finished doing a sanity check on the bug and it works, developed test case and sent the test case for review, once i get approvals will move the bug to verified state, thanks !!
Verified with v3.11.232 [root@dhcp-140-138 ~]# oc version oc v3.11.232 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Moving the bug to verified state as all the test cases were approved and when run on the 3.11 cluster they pass.
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-2020:2477