Change:
// This test verifies we don't allow scheduling of pods in a way that sum of local ephemeral storage limits of pods is greater than machines capacity. // It assumes that cluster add-on pods stay stable and cannot be run in parallel with any other test that touches Nodes or Pods. // It is so because we need to have precise control on what's running in the cluster. <del> It("validates local ephemeral storage resource limits of pods that are allowed to run [Conformance]", func() { </del> <ins> It("validates local ephemeral storage resource limits of pods that are allowed to run [Feature:LocalStorageCapacityIsolation]", func() { </ins> nodeMaxAllocatable := int64(0) nodeToAllocatableMap := make(map[string]int64)

Discussion:
Is this a BUG REPORT or FEATURE REQUEST?: What happened: There are several CI e2e jobs that are failing this new Conformance test: [sig-scheduling] SchedulerPredicates [Serial] validates local ephemeral storage resource limits of pods that are allowed to run [Conformance] 1m6s Expected <bool: false to equal <bool: true Here is one such failure: https://k8s- Moreover, this new test has been consistently failing on multiple e2e jobs ever since it was merged to master: https://k8s- https://k8s- https://k8s- https://k8s- Here is the pull request for the new test: I don't know if this is a legitimate problem with the scheduler in these jobs and if the test is running and passing elsewhere, or if there is a flaw in the test itself.
CC to comment on the correctness of this new test, since it is failing both for kubeadm e2es and kops as well: https://k8s- I haven't been able to find any other e2e jobs where this test isn't skipped, so I don't know if it's green anywhere.
Also failing gce-serial and gke-serial: https://k8s- https://k8s-
Updated title/description since this isn't a kubeadm-specific CI failure.
Sorry for that, I will look into it /assign
LocalEphemeralStorage will be to node Status's capacity when feature gate is enabled. In e2e tests ,the feature gate is not enabled, so the error happened.
Thanks for looking into this, I'll be out of the office for the next few days (back on September 5th), so I would include more people on that PR so it's not stalled on my feedback. My personal vote is to change the test's tag from "[Conformance]" to "[Feature:EphemeralStorage]" so that test jobs will have to opt into running the test, but I don't know if we already have the pattern elsewhere of checking for whether or not a feature is enabled and skipping an enabled test anyway. SIG Testing might have guidelines for best practices here.

Sorry for not understanding the tag's meaning
/kind e2e-test-failure cc
[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/cluster-lifecycle sig/scheduling: Issue will be escalated to these SIGs if needed. priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. kind/bug: Fixes a bug discovered during the current release. <detailsAdditional instructions available <a href=""here</a</details
from what I can see this test has never passed for certain test suites. e.g. https://k8s- Would it be appropriate to revert the test?
See ; which fixes the main problem. I just asked to bump the priority