ci-cri-containerd-e2e-cos-gce-reboot #1619877651143462912
Recent runs || View in Spyglass
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\sinbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:19.487 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:10:49.367 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:10:49.367 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:10:49.367 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:10:49.367 Jan 30 02:10:49.367: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:10:49.368 Jan 30 02:10:49.408: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:51.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:53.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:55.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:57.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:59.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:01.447: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:03.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:05.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:07.447: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:09.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:11.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:13.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:15.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:17.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.487: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.487: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:19.487 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:19.487 (30.12s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:19.487 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:11:19.488 Jan 30 02:11:19.527: INFO: Unexpected error: <*url.Error | 0xc000a6b8c0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0038b6b90>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc002921f80>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc003d74780>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:11:19.527 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:19.527 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:19.527 Jan 30 02:11:19.527: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:19.567 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:19.567 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:19.567 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:19.567 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:19.567 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:19.567 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:19.567 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:19.567 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:19.567 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\sinbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:19.487 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:10:49.367 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:10:49.367 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:10:49.367 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:10:49.367 Jan 30 02:10:49.367: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:10:49.368 Jan 30 02:10:49.408: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:51.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:53.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:55.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:57.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:59.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:01.447: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:03.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:05.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:07.447: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:09.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:11.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:13.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:15.449: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:17.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.448: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.487: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:19.487: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:19.487 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:19.487 (30.12s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:19.487 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:11:19.488 Jan 30 02:11:19.527: INFO: Unexpected error: <*url.Error | 0xc000a6b8c0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0038b6b90>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc002921f80>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc003d74780>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:11:19.527 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:19.527 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:19.527 Jan 30 02:11:19.527: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:19.567 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:19.567 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:19.567 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:19.567 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:19.567 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:19.567 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:19.567 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:19.567 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:19.567 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\soutbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:20:16.964 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:19:46.843 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:19:46.843 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:19:46.843 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:19:46.843 Jan 30 02:19:46.843: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:19:46.845 Jan 30 02:19:46.884: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:48.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:50.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:52.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:54.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:56.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:58.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:00.926: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:02.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:04.927: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:06.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:08.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:10.926: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:12.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:14.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.963: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.964: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:20:16.964 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:20:16.964 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:20:16.964 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:20:16.964 Jan 30 02:20:17.004: INFO: Unexpected error: <*url.Error | 0xc004710690>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004700460>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004781ec0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc0047141c0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:20:17.004 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:20:17.004 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:20:17.004 Jan 30 02:20:17.004: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:20:17.043 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:20:17.043 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:20:17.043 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:20:17.043 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:20:17.043 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:20:17.043 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:20:17.043 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:20:17.043 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:20:17.043 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\soutbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:20:16.964 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:19:46.843 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:19:46.843 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:19:46.843 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:19:46.843 Jan 30 02:19:46.843: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:19:46.845 Jan 30 02:19:46.884: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:48.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:50.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:52.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:54.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:56.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:19:58.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:00.926: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:02.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:04.927: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:06.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:08.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:10.926: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:12.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:14.925: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.924: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.963: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:16.964: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:20:16.964 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:20:16.964 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:20:16.964 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:20:16.964 Jan 30 02:20:17.004: INFO: Unexpected error: <*url.Error | 0xc004710690>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004700460>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004781ec0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc0047141c0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:20:17.004 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:20:17.004 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:20:17.004 Jan 30 02:20:17.004: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:20:17.043 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:20:17.043 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:20:17.043 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:20:17.043 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:20:17.043 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:20:17.043 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:20:17.043 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:20:17.043 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:20:17.043 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:49.694 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:19.573 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:19.573 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:19.573 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:11:19.573 Jan 30 02:11:19.573: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:11:19.574 Jan 30 02:11:19.614: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:21.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:23.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:25.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:27.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:29.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:31.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:33.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:35.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:37.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:39.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:41.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:43.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:45.656: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:47.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.694: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.694: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:49.694 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:49.694 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:49.694 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:11:49.694 Jan 30 02:11:49.734: INFO: Unexpected error: <*url.Error | 0xc0038a7da0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004484e10>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc003b45d10>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d855a0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:11:49.734 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:49.734 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:49.734 Jan 30 02:11:49.734: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:49.773 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:49.773 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:49.773 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:49.773 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:49.773 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:49.773 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:49.773 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:49.773 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:49.773 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:49.694 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:19.573 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:19.573 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:19.573 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:11:19.573 Jan 30 02:11:19.573: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:11:19.574 Jan 30 02:11:19.614: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:21.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:23.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:25.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:27.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:29.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:31.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:33.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:35.653: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:37.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:39.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:41.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:43.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:45.656: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:47.654: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.655: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.694: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:11:49.694: INFO: Unexpected error: <*errors.errorString | 0xc000205c70>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:11:49.694 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:49.694 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:49.694 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:11:49.694 Jan 30 02:11:49.734: INFO: Unexpected error: <*url.Error | 0xc0038a7da0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004484e10>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc003b45d10>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d855a0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:11:49.734 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:11:49.734 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:49.734 Jan 30 02:11:49.734: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:11:49.773 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:49.773 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:49.773 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:11:49.773 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:11:49.773 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:49.773 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:11:49.773 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:49.773 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:11:49.773 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sunclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] wait for service account "default" in namespace "reboot-4353": timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:22:46.509 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:20:17.066 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:20:17.067 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:20:17.067 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:20:17.067 Jan 30 02:20:17.067: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:20:17.068 Jan 30 02:20:17.107: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:19.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:21.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:23.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:25.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:27.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:29.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:31.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:33.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:35.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:37.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:39.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:22:46.508: INFO: Unexpected error: <*fmt.wrapError | 0xc004d68000>: { msg: "wait for service account \"default\" in namespace \"reboot-4353\": timed out waiting for the condition", err: <*errors.errorString | 0xc000205c70>{ s: "timed out waiting for the condition", }, } [FAILED] wait for service account "default" in namespace "reboot-4353": timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:22:46.509 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:22:46.509 (2m29.442s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:22:46.509 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:22:46.509 Jan 30 02:22:46.549: INFO: Unexpected error: <*url.Error | 0xc0027ec000>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0046fe140>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004780960>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc0004aa000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:22:46.55 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:22:46.55 (41ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:22:46.55 Jan 30 02:22:46.550: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:22:46.589 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:22:46.589 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:22:46.589 STEP: Collecting events from namespace "reboot-4353". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:22:46.589 Jan 30 02:22:46.629: INFO: Unexpected error: failed to list events in namespace "reboot-4353": <*url.Error | 0xc004780d80>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-4353/events", Err: <*net.OpError | 0xc003f32780>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004780d50>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d684c0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:22:46.629 (40ms) [FAILED] failed to list events in namespace "reboot-4353": Get "https://34.168.242.120/api/v1/namespaces/reboot-4353/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:22:46.629 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:22:46.629 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:22:46.629 STEP: Destroying namespace "reboot-4353" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:22:46.629 [FAILED] Couldn't delete ns: "reboot-4353": Delete "https://34.168.242.120/api/v1/namespaces/reboot-4353": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-4353", Err:(*net.OpError)(0xc0046ff0e0)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:22:46.669 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:22:46.669 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:22:46.669 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:22:46.669 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sunclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] wait for service account "default" in namespace "reboot-4353": timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:22:46.509 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:20:17.066 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:20:17.067 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:20:17.067 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:20:17.067 Jan 30 02:20:17.067: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:20:17.068 Jan 30 02:20:17.107: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:19.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:21.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:23.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:25.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:27.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:29.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:31.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:33.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:35.147: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:37.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:20:39.148: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:22:46.508: INFO: Unexpected error: <*fmt.wrapError | 0xc004d68000>: { msg: "wait for service account \"default\" in namespace \"reboot-4353\": timed out waiting for the condition", err: <*errors.errorString | 0xc000205c70>{ s: "timed out waiting for the condition", }, } [FAILED] wait for service account "default" in namespace "reboot-4353": timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 02:22:46.509 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:22:46.509 (2m29.442s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:22:46.509 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:22:46.509 Jan 30 02:22:46.549: INFO: Unexpected error: <*url.Error | 0xc0027ec000>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0046fe140>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004780960>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc0004aa000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:22:46.55 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:22:46.55 (41ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:22:46.55 Jan 30 02:22:46.550: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:22:46.589 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:22:46.589 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:22:46.589 STEP: Collecting events from namespace "reboot-4353". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:22:46.589 Jan 30 02:22:46.629: INFO: Unexpected error: failed to list events in namespace "reboot-4353": <*url.Error | 0xc004780d80>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-4353/events", Err: <*net.OpError | 0xc003f32780>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc004780d50>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d684c0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:22:46.629 (40ms) [FAILED] failed to list events in namespace "reboot-4353": Get "https://34.168.242.120/api/v1/namespaces/reboot-4353/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:22:46.629 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:22:46.629 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:22:46.629 STEP: Destroying namespace "reboot-4353" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:22:46.629 [FAILED] Couldn't delete ns: "reboot-4353": Delete "https://34.168.242.120/api/v1/namespaces/reboot-4353": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-4353", Err:(*net.OpError)(0xc0046ff0e0)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:22:46.669 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:22:46.669 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:22:46.669 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:22:46.669 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sswitching\soff\sthe\snetwork\sinterface\sand\sensure\sthey\sfunction\supon\sswitch\son$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:19:46.574 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:49.777 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:49.777 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:49.777 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:11:49.777 Jan 30 02:11:49.777: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:11:49.778 Jan 30 02:11:49.817: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 02:13:42.513 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 02:13:42.594 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:13:42.674 (1m52.897s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:13:42.674 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:13:42.674 (0s) > Enter [It] each node by switching off the network interface and ensure they function upon switch on - test/e2e/cloud/gcp/reboot.go:115 @ 01/30/23 02:13:42.674 Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-w9vk Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-9nd1 Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-w6qn Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:13:42.990: INFO: Node bootstrap-e2e-minion-group-w9vk has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Node bootstrap-e2e-minion-group-9nd1 has 4 assigned pods with no liveness probes: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.991: INFO: Node bootstrap-e2e-minion-group-w6qn has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:43.052: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 62.737814ms Jan 30 02:13:43.052: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.052: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 62.538108ms Jan 30 02:13:43.052: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.053: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 62.500488ms Jan 30 02:13:43.053: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.053: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:43.053: INFO: Getting external IP address for bootstrap-e2e-minion-group-w9vk Jan 30 02:13:43.053: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w9vk(104.198.6.37:22) Jan 30 02:13:43.061: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=true. Elapsed: 70.557007ms Jan 30 02:13:43.061: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.061: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 70.749625ms Jan 30 02:13:43.061: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 70.519251ms Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.061: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 70.490744ms Jan 30 02:13:43.061: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 71.16232ms Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: stdout: "" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: stderr: "" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: exit code: 0 Jan 30 02:13:43.595: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be false Jan 30 02:13:43.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:45.107: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.116441173s Jan 30 02:13:45.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 2.115963082s Jan 30 02:13:45.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:45.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:45.684: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:47.107: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.116811317s Jan 30 02:13:47.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 4.116320542s Jan 30 02:13:47.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:47.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:47.728: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:49.104: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.11345029s Jan 30 02:13:49.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:49.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 6.114197396s Jan 30 02:13:49.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:49.770: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:51.103: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.113180079s Jan 30 02:13:51.103: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:51.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 8.114085717s Jan 30 02:13:51.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:51.814: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:53.104: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.113868864s Jan 30 02:13:53.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:53.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 10.114674354s Jan 30 02:13:53.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:53.857: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:55.106: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 12.11605325s Jan 30 02:13:55.106: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:13:55.106: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:55.106: INFO: Getting external IP address for bootstrap-e2e-minion-group-9nd1 Jan 30 02:13:55.106: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-9nd1(35.247.49.149:22) Jan 30 02:13:55.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 12.116135733s Jan 30 02:13:55.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: stdout: "" Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: stderr: "" Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: exit code: 0 Jan 30 02:13:55.647: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be false Jan 30 02:13:55.689: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:55.900: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:57.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 14.113256532s Jan 30 02:13:57.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:57.732: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:57.943: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 16.113211701s Jan 30 02:13:59.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:13:59.104: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:59.104: INFO: Getting external IP address for bootstrap-e2e-minion-group-w6qn Jan 30 02:13:59.104: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w6qn(34.105.21.11:22) Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: stdout: "" Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: stderr: "" Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: exit code: 0 Jan 30 02:13:59.663: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be false Jan 30 02:13:59.705: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.775: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.985: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:01.748: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:01.818: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:02.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:03.791: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:03.861: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:04.072: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:05.834: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:05.912: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:06.115: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:07.877: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:07.956: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:08.158: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:09.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:09.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:10.201: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:11.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:12.042: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:12.244: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.007: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.085: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.288: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.049: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.128: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.330: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.381: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.135: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.425: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.255: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.468: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.293: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.298: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.511: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.336: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.341: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.562: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.378: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.383: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.421: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.426: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.463: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.474: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.754: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:14:32.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:34.506: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:34.517: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:34.879: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:36.548: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:36.562: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:36.922: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:38.613: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:38.623: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:38.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:40.656: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:40.665: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:41.007: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:42.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:42.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:43.070: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:44.767: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:14:44.767: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:14:44.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:44.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:45.111: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:46.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:46.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:47.155: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:48.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:48.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:49.198: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:50.942: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:50.942: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:51.240: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:52.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:52.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:53.283: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:55.030: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:55.030: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:55.326: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:57.076: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:57.076: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:57.369: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:59.119: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:59.119: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:59.412: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:01.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:01.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:01.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:03.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:03.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:03.497: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:05.251: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:05.251: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:05.539: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:07.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:07.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:07.582: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:09.338: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:09.338: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:09.625: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:11.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:11.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:11.668: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:13.427: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:13.427: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:13.710: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:15.471: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:15.471: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:15.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:17.515: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:17.515: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:17.796: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:19.558: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:19.558: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:19.839: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:21.602: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:21.602: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:21.882: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:23.653: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:23.653: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:23.926: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:25.696: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:25.696: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:25.969: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:27.741: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:27.741: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:28.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:29.784: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:29.784: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:30.057: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:31.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:31.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:32.100: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:33.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:33.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:34.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:35.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:35.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:36.196: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:37.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:37.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:38.238: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:40.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:40.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:40.284: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:42.067: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:42.067: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:42.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:44.113: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:44.113: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:44.384: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:46.156: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:46.156: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:46.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:48.200: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:48.200: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:48.470: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:50.243: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:50.243: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:50.512: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:52.284: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:52.284: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:52.555: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:54.336: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:54.336: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:54.599: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:56.376: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:56.376: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:56.639: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:58.416: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:58.416: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:58.680: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:00.457: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:00.457: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:00.720: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:02.497: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:02.497: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:02.760: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:04.536: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:04.536: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:04.800: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:06.577: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:06.577: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:06.840: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:08.618: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:08.618: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:08.880: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:10.659: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:10.659: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:10.920: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:12.700: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:12.700: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:12.960: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:14.740: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:14.740: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:15.000: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:16.780: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:16.780: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:17.041: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:18.819: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:18.819: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:19.081: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:20.859: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:20.859: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:21.121: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:22.899: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:22.899: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:23.161: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:24.939: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:24.939: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:25.201: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:26.980: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:26.980: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:27.241: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:29.021: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:29.021: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:29.281: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:31.062: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:31.062: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:31.321: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:33.101: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:33.101: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:33.361: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:35.141: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:35.141: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:35.401: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:37.180: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:37.180: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:37.441: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:39.221: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:39.221: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:39.481: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:41.261: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:41.261: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:41.521: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:43.301: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:43.301: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:43.561: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:45.341: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:45.341: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:45.602: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:47.380: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:47.381: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:47.641: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:49.421: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:49.421: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:49.682: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:51.460: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:51.460: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:51.721: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:53.501: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:53.501: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:53.762: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:55.541: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:55.541: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:55.801: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:57.581: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:57.581: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:57.841: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:59.621: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:59.621: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:59.881: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:01.662: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:01.662: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:01.921: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:03.702: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:03.702: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:03.961: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:05.745: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:05.745: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:06.001: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:07.785: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:07.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:08.041: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:09.825: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:09.825: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:10.081: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:11.865: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:11.865: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:12.121: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:13.905: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:13.905: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:14.161: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:15.945: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:15.946: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:16.201: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:17.985: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:17.985: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:18.241: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:20.025: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:20.025: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:20.282: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:22.065: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:22.065: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:22.322: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:24.106: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:24.106: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:24.363: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:26.146: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:26.146: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:26.403: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:28.186: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:28.186: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:28.442: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:30.225: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:30.225: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:30.482: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:32.265: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:32.265: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:32.523: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:34.305: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:34.305: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:34.562: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:36.344: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:36.345: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:36.602: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:38.384: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:38.384: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:38.642: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:40.424: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:40.424: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:40.682: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:42.464: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:42.464: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:42.722: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:58.491: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:58.491: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:58.492: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:18.892: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:18.892: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:18.893: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:39.292: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:39.292: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:39.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 6m52.898s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m0s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m12.9s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m20.002s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m32.901s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m40.004s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:26.213: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:26.214: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:26.214: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:34.333: INFO: Node bootstrap-e2e-minion-group-w9vk didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:34.373: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:34.373: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:36.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:36.413: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:38.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:38.453: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:40.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:40.493: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:42.532: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:42.532: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m52.903s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 6m0.005s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:44.572: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:44.572: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:46.572: INFO: Node bootstrap-e2e-minion-group-w6qn didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-9nd1 didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-9nd1 failed reboot test. Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-w6qn failed reboot test. Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-w9vk failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:19:46.574 < Exit [It] each node by switching off the network interface and ensure they function upon switch on - test/e2e/cloud/gcp/reboot.go:115 @ 01/30/23 02:19:46.574 (6m3.899s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:19:46.574 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:19:46.574 Jan 30 02:19:46.613: INFO: Unexpected error: <*url.Error | 0xc003670bd0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0044c2280>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0057d98f0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00016dac0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:19:46.613 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:19:46.613 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:19:46.613 Jan 30 02:19:46.613: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:19:46.653 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:19:46.653 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:19:46.653 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:19:46.653 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:19:46.653 STEP: Collecting events from namespace "reboot-6557". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:19:46.653 Jan 30 02:19:46.693: INFO: Unexpected error: failed to list events in namespace "reboot-6557": <*url.Error | 0xc003671140>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-6557/events", Err: <*net.OpError | 0xc0044c3090>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0034792c0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00016dee0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:19:46.693 (40ms) [FAILED] failed to list events in namespace "reboot-6557": Get "https://34.168.242.120/api/v1/namespaces/reboot-6557/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:19:46.693 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:19:46.693 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:19:46.693 STEP: Destroying namespace "reboot-6557" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:19:46.693 [FAILED] Couldn't delete ns: "reboot-6557": Delete "https://34.168.242.120/api/v1/namespaces/reboot-6557": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-6557", Err:(*net.OpError)(0xc00491d3b0)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:19:46.733 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:19:46.733 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:19:46.733 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:19:46.733 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sswitching\soff\sthe\snetwork\sinterface\sand\sensure\sthey\sfunction\supon\sswitch\son$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:19:46.574 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:49.777 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:11:49.777 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:11:49.777 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:11:49.777 Jan 30 02:11:49.777: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:11:49.778 Jan 30 02:11:49.817: INFO: Unexpected error while creating namespace: Post "https://34.168.242.120/api/v1/namespaces": dial tcp 34.168.242.120:443: connect: connection refused STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 02:13:42.513 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 02:13:42.594 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:13:42.674 (1m52.897s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:13:42.674 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:13:42.674 (0s) > Enter [It] each node by switching off the network interface and ensure they function upon switch on - test/e2e/cloud/gcp/reboot.go:115 @ 01/30/23 02:13:42.674 Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-w9vk Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-9nd1 Jan 30 02:13:42.859: INFO: Getting bootstrap-e2e-minion-group-w6qn Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:13:42.942: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:13:42.990: INFO: Node bootstrap-e2e-minion-group-w9vk has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Node bootstrap-e2e-minion-group-9nd1 has 4 assigned pods with no liveness probes: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.990: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.991: INFO: Node bootstrap-e2e-minion-group-w6qn has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:42.991: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:13:43.052: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 62.737814ms Jan 30 02:13:43.052: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.052: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 62.538108ms Jan 30 02:13:43.052: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.053: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 62.500488ms Jan 30 02:13:43.053: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.053: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w9vk metadata-proxy-v0.1-z4wwh] Jan 30 02:13:43.053: INFO: Getting external IP address for bootstrap-e2e-minion-group-w9vk Jan 30 02:13:43.053: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w9vk(104.198.6.37:22) Jan 30 02:13:43.061: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=true. Elapsed: 70.557007ms Jan 30 02:13:43.061: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.061: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 70.749625ms Jan 30 02:13:43.061: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 70.519251ms Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.061: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 70.490744ms Jan 30 02:13:43.061: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 71.16232ms Jan 30 02:13:43.061: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: stdout: "" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: stderr: "" Jan 30 02:13:43.595: INFO: ssh prow@104.198.6.37:22: exit code: 0 Jan 30 02:13:43.595: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be false Jan 30 02:13:43.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:45.107: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.116441173s Jan 30 02:13:45.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 2.115963082s Jan 30 02:13:45.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:45.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:45.684: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:47.107: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.116811317s Jan 30 02:13:47.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 4.116320542s Jan 30 02:13:47.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:47.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:47.728: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:49.104: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.11345029s Jan 30 02:13:49.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:49.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 6.114197396s Jan 30 02:13:49.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:49.770: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:51.103: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.113180079s Jan 30 02:13:51.103: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:51.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 8.114085717s Jan 30 02:13:51.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:51.814: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:53.104: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.113868864s Jan 30 02:13:53.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:12:30 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:13:53.105: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 10.114674354s Jan 30 02:13:53.105: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:53.857: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:55.106: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 12.11605325s Jan 30 02:13:55.106: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:13:55.106: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-27p25 volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1] Jan 30 02:13:55.106: INFO: Getting external IP address for bootstrap-e2e-minion-group-9nd1 Jan 30 02:13:55.106: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-9nd1(35.247.49.149:22) Jan 30 02:13:55.107: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 12.116135733s Jan 30 02:13:55.107: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: stdout: "" Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: stderr: "" Jan 30 02:13:55.647: INFO: ssh prow@35.247.49.149:22: exit code: 0 Jan 30 02:13:55.647: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be false Jan 30 02:13:55.689: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:55.900: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:57.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 14.113256532s Jan 30 02:13:57.104: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:13:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:13:57.732: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:57.943: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 16.113211701s Jan 30 02:13:59.104: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:13:59.104: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:13:59.104: INFO: Getting external IP address for bootstrap-e2e-minion-group-w6qn Jan 30 02:13:59.104: INFO: SSH "nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w6qn(34.105.21.11:22) Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: command: nohup sh -c 'sleep 10; echo Shutting down eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 down | sudo tee /dev/kmsg; sleep 120; echo Starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; sleep 10; echo Retrying starting up eth0 | sudo tee /dev/kmsg; sudo ip link set eth0 up | sudo tee /dev/kmsg; echo Running dhclient | sudo tee /dev/kmsg; sudo dhclient | sudo tee /dev/kmsg; echo Starting systemd-networkd | sudo tee /dev/kmsg; sudo systemctl restart systemd-networkd | sudo tee /dev/kmsg' >/dev/null 2>&1 & Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: stdout: "" Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: stderr: "" Jan 30 02:13:59.663: INFO: ssh prow@34.105.21.11:22: exit code: 0 Jan 30 02:13:59.663: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be false Jan 30 02:13:59.705: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.775: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:13:59.985: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:01.748: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:01.818: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:02.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:03.791: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:03.861: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:04.072: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:05.834: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:05.912: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:06.115: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:07.877: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:07.956: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:08.158: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:09.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:09.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:10.201: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:11.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:12.042: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:12.244: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.007: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.085: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:14.288: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.049: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.128: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:16.330: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:18.381: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.135: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:20.425: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.255: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:22.468: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.293: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.298: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:24.511: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.336: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.341: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:26.562: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.378: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.383: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:28.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.421: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.426: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:30.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.463: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.474: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:32.754: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:14:32.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:34.506: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:34.517: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:34.879: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:36.548: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:36.562: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:36.922: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:38.613: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:38.623: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:38.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:40.656: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:40.665: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:41.007: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:42.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:42.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:14:43.070: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:44.767: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:14:44.767: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:14:44.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:44.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:45.111: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:46.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:46.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:47.155: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:48.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:48.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:49.198: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:50.942: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:50.942: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:51.240: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:52.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:52.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:53.283: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:55.030: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:55.030: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:55.326: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:57.076: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:57.076: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:57.369: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:14:59.119: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:59.119: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:14:59.412: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:01.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:01.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:01.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:03.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:03.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:03.497: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:05.251: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:05.251: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:05.539: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:07.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:07.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:07.582: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:09.338: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:09.338: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:09.625: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:11.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:11.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:11.668: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:13.427: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:13.427: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:13.710: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:15.471: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:15.471: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:15.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:17.515: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:17.515: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:17.796: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:19.558: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:19.558: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:19.839: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:21.602: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:21.602: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:21.882: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:23.653: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:23.653: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:23.926: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:25.696: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:25.696: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:25.969: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:27.741: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:27.741: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:28.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:29.784: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:29.784: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:30.057: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:31.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:31.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:32.100: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:33.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:33.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:34.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:35.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:35.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:36.196: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:37.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:37.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:38.238: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:40.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:40.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:40.284: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:42.067: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:42.067: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:42.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:44.113: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:44.113: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:15:44.384: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:14:32 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:14:37 +0000 UTC}]. Failure Jan 30 02:15:46.156: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:46.156: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:46.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:48.200: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:48.200: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:48.470: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:50.243: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:50.243: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:50.512: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:52.284: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:52.284: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:52.555: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:54.336: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:54.336: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:54.599: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:56.376: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:56.376: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:56.639: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:15:58.416: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:15:58.416: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:15:58.680: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:00.457: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:00.457: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:00.720: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:02.497: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:02.497: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:02.760: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:04.536: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:04.536: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:04.800: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:06.577: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:06.577: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:06.840: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:08.618: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:08.618: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:08.880: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:10.659: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:10.659: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:10.920: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:12.700: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:12.700: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:12.960: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:14.740: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:14.740: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:15.000: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:16.780: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:16.780: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:17.041: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:18.819: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:18.819: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:19.081: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:20.859: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:20.859: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:21.121: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:22.899: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:22.899: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:23.161: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:24.939: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:24.939: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:25.201: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:26.980: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:26.980: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:27.241: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:29.021: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:29.021: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:29.281: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:31.062: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:31.062: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:31.321: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:33.101: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:33.101: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:33.361: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:35.141: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:35.141: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:35.401: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:37.180: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:37.180: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:37.441: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:39.221: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:39.221: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:39.481: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:41.261: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:41.261: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:41.521: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:43.301: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:43.301: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:43.561: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:45.341: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:45.341: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:45.602: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:47.380: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:47.381: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:47.641: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:49.421: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:49.421: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:49.682: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:51.460: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:51.460: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:51.721: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:53.501: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:53.501: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:53.762: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:55.541: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:55.541: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:55.801: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:57.581: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:57.581: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:57.841: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:16:59.621: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:16:59.621: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:16:59.881: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:01.662: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:01.662: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:01.921: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:03.702: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:03.702: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:03.961: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:05.745: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:05.745: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:06.001: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:07.785: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:07.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:08.041: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:09.825: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:09.825: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:10.081: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:11.865: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:11.865: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:12.121: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:13.905: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:13.905: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:14.161: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:15.945: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:15.946: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:16.201: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:17.985: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:17.985: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:18.241: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:20.025: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:20.025: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:20.282: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:22.065: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:22.065: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:22.322: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:24.106: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:24.106: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:24.363: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:26.146: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:26.146: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:26.403: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:28.186: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:28.186: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:28.442: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:30.225: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:30.225: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:30.482: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:32.265: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:32.265: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:32.523: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:34.305: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:34.305: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:34.562: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:36.344: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:36.345: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:36.602: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:38.384: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:38.384: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:38.642: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:40.424: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:40.424: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:40.682: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:42.464: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:42.464: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:42.722: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:50.329: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:52.369: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:54.410: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:17:56.450: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:58.491: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:17:58.491: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:17:58.492: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:00.531: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:02.571: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:04.612: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:06.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:08.692: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:10.733: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:12.773: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:14.813: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:16.853: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:18.892: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:18.892: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:18.893: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:20.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:22.972: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:25.012: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:27.053: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:29.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:31.133: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:33.173: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:35.213: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:37.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:39.292: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:39.292: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:39.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:41.333: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 6m52.898s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m0s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:43.372: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:45.413: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:47.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:49.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:51.534: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:53.574: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:55.614: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:57.653: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:18:59.694: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:01.735: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m12.9s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m20.002s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:03.774: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:05.814: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:07.854: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:09.894: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:11.933: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:13.973: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:16.014: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:18.054: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:20.094: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:22.134: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m32.901s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 5m40.004s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4198 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174720, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174720, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:24.174: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:26.213: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:26.214: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:26.214: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:28.253: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:30.293: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:19:32.333: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:34.333: INFO: Node bootstrap-e2e-minion-group-w9vk didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:34.373: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:34.373: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:36.413: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:36.413: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:38.453: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:38.453: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:40.493: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:40.493: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:42.532: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:42.532: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on (Spec Runtime: 7m52.903s) test/e2e/cloud/gcp/reboot.go:115 In [It] (Node Runtime: 6m0.005s) test/e2e/cloud/gcp/reboot.go:115 Spec Goroutine goroutine 4194 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc0004a08b8?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f70a45dc2a8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f70a45dc2a8?, 0xc00115e780}, {0x8147128?, 0xc002868000}, {0x7903e7c, 0x21e}, 0x0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.6({0x7f70a45dc2a8?, 0xc00115e780?}) test/e2e/cloud/gcp/reboot.go:133 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00115e780}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 4197 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc001174460, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc001174460, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x1) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 goroutine 4196 [sleep] time.Sleep(0x77359400) /usr/local/go/src/runtime/time.go:195 k8s.io/kubernetes/test/e2e/framework/node.WaitConditionToBe({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0xc0011741a0, 0x1f}, {0x76bb977, 0x5}, 0x1, 0x45d964b800) test/e2e/framework/node/wait.go:119 k8s.io/kubernetes/test/e2e/framework/node.WaitForNodeToBeReady(...) test/e2e/framework/node/wait.go:143 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f70a45dc2a8, 0xc00115e780}, {0x8147128, 0xc002868000}, {0x7ffff1f495f2, 0x3}, {0xc0011741a0, 0x1f}, {0x7903e7c, 0x21e}) test/e2e/cloud/gcp/reboot.go:301 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 02:19:44.572: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:19:44.572: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:19:46.572: INFO: Node bootstrap-e2e-minion-group-w6qn didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-9nd1 didn't reach desired Ready condition status (true) within 5m0s Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-9nd1 failed reboot test. Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-w6qn failed reboot test. Jan 30 02:19:46.573: INFO: Node bootstrap-e2e-minion-group-w9vk failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:19:46.574 < Exit [It] each node by switching off the network interface and ensure they function upon switch on - test/e2e/cloud/gcp/reboot.go:115 @ 01/30/23 02:19:46.574 (6m3.899s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:19:46.574 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:19:46.574 Jan 30 02:19:46.613: INFO: Unexpected error: <*url.Error | 0xc003670bd0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0044c2280>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0057d98f0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00016dac0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:19:46.613 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:19:46.613 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:19:46.613 Jan 30 02:19:46.613: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:19:46.653 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:19:46.653 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:19:46.653 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:19:46.653 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:19:46.653 STEP: Collecting events from namespace "reboot-6557". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:19:46.653 Jan 30 02:19:46.693: INFO: Unexpected error: failed to list events in namespace "reboot-6557": <*url.Error | 0xc003671140>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-6557/events", Err: <*net.OpError | 0xc0044c3090>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0034792c0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00016dee0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:19:46.693 (40ms) [FAILED] failed to list events in namespace "reboot-6557": Get "https://34.168.242.120/api/v1/namespaces/reboot-6557/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:19:46.693 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:19:46.693 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:19:46.693 STEP: Destroying namespace "reboot-6557" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:19:46.693 [FAILED] Couldn't delete ns: "reboot-6557": Delete "https://34.168.242.120/api/v1/namespaces/reboot-6557": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-6557", Err:(*net.OpError)(0xc00491d3b0)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:19:46.733 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:19:46.733 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:19:46.733 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:19:46.733 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\striggering\skernel\spanic\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:10:49.113 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:08:01.824 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:08:01.824 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:08:01.824 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:08:01.824 Jan 30 02:08:01.824: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:08:01.827 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 02:08:01.976 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 02:08:02.057 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:08:02.14 (316ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:08:02.14 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:08:02.142 (2ms) > Enter [It] each node by triggering kernel panic and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:109 @ 01/30/23 02:08:02.142 Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-w9vk Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-w6qn Jan 30 02:08:02.341: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:08:02.343: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:08:02.343: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:08:02.383: INFO: Node bootstrap-e2e-minion-group-9nd1 has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Node bootstrap-e2e-minion-group-w6qn has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Node bootstrap-e2e-minion-group-w9vk has 2 assigned pods with no liveness probes: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.425: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 42.483776ms Jan 30 02:08:02.425: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.429: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=true. Elapsed: 45.997672ms Jan 30 02:08:02.429: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 47.731579ms Jan 30 02:08:02.431: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 47.699815ms Jan 30 02:08:02.431: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.431: INFO: Getting external IP address for bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:02.431: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-9nd1(35.247.49.149:22) Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 46.397364ms Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 46.500578ms Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.433: INFO: Getting external IP address for bootstrap-e2e-minion-group-w6qn Jan 30 02:08:02.433: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w6qn(34.105.21.11:22) Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 46.099069ms Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 46.235461ms Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.433: INFO: Getting external IP address for bootstrap-e2e-minion-group-w9vk Jan 30 02:08:02.433: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w9vk(104.198.6.37:22) Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: stdout: "" Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: stderr: "" Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: exit code: 0 Jan 30 02:08:02.964: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be false Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: stdout: "" Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: stderr: "" Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: exit code: 0 Jan 30 02:08:02.967: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be false Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: stdout: "" Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: stderr: "" Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: exit code: 0 Jan 30 02:08:02.975: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be false Jan 30 02:08:03.008: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:03.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:03.019: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.052: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.054: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.063: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.106: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.141: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.191: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.228: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.233: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.276: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.319: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.365: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.365: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.366: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.411: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.411: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.412: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.502: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.502: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.503: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.963: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.008: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:50.050: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:50.054: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:08:50.054: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:08:50.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:50.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:52.096: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:52.141: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:52.142: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.140: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:08:54.181: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:08:56.223: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:56.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:08:56.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:58.263: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:58.268: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:08:58.268: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:00.304: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:00.308: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:00.308: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:02.343: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:02.348: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:02.348: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:04.385: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:04.388: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:04.388: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:06.424: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:06.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:06.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:08.464: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:08.467: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:08.467: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:10.505: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:10.507: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:10.507: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:12.545: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:12.546: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:12.546: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:14.584: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:14.587: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:14.587: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:16.624: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:16.626: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:16.626: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:18.664: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:18.666: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:18.666: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:20.704: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:20.706: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:20.706: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:22.744: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:22.746: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:22.746: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:26.824: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:26.824: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:26.825: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:35.613: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:35.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:35.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:37.656: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:37.719: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:37.720: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:41.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:41.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:41.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:43.787: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:43.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:43.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:45.830: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:45.906: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:45.906: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:49.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:49.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:49.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:51.961: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:54.004: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:54.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:54.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:56.047: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:56.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:56.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:00.136: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:00.236: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:00.236: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:02.179: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:02.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:02.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:04.222: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:04.327: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:04.327: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.265: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.370: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.372: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:08.307: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:08.413: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:08.415: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:10.350: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:10.459: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:10.459: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.505: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.506: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:14.437: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:14.553: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:14.553: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:16.481: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:16.597: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:16.597: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.524: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:20.576: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:20.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:20.692: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:22.619: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:22.739: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:22.739: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:24.758: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:24.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:24.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:26.801: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:26.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:26.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.954: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=false. Elapsed: 62.747731ms Jan 30 02:10:28.954: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-z4wwh' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.954: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=false. Elapsed: 63.711909ms Jan 30 02:10:28.954: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w9vk' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC }] Jan 30 02:10:28.992: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 51.717019ms Jan 30 02:10:28.992: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:28.992: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 51.743361ms Jan 30 02:10:28.992: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 53.233648ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 53.300733ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:59 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=false. Elapsed: 53.516973ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-6rwwg' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 53.963354ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:30.997: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=false. Elapsed: 2.10663645s Jan 30 02:10:30.997: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-z4wwh' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:30.997: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=false. Elapsed: 2.1069088s Jan 30 02:10:30.998: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w9vk' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC }] Jan 30 02:10:31.034: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.094225883s Jan 30 02:10:31.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:31.036: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 2.096007367s Jan 30 02:10:31.036: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 2.100850196s Jan 30 02:10:31.041: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 2.101096703s Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:10:31.041: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 2.10118876s Jan 30 02:10:31.041: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:31.042: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 2.10117946s Jan 30 02:10:31.042: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:10:31.042: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:10:31.042: INFO: Reboot successful on node bootstrap-e2e-minion-group-w6qn Jan 30 02:10:32.998: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 4.107400007s Jan 30 02:10:32.998: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:10:32.998: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 4.107305641s Jan 30 02:10:32.998: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:10:32.998: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:10:32.998: INFO: Reboot successful on node bootstrap-e2e-minion-group-w9vk Jan 30 02:10:33.038: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 4.097784919s Jan 30 02:10:33.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:33.038: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 4.098025119s Jan 30 02:10:33.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:33.040: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 4.099646157s Jan 30 02:10:33.040: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:33.040: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.099903935s Jan 30 02:10:33.040: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:35.035: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 6.094349168s Jan 30 02:10:35.035: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:35.037: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 6.096698483s Jan 30 02:10:35.037: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:10:35.039: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 6.099010807s Jan 30 02:10:35.039: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:10:35.039: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 6.099012451s Jan 30 02:10:35.039: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:10:37.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 8.093865671s Jan 30 02:10:37.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:39.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 10.093380023s Jan 30 02:10:39.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:41.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 12.093247634s Jan 30 02:10:41.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:43.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 14.105726616s Jan 30 02:10:43.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:45.033: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 16.093111306s Jan 30 02:10:45.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:47.038: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 18.097637679s Jan 30 02:10:47.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:49.032: INFO: Encountered non-retryable error while getting pod kube-system/kube-dns-autoscaler-5f6455f985-lrh8m: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:49.032: INFO: Pod kube-dns-autoscaler-5f6455f985-lrh8m failed to be running and ready, or succeeded. Jan 30 02:10:49.032: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:10:49.032: INFO: Status for not ready pod kube-system/volume-snapshot-controller-0: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.27 PodIPs:[{IP:10.64.1.27}] StartTime:2023-01-30 02:04:56 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=volume-snapshot-controller pod=volume-snapshot-controller-0_kube-system(3ba57879-a20b-4a41-8d2c-47c8dcf19e76),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 02:10:33 +0000 UTC,FinishedAt:2023-01-30 02:10:34 +0000 UTC,ContainerID:containerd://732e547888061e09b6d5b344c44890bb0bdf8e865c9bb6e460faaac22e9b465d,}} Ready:false RestartCount:4 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://732e547888061e09b6d5b344c44890bb0bdf8e865c9bb6e460faaac22e9b465d Started:0xc003b1a17f}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 30 02:10:49.073: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0/log?container=volume-snapshot-controller&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.073: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0/log?container=volume-snapshot-controller&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.073: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-lrh8m: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.30 PodIPs:[{IP:10.64.1.30}] StartTime:2023-01-30 02:04:56 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=autoscaler pod=kube-dns-autoscaler-5f6455f985-lrh8m_kube-system(bca61c97-b009-4c95-9c7c-afa540a19c87),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 02:10:34 +0000 UTC,FinishedAt:2023-01-30 02:10:35 +0000 UTC,ContainerID:containerd://484ab5d6fd25b8ab70a7221f5c928a261e0fcd18f300972e217666fca169be4d,}} Ready:false RestartCount:5 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://484ab5d6fd25b8ab70a7221f5c928a261e0fcd18f300972e217666fca169be4d Started:0xc0037f65af}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 02:10:49.113: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-lrh8m/autoscaler, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m/log?container=autoscaler&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.113: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-lrh8m/autoscaler, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m/log?container=autoscaler&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.113: INFO: Node bootstrap-e2e-minion-group-9nd1 failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:10:49.113 < Exit [It] each node by triggering kernel panic and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:109 @ 01/30/23 02:10:49.113 (2m46.971s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:10:49.113 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:10:49.113 Jan 30 02:10:49.153: INFO: Unexpected error: <*url.Error | 0xc000a6b950>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0050aa5a0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001df8ea0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d848e0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:10:49.153 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:10:49.153 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:10:49.153 Jan 30 02:10:49.153: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:10:49.192 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:10:49.192 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:10:49.192 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:10:49.192 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:10:49.192 STEP: Collecting events from namespace "reboot-98". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:10:49.192 Jan 30 02:10:49.231: INFO: Unexpected error: failed to list events in namespace "reboot-98": <*url.Error | 0xc001658ae0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-98/events", Err: <*net.OpError | 0xc001767ef0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001df93e0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc005a9a000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:10:49.232 (40ms) [FAILED] failed to list events in namespace "reboot-98": Get "https://34.168.242.120/api/v1/namespaces/reboot-98/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:10:49.232 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:10:49.232 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:10:49.232 STEP: Destroying namespace "reboot-98" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:10:49.232 [FAILED] Couldn't delete ns: "reboot-98": Delete "https://34.168.242.120/api/v1/namespaces/reboot-98": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-98", Err:(*net.OpError)(0xc0050aab90)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:10:49.272 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:10:49.272 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:10:49.272 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:10:49.272 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\striggering\skernel\spanic\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:10:49.113 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:08:01.824 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 02:08:01.824 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:08:01.824 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 02:08:01.824 Jan 30 02:08:01.824: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 02:08:01.827 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 02:08:01.976 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 02:08:02.057 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 02:08:02.14 (316ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:08:02.14 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 02:08:02.142 (2ms) > Enter [It] each node by triggering kernel panic and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:109 @ 01/30/23 02:08:02.142 Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-w9vk Jan 30 02:08:02.298: INFO: Getting bootstrap-e2e-minion-group-w6qn Jan 30 02:08:02.341: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:08:02.343: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:08:02.343: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:08:02.383: INFO: Node bootstrap-e2e-minion-group-9nd1 has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.383: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Node bootstrap-e2e-minion-group-w6qn has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Node bootstrap-e2e-minion-group-w9vk has 2 assigned pods with no liveness probes: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.387: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:08:02.425: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 42.483776ms Jan 30 02:08:02.425: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.429: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=true. Elapsed: 45.997672ms Jan 30 02:08:02.429: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 47.731579ms Jan 30 02:08:02.431: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 47.699815ms Jan 30 02:08:02.431: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.431: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:08:02.431: INFO: Getting external IP address for bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:02.431: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-9nd1(35.247.49.149:22) Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 46.397364ms Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 46.500578ms Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:08:02.433: INFO: Getting external IP address for bootstrap-e2e-minion-group-w6qn Jan 30 02:08:02.433: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w6qn(34.105.21.11:22) Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 46.099069ms Jan 30 02:08:02.433: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 46.235461ms Jan 30 02:08:02.433: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:08:02.433: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:08:02.433: INFO: Getting external IP address for bootstrap-e2e-minion-group-w9vk Jan 30 02:08:02.433: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-w9vk(104.198.6.37:22) Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: stdout: "" Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: stderr: "" Jan 30 02:08:02.964: INFO: ssh prow@104.198.6.37:22: exit code: 0 Jan 30 02:08:02.964: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be false Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: stdout: "" Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: stderr: "" Jan 30 02:08:02.967: INFO: ssh prow@35.247.49.149:22: exit code: 0 Jan 30 02:08:02.967: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be false Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo c | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: stdout: "" Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: stderr: "" Jan 30 02:08:02.975: INFO: ssh prow@34.105.21.11:22: exit code: 0 Jan 30 02:08:02.975: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be false Jan 30 02:08:03.008: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:03.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:03.019: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.052: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.054: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:05.063: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:07.106: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.141: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:09.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:11.191: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.228: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:13.233: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:15.276: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:17.319: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.365: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.365: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:19.366: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.411: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.411: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:21.412: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:23.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.502: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.502: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:25.503: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:27.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:29.595: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:31.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:33.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:35.737: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:37.782: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:39.828: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:41.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:43.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.963: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:45.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.008: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:48.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:50.050: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:50.054: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w9vk condition Ready to be true Jan 30 02:08:50.054: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-w6qn condition Ready to be true Jan 30 02:08:50.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:50.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:52.096: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 02:08:52.141: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:52.142: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.140: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-9nd1 condition Ready to be true Jan 30 02:08:54.181: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:54.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:08:56.223: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:56.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:08:56.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:08:58.263: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:08:58.268: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:08:58.268: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:00.304: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:00.308: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:00.308: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:02.343: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:02.348: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:02.348: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:04.385: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:04.388: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:04.388: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:06.424: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:06.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:06.428: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:08.464: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:08.467: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:08.467: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:10.505: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:10.507: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:10.507: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:12.545: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:12.546: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:12.546: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:14.584: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:14.587: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:14.587: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:16.624: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:16.626: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:16.626: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:18.664: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:18.666: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:18.666: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:20.704: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:20.706: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:20.706: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:22.744: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:22.746: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:22.746: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:24.785: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:26.824: INFO: Couldn't get node bootstrap-e2e-minion-group-9nd1 Jan 30 02:09:26.824: INFO: Couldn't get node bootstrap-e2e-minion-group-w9vk Jan 30 02:09:26.825: INFO: Couldn't get node bootstrap-e2e-minion-group-w6qn Jan 30 02:09:35.613: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:35.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:35.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:37.656: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:37.719: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:37.720: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:39.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:41.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:41.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:41.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:43.787: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:43.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:43.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:45.830: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:45.906: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:45.906: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:47.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:49.918: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:49.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:49.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:51.961: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:54.004: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:54.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:54.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:56.047: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:56.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:09:56.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:09:58.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:00.136: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:00.236: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:00.236: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:02.179: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:02.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:02.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:04.222: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:04.327: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:04.327: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.265: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.370: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:06.372: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:08.307: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:08.413: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:08.415: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:10.350: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:10.459: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:10.459: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.505: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:12.506: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:14.437: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:14.553: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:14.553: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:16.481: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:16.597: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:16.597: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.524: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:18.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:20.576: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:20.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:20.692: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:22.619: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:22.739: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:22.739: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:24.758: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:24.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:24.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:26.801: INFO: Condition Ready of node bootstrap-e2e-minion-group-w9vk is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:26.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-w6qn is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 02:08:48 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 02:08:53 +0000 UTC}]. Failure Jan 30 02:10:26.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-9nd1 is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.891: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-z4wwh" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-6rwwg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-27p25" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-lrh8m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.940: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 02:10:28.954: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=false. Elapsed: 62.747731ms Jan 30 02:10:28.954: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-z4wwh' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.954: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=false. Elapsed: 63.711909ms Jan 30 02:10:28.954: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w9vk' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC }] Jan 30 02:10:28.992: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 51.717019ms Jan 30 02:10:28.992: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:28.992: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 51.743361ms Jan 30 02:10:28.992: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 53.233648ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=false. Elapsed: 53.300733ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w6qn' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:59 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=false. Elapsed: 53.516973ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-6rwwg' on 'bootstrap-e2e-minion-group-w6qn' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:28.994: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 53.963354ms Jan 30 02:10:28.994: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:30.997: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=false. Elapsed: 2.10663645s Jan 30 02:10:30.997: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-z4wwh' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:51 +0000 UTC }] Jan 30 02:10:30.997: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=false. Elapsed: 2.1069088s Jan 30 02:10:30.998: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-w9vk' on 'bootstrap-e2e-minion-group-w9vk' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC }] Jan 30 02:10:31.034: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.094225883s Jan 30 02:10:31.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:31.036: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 2.096007367s Jan 30 02:10:31.036: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:07:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 2.100850196s Jan 30 02:10:31.041: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-6rwwg": Phase="Running", Reason="", readiness=true. Elapsed: 2.101096703s Jan 30 02:10:31.041: INFO: Pod "metadata-proxy-v0.1-6rwwg" satisfied condition "running and ready, or succeeded" Jan 30 02:10:31.041: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 2.10118876s Jan 30 02:10:31.041: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:31.042: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn": Phase="Running", Reason="", readiness=true. Elapsed: 2.10117946s Jan 30 02:10:31.042: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w6qn" satisfied condition "running and ready, or succeeded" Jan 30 02:10:31.042: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-w6qn metadata-proxy-v0.1-6rwwg] Jan 30 02:10:31.042: INFO: Reboot successful on node bootstrap-e2e-minion-group-w6qn Jan 30 02:10:32.998: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk": Phase="Running", Reason="", readiness=true. Elapsed: 4.107400007s Jan 30 02:10:32.998: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-w9vk" satisfied condition "running and ready, or succeeded" Jan 30 02:10:32.998: INFO: Pod "metadata-proxy-v0.1-z4wwh": Phase="Running", Reason="", readiness=true. Elapsed: 4.107305641s Jan 30 02:10:32.998: INFO: Pod "metadata-proxy-v0.1-z4wwh" satisfied condition "running and ready, or succeeded" Jan 30 02:10:32.998: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-z4wwh kube-proxy-bootstrap-e2e-minion-group-w9vk] Jan 30 02:10:32.998: INFO: Reboot successful on node bootstrap-e2e-minion-group-w9vk Jan 30 02:10:33.038: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 4.097784919s Jan 30 02:10:33.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:33.038: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=false. Elapsed: 4.098025119s Jan 30 02:10:33.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-9nd1' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:06:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:33.040: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=false. Elapsed: 4.099646157s Jan 30 02:10:33.040: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-27p25' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:48 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:47 +0000 UTC }] Jan 30 02:10:33.040: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.099903935s Jan 30 02:10:33.040: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:35.035: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 6.094349168s Jan 30 02:10:35.035: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:08:53 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:29 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:35.037: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 6.096698483s Jan 30 02:10:35.037: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 02:10:35.039: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1": Phase="Running", Reason="", readiness=true. Elapsed: 6.099010807s Jan 30 02:10:35.039: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-9nd1" satisfied condition "running and ready, or succeeded" Jan 30 02:10:35.039: INFO: Pod "metadata-proxy-v0.1-27p25": Phase="Running", Reason="", readiness=true. Elapsed: 6.099012451s Jan 30 02:10:35.039: INFO: Pod "metadata-proxy-v0.1-27p25" satisfied condition "running and ready, or succeeded" Jan 30 02:10:37.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 8.093865671s Jan 30 02:10:37.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:39.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 10.093380023s Jan 30 02:10:39.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:41.034: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 12.093247634s Jan 30 02:10:41.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:43.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 14.105726616s Jan 30 02:10:43.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:45.033: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 16.093111306s Jan 30 02:10:45.034: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:47.038: INFO: Pod "kube-dns-autoscaler-5f6455f985-lrh8m": Phase="Running", Reason="", readiness=false. Elapsed: 18.097637679s Jan 30 02:10:47.038: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-lrh8m' on 'bootstrap-e2e-minion-group-9nd1' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:10:36 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 02:04:56 +0000 UTC }] Jan 30 02:10:49.032: INFO: Encountered non-retryable error while getting pod kube-system/kube-dns-autoscaler-5f6455f985-lrh8m: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m": dial tcp 34.168.242.120:443: connect: connection refused Jan 30 02:10:49.032: INFO: Pod kube-dns-autoscaler-5f6455f985-lrh8m failed to be running and ready, or succeeded. Jan 30 02:10:49.032: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-lrh8m kube-proxy-bootstrap-e2e-minion-group-9nd1 metadata-proxy-v0.1-27p25 volume-snapshot-controller-0] Jan 30 02:10:49.032: INFO: Status for not ready pod kube-system/volume-snapshot-controller-0: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.27 PodIPs:[{IP:10.64.1.27}] StartTime:2023-01-30 02:04:56 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=volume-snapshot-controller pod=volume-snapshot-controller-0_kube-system(3ba57879-a20b-4a41-8d2c-47c8dcf19e76),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 02:10:33 +0000 UTC,FinishedAt:2023-01-30 02:10:34 +0000 UTC,ContainerID:containerd://732e547888061e09b6d5b344c44890bb0bdf8e865c9bb6e460faaac22e9b465d,}} Ready:false RestartCount:4 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://732e547888061e09b6d5b344c44890bb0bdf8e865c9bb6e460faaac22e9b465d Started:0xc003b1a17f}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 30 02:10:49.073: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0/log?container=volume-snapshot-controller&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.073: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0/log?container=volume-snapshot-controller&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.073: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-lrh8m: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:10:36 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 02:04:56 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.30 PodIPs:[{IP:10.64.1.30}] StartTime:2023-01-30 02:04:56 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 10s restarting failed container=autoscaler pod=kube-dns-autoscaler-5f6455f985-lrh8m_kube-system(bca61c97-b009-4c95-9c7c-afa540a19c87),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 02:10:34 +0000 UTC,FinishedAt:2023-01-30 02:10:35 +0000 UTC,ContainerID:containerd://484ab5d6fd25b8ab70a7221f5c928a261e0fcd18f300972e217666fca169be4d,}} Ready:false RestartCount:5 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://484ab5d6fd25b8ab70a7221f5c928a261e0fcd18f300972e217666fca169be4d Started:0xc0037f65af}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 02:10:49.113: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-lrh8m/autoscaler, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m/log?container=autoscaler&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.113: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-lrh8m/autoscaler, err: Get "https://34.168.242.120/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-lrh8m/log?container=autoscaler&previous=false": dial tcp 34.168.242.120:443: connect: connection refused: Jan 30 02:10:49.113: INFO: Node bootstrap-e2e-minion-group-9nd1 failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 02:10:49.113 < Exit [It] each node by triggering kernel panic and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:109 @ 01/30/23 02:10:49.113 (2m46.971s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:10:49.113 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 02:10:49.113 Jan 30 02:10:49.153: INFO: Unexpected error: <*url.Error | 0xc000a6b950>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0050aa5a0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001df8ea0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc004d848e0>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.168.242.120/api/v1/namespaces/kube-system/events": dial tcp 34.168.242.120:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 02:10:49.153 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 02:10:49.153 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:10:49.153 Jan 30 02:10:49.153: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 02:10:49.192 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:10:49.192 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 02:10:49.192 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:10:49.192 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:10:49.192 STEP: Collecting events from namespace "reboot-98". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 02:10:49.192 Jan 30 02:10:49.231: INFO: Unexpected error: failed to list events in namespace "reboot-98": <*url.Error | 0xc001658ae0>: { Op: "Get", URL: "https://34.168.242.120/api/v1/namespaces/reboot-98/events", Err: <*net.OpError | 0xc001767ef0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001df93e0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 168, 242, 120], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc005a9a000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 02:10:49.232 (40ms) [FAILED] failed to list events in namespace "reboot-98": Get "https://34.168.242.120/api/v1/namespaces/reboot-98/events": dial tcp 34.168.242.120:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 02:10:49.232 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 02:10:49.232 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:10:49.232 STEP: Destroying namespace "reboot-98" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 02:10:49.232 [FAILED] Couldn't delete ns: "reboot-98": Delete "https://34.168.242.120/api/v1/namespaces/reboot-98": dial tcp 34.168.242.120:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.168.242.120/api/v1/namespaces/reboot-98", Err:(*net.OpError)(0xc0050aab90)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 02:10:49.272 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 02:10:49.272 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:10:49.272 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 02:10:49.272 (0s)
Filter through log files
error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Feature:Reboot\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
from junit_runner.xml
Filter through log files
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e JUnit report
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedBeforeSuite]
Kubernetes e2e suite [SynchronizedBeforeSuite]
kubetest Check APIReachability
kubetest Deferred TearDown
kubetest DumpClusterLogs
kubetest Extract
kubetest GetDeployer
kubetest IsUp
kubetest Prepare
kubetest TearDown
kubetest TearDown Previous
kubetest Timeout
kubetest Up
kubetest diffResources
kubetest kubectl version
kubetest list nodes
kubetest listResources After
kubetest listResources Before
kubetest listResources Down
kubetest listResources Up
kubetest test setup
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can be classified by adding FlowSchema and PriorityLevelConfiguration
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can be classified by adding FlowSchema and PriorityLevelConfiguration
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (fairness)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (fairness)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (priority)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (priority)
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should include webhook resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should include webhook resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert a non homogeneous list of CRs [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert a non homogeneous list of CRs [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Flaky] kubectl explain works for CR with the same resource name as built-in object.
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Flaky] kubectl explain works for CR with the same resource name as built-in object.
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] updates the published spec when one version gets renamed [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] updates the published spec when one version gets renamed [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields at the schema root [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields at the schema root [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of different groups [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of different groups [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST NOT fail validation for create of a custom resource that satisfies the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST NOT fail validation for create of a custom resource that satisfies the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains a x-kubernetes-validations rule that refers to a property that do not exist
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains a x-kubernetes-validations rule that refers to a property that do not exist
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that contains a syntax error
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that contains a syntax error
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that exceeds the estimated cost limit
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that exceeds the estimated cost limit
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource that exceeds the runtime cost limit for x-kubernetes-validations rule execution
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource that exceeds the runtime cost limit for x-kubernetes-validations rule execution
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail update of a custom resource that does not satisfy a x-kubernetes-validations transition rule
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail update of a custom resource that does not satisfy a x-kubernetes-validations transition rule
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail validation for create of a custom resource that does not satisfy the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail validation for create of a custom resource that does not satisfy the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] Discovery Custom resource should have storage version hash
Kubernetes e2e suite [It] [sig-api-machinery] Discovery Custom resource should have storage version hash
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should accurately determine present and missing resources
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should accurately determine present and missing resources
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from SIGKILL
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from SIGKILL
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from network partition with master
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from network partition with master
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply an invalid CR with extra properties for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply an invalid CR with extra properties for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect duplicates in a CR when preserving unknown fields
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect duplicates in a CR when preserving unknown fields
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown and duplicate fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown and duplicate fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete jobs and pods created by cronjob
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete jobs and pods created by cronjob
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan RS created by deployment when deleteOptions.PropagationPolicy is Orphan [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan RS created by deployment when deleteOptions.PropagationPolicy is Orphan [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if deleteOptions.OrphanDependents is nil
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if deleteOptions.OrphanDependents is nil
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support cascading deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support cascading deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support orphan deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support orphan deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create pods, set the deletionTimestamp and deletionGracePeriodSeconds of the pod
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create pods, set the deletionTimestamp and deletionGracePeriodSeconds of the pod
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create v1 cronJobs, delete cronJobs, watch cronJobs
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create v1 cronJobs, delete cronJobs, watch cronJobs
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should always delete fast (ALL of 100 namespaces in 150 seconds) [Feature:ComprehensiveNamespaceDraining]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should always delete fast (ALL of 100 namespaces in 150 seconds) [Feature:ComprehensiveNamespaceDraining]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply a finalizer to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply a finalizer to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply an update to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply an update to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply changes to a namespace status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply changes to a namespace status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds)
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds)
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's multiple priority class scope (quota set to pod count: 2) against 2 pods with same priority classes.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's multiple priority class scope (quota set to pod count: 2) against 2 pods with same priority classes.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (cpu, memory quota set) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (cpu, memory quota set) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with different priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with different priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpExists).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpExists).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpNotIn).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpNotIn).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with best effort scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with best effort scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with terminating scopes through scope selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with terminating scopes through scope selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should apply changes to a resourcequota status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should apply changes to a resourcequota status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a custom resource.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a custom resource.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim with a storage class
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim with a storage class
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replica set. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replica set. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a secret. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a secret. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a service. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a service. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should manage the lifecycle of a ResourceQuota [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should manage the lifecycle of a ResourceQuota [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout default timeout should be used if the specified timeout in the request URL is 0s
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout default timeout should be used if the specified timeout in the request URL is 0s
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout should return HTTP status code 400 if the user specifies an invalid timeout in the request URL
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout should return HTTP status code 400 if the user specifies an invalid timeout in the request URL
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout the request should be served with a default timeout if the specified timeout in the request URL exceeds maximum allowed
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout the request should be served with a default timeout if the specified timeout in the request URL exceeds maximum allowed
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should create an applied object if it does not already exist
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should create an applied object if it does not already exist
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should give up ownership of a field if forced applied by a controller
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should give up ownership of a field if forced applied by a controller
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should ignore conflict errors if force apply is used
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should ignore conflict errors if force apply is used
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should not remove a field if an owner unsets the field but other managers still have ownership of the field
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should not remove a field if an owner unsets the field but other managers still have ownership of the field
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should remove a field if it is owned but removed in the apply request
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should remove a field if it is owned but removed in the apply request
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for CRDs
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for CRDs
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for subresources
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for subresources
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should return chunks of results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should return chunks of results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should support continue listing from the last key if the original version has been compacted away, though the list is inconsistent [Slow]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should support continue listing from the last key if the original version has been compacted away, though the list is inconsistent [Slow]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return a 406 for a backend which does not implement metadata [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return a 406 for a backend which does not implement metadata [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return chunks of table results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return chunks of table results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return pod details
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return pod details
Kubernetes e2e suite [It] [sig-api-machinery] StorageVersion resources [Feature:StorageVersionAPI] storage version with non-existing id should be GC'ed
Kubernetes e2e suite [It] [sig-api-machinery] StorageVersion resources [Feature:StorageVersionAPI] storage version with non-existing id should be GC'ed
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to restart watching from the last resource version observed by the previous watch [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to restart watching from the last resource version observed by the previous watch [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json,application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json,application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf,application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf,application/json"
Kubernetes e2e suite [It] [sig-api-machinery] health handlers should contain necessary checks
Kubernetes e2e suite [It] [sig-api-machinery] health handlers should contain necessary checks
Kubernetes e2e suite [It] [sig-api-machinery] kube-apiserver identity [Feature:APIServerIdentity] kube-apiserver identity should persist after restart [Disruptive]
Kubernetes e2e suite [It] [sig-api-machinery] kube-apiserver identity [Feature:APIServerIdentity] kube-apiserver identity should persist after restart [Disruptive]
Kubernetes e2e suite [It] [sig-api-machinery] server version should find the server version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] server version should find the server version [Conformance]
Kubernetes e2e suite [It] [sig-apps] ControllerRevision [Serial] should manage the lifecycle of a ControllerRevision [Conformance]
Kubernetes e2e suite [It] [sig-apps] ControllerRevision [Serial] should manage the lifecycle of a ControllerRevision [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should be able to schedule after more than 100 missed schedule
Kubernetes e2e suite [It] [sig-apps] CronJob should be able to schedule after more than 100 missed schedule
Kubernetes e2e suite [It] [sig-apps] CronJob should delete failed finished jobs with limit of one job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete failed finished jobs with limit of one job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete successful finished jobs with limit of one successful job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete successful finished jobs with limit of one successful job
Kubernetes e2e suite [It] [sig-apps] CronJob should not emit unexpected warnings
Kubernetes e2e suite [It] [sig-apps] CronJob should not emit unexpected warnings
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule jobs when suspended [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule jobs when suspended [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule new jobs when ForbidConcurrent [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule new jobs when ForbidConcurrent [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should remove from active list jobs that have been deleted
Kubernetes e2e suite [It] [sig-apps] CronJob should remove from active list jobs that have been deleted
Kubernetes e2e suite [It] [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should schedule multiple jobs concurrently [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should schedule multiple jobs concurrently [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support CronJob API operations [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support CronJob API operations [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support timezone
Kubernetes e2e suite [It] [sig-apps] CronJob should support timezone
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should list and delete a collection of DaemonSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should list and delete a collection of DaemonSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon with node affinity
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon with node affinity
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should verify changes to a daemon set status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should verify changes to a daemon set status [Conformance]
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Controller Manager should not create/delete replicas across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Controller Manager should not create/delete replicas across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kube-proxy should recover after being killed accidentally
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kube-proxy should recover after being killed accidentally
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Scheduler should continue assigning pods to nodes across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Scheduler should continue assigning pods to nodes across restart
Kubernetes e2e suite [It] [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment reaping should cascade to its replica sets and pods
Kubernetes e2e suite [It] [sig-apps] Deployment deployment reaping should cascade to its replica sets and pods
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should delete old replica sets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should delete old replica sets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support proportional scaling [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support proportional scaling [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support rollover [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support rollover [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment iterative rollouts should eventually progress
Kubernetes e2e suite [It] [sig-apps] Deployment iterative rollouts should eventually progress
Kubernetes e2e suite [It] [sig-apps] Deployment should not disrupt a cloud load-balancer's connectivity during rollout
Kubernetes e2e suite [It] [sig-apps] Deployment should not disrupt a cloud load-balancer's connectivity during rollout
Kubernetes e2e suite [It] [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should validate Deployment Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should validate Deployment Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment test Deployment ReplicaSet orphaning and adoption regarding controllerRef
Kubernetes e2e suite [It] [sig-apps] Deployment test Deployment ReplicaSet orphaning and adoption regarding controllerRef
Kubernetes e2e suite [It] [sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, absolute => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, absolute => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, replicaSet, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, replicaSet, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: no PDB => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: no PDB => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, absolute => should not allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, absolute => should not allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe that the PodDisruptionBudget status is not updated for unmanaged pods
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe that the PodDisruptionBudget status is not updated for unmanaged pods
Kubernetes e2e suite [It] [sig-apps] DisruptionController should update/patch PodDisruptionBudget status [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should update/patch PodDisruptionBudget status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore DisruptionTarget condition
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore DisruptionTarget condition
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore exit code 137
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore exit code 137
Kubernetes e2e suite [It] [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy on exit code to fail the job early
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy on exit code to fail the job early
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy to not count the failure towards the backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy to not count the failure towards the backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should apply changes to a job status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should apply changes to a job status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should create pods for an Indexed job with completion indexes and specified hostname [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should create pods for an Indexed job with completion indexes and specified hostname [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete pods when suspended
Kubernetes e2e suite [It] [sig-apps] Job should delete pods when suspended
Kubernetes e2e suite [It] [sig-apps] Job should fail to exceed backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should fail to exceed backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should fail when exceeds active deadline
Kubernetes e2e suite [It] [sig-apps] Job should fail when exceeds active deadline
Kubernetes e2e suite [It] [sig-apps] Job should manage the lifecycle of a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should manage the lifecycle of a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should not create pods when created in suspend state
Kubernetes e2e suite [It] [sig-apps] Job should not create pods when created in suspend state
Kubernetes e2e suite [It] [sig-apps] Job should remove pods when job is deleted
Kubernetes e2e suite [It] [sig-apps] Job should remove pods when job is deleted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are not locally restarted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are not locally restarted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks succeed
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks succeed
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion with CPU requests [Serial]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion with CPU requests [Serial]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should list and delete a collection of ReplicaSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should list and delete a collection of ReplicaSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should surface a failure condition on a common issue like exceeded quota
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should surface a failure condition on a common issue like exceeded quota
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should get and update a ReplicationController scale [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should get and update a ReplicationController scale [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet AvailableReplicas should get updated accordingly when MinReadySeconds is enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet AvailableReplicas should get updated accordingly when MinReadySeconds is enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should adopt matching orphans and release non-matching pods
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should adopt matching orphans and release non-matching pods
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should provide basic identity
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should provide basic identity
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working CockroachDB cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working CockroachDB cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working mysql cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working mysql cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working redis cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working redis cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working zookeeper cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working zookeeper cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet MinReadySeconds should be honored when enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet MinReadySeconds should be honored when enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenDeleted)
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenDeleted)
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenScaled) [Feature:StatefulSetAutoDeletePVC]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenScaled) [Feature:StatefulSetAutoDeletePVC]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a OnScaledown policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a OnScaledown policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a WhenDeleted policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a WhenDeleted policy
Kubernetes e2e suite [It] [sig-apps] TTLAfterFinished job should be deleted once it finishes after TTL seconds
Kubernetes e2e suite [It] [sig-apps] TTLAfterFinished job should be deleted once it finishes after TTL seconds
Kubernetes e2e suite [It] [sig-apps] stateful Upgrade [Feature:StatefulUpgrade] stateful upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-apps] stateful Upgrade [Feature:StatefulUpgrade] stateful upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-architecture] Conformance Tests should have at least two untainted nodes [Conformance]
Kubernetes e2e suite [It] [sig-architecture] Conformance Tests should have at least two untainted nodes [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support building a client with a CSR
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support building a client with a CSR
Kubernetes e2e suite [It] [sig-auth] SelfSubjectReview [Feature:APISelfSubjectReview] should support SelfSubjectReview API operations
Kubernetes e2e suite [It] [sig-auth] SelfSubjectReview [Feature:APISelfSubjectReview] should support SelfSubjectReview API operations
Kubernetes e2e suite [It] [sig-auth] ServiceAccount admission controller migration [Feature:BoundServiceAccountTokenVolume] master upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-auth] ServiceAccount admission controller migration [Feature:BoundServiceAccountTokenVolume] master upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts no secret-based service account token should be auto-generated
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts no secret-based service account token should be auto-generated
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should allow opting out of API token automount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should allow opting out of API token automount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount an API token into pods [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount an API token into pods [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount projected service account token [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount projected service account token [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should run through the lifecycle of a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should run through the lifecycle of a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should support InClusterConfig with token rotation [Slow]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should support InClusterConfig with token rotation [Slow]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should update a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should update a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] SubjectReview should support SubjectReview API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] SubjectReview should support SubjectReview API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet can delegate ServiceAccount tokens to the API server
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet can delegate ServiceAccount tokens to the API server
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet's main port 10250 should reject requests with no credentials
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet's main port 10250 should reject requests with no credentials
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to create another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to create another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to delete another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to delete another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent configmap should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent configmap should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent secret should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent secret should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a secret for a workload the node has access to should succeed
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a secret for a workload the node has access to should succeed
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing configmap should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing configmap should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing secret should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing secret should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] CA ignores unschedulable pods while scheduling schedulable pods [Feature:ClusterAutoscalerScalability6]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] CA ignores unschedulable pods while scheduling schedulable pods [Feature:ClusterAutoscalerScalability6]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down empty nodes [Feature:ClusterAutoscalerScalability3]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down empty nodes [Feature:ClusterAutoscalerScalability3]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down underutilized nodes [Feature:ClusterAutoscalerScalability4]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down underutilized nodes [Feature:ClusterAutoscalerScalability4]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up at all [Feature:ClusterAutoscalerScalability1]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up at all [Feature:ClusterAutoscalerScalability1]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up twice [Feature:ClusterAutoscalerScalability2]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up twice [Feature:ClusterAutoscalerScalability2]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] shouldn't scale down with underutilized nodes due to host port conflicts [Feature:ClusterAutoscalerScalability5]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] shouldn't scale down with underutilized nodes due to host port conflicts [Feature:ClusterAutoscalerScalability5]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group down to 0[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group down to 0[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group up from 0[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group up from 0[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should not scale GPU pool up if pod does not require GPUs [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should not scale GPU pool up if pod does not require GPUs [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale down GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale down GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 0 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 0 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Shouldn't perform scale up operation and should list unhealthy status if most of the cluster is broken[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Shouldn't perform scale up operation and should list unhealthy status if most of the cluster is broken[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should add node to the particular mig [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should add node to the particular mig [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down when rescheduling a pod is required and pdb allows for it[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down when rescheduling a pod is required and pdb allows for it[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed and one node is broken [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed and one node is broken [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed when there is non autoscaled pool[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed when there is non autoscaled pool[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should disable node pool autoscaling [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should disable node pool autoscaling [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and one node is broken [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and one node is broken [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and there is another node pool that is not autoscaled [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and there is another node pool that is not autoscaled [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting EmptyDir volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting EmptyDir volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to host port conflict [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to host port conflict [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to pod anti-affinity [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to pod anti-affinity [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale down when expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale down when expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up correct target pool [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up correct target pool [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up when non expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up when non expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't be able to scale down when rescheduling a pod is required, but pdb doesn't allow drain[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't be able to scale down when rescheduling a pod is required, but pdb doesn't allow drain[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't increase cluster size if pending pod is too large [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't increase cluster size if pending pod is too large [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale down when non expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale down when non expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is preempted [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is preempted [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't trigger additional scale-ups during processing scale-up [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't trigger additional scale-ups during processing scale-up [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:ClusterSizeAutoscalingScaleUp] [Slow] Autoscaling Autoscaling a service from 1 pod and 3 nodes to 8 pods and >=4 nodes takes less than 15 minutes
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:ClusterSizeAutoscalingScaleUp] [Slow] Autoscaling Autoscaling a service from 1 pod and 3 nodes to 8 pods and >=4 nodes takes less than 15 minutes
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) CustomResourceDefinition Should scale with a CRD targetRef
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) CustomResourceDefinition Should scale with a CRD targetRef
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light Should scale from 1 pod to 2 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light Should scale from 1 pod to 2 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light [Slow] Should scale from 2 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light [Slow] Should scale from 2 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should not scale up on a busy sidecar with an idle application
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should not scale up on a busy sidecar with an idle application
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods on a busy application with an idle sidecar container
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods on a busy application with an idle sidecar container
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with long upscale stabilization window should scale up only after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with long upscale stabilization window should scale up only after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale down no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale down no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale up no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale up no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale down no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale down no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale up no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale up no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with short downscale stabilization window should scale down soon after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with short downscale stabilization window should scale down soon after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down to 0
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down to 0
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down with Prometheus
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down with Prometheus
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target average value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target average value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Container Resource and External Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Container Resource and External Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Pod and Object Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Pod and Object Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Pod and External metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Pod and External metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Resource and Object metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Resource and Object metrics)
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl api-versions should check if v1 is in available api versions [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl api-versions should check if v1 is in available api versions [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply apply set/view last-applied
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply apply set/view last-applied
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should apply a new configuration to an existing RC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should apply a new configuration to an existing RC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should reuse port when apply to an existing SVC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should reuse port when apply to an existing SVC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota with scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota with scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota without scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota without scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should reject quota with invalid scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should reject quota with invalid scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for cronjob
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for cronjob
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl events should show event when pod is created
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl events should show event when pod is created
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl expose should create services for rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl expose should create services for rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl get componentstatuses should get componentstatuses
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl get componentstatuses should get componentstatuses
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl label should update the label on a resource [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl label should update the label on a resource [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should remove all the taints with the same key off a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should remove all the taints with the same key off a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should update the taint on a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should update the taint on a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply an invalid/valid CR with arbitrary-extra properties for CRD with partially-specified validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply an invalid/valid CR with arbitrary-extra properties for CRD with partially-specified validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl version should check is all data is printed [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl version should check is all data is printed [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support --unix-socket=/path [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support --unix-socket=/path [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support proxy with --port 0 [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support proxy with --port 0 [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command with --leave-stdin-open
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command with --leave-stdin-open
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never, but with --rm
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never, but with --rm
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should contain last line of the log
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should contain last line of the log
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should handle in-cluster config
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should handle in-cluster config
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through an HTTP proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through an HTTP proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through kubectl proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through kubectl proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec using resource/name
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec using resource/name
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support inline execution and attach
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support inline execution and attach
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should scale a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should scale a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client kubectl wait should ignore not found error with --for=delete
Kubernetes e2e suite [It] [sig-cli] Kubectl client kubectl wait should ignore not found error with --for=delete
Kubernetes e2e suite [It] [sig-cli] Kubectl logs default container logs the second container is the default-container by annotation should log default container if not specified
Kubernetes e2e suite [It] [sig-cli] Kubectl logs default container logs the second container is the default-container by annotation should log default container if not specified
Kubernetes e2e suite [It] [sig-cli] Kubectl logs logs should be able to retrieve and filter logs [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl logs logs should be able to retrieve and filter logs [Conformance]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Addon update should propagate add-on file changes [Slow]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Addon update should propagate add-on file changes [Slow]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Downgrade [Feature:Downgrade] cluster downgrade should maintain a functioning cluster [Feature:ClusterDowngrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Downgrade [Feature:Downgrade] cluster downgrade should maintain a functioning cluster [Feature:ClusterDowngrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] GKE node pools [Feature:GKENodePool] should create a cluster with multiple node pools [Feature:GKENodePool]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] GKE node pools [Feature:GKENodePool] should create a cluster with multiple node pools [Feature:GKENodePool]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas different zones [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas different zones [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas multizone workers [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas multizone workers [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas same zone [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas same zone [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to cadvisor port 4194 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to cadvisor port 4194 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to the readonly kubelet port 10255 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to the readonly kubelet port 10255 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 10255 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 10255 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 4194 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 4194 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Recreate [Feature:Recreate] recreate nodes and ensure they function upon restart
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Recreate [Feature:Recreate] recreate nodes and ensure they function upon restart
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Restart [Disruptive] should restart all nodes and ensure all nodes and pods recover
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Restart [Disruptive] should restart all nodes and ensure all nodes and pods recover
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] [Disruptive]NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] [Disruptive]NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted
Kubernetes e2e suite [It] [sig-cloud-provider] [Feature:CloudProvider][Disruptive] Nodes should be deleted on API server if it doesn't exist in the cloud provider
Kubernetes e2e suite [It] [sig-cloud-provider] [Feature:CloudProvider][Disruptive] Nodes should be deleted on API server if it doesn't exist in the cloud provider
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the signed bootstrap tokens from clusterInfo ConfigMap when bootstrap token is deleted
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the signed bootstrap tokens from clusterInfo ConfigMap when bootstrap token is deleted
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the token secret when the secret expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the token secret when the secret expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should not delete the token secret when the secret is not expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should not delete the token secret when the secret is not expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should resign the bootstrap tokens when the clusterInfo ConfigMap updated [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should resign the bootstrap tokens when the clusterInfo ConfigMap updated [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should sign the new added bootstrap tokens
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should sign the new added bootstrap tokens
Kubernetes e2e suite [It] [sig-instrumentation] Events API should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should manage the lifecycle of an event [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should manage the lifecycle of an event [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Logging soak [Performance] [Slow] [Disruptive] should survive logging 1KB every 1s seconds, for a duration of 2m0s
Kubernetes e2e suite [It] [sig-instrumentation] Logging soak [Performance] [Slow] [Disruptive] should survive logging 1KB every 1s seconds, for a duration of 2m0s
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Kubelet.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Kubelet.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Scheduler.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Scheduler.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics slis from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics slis from API server.
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have accelerator metrics [Feature:StackdriverAcceleratorMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have accelerator metrics [Feature:StackdriverAcceleratorMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have cluster metrics [Feature:StackdriverMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have cluster metrics [Feature:StackdriverMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for external metrics [Feature:StackdriverExternalMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for external metrics [Feature:StackdriverExternalMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for new resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for new resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for old resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for old resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Stackdriver Metadata Agent [Feature:StackdriverMetadataAgent]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Stackdriver Metadata Agent [Feature:StackdriverMetadataAgent]
Kubernetes e2e suite [It] [sig-network] CVE-2021-29923 IPv4 Service Type ClusterIP with leading zeros should work interpreted as decimal
Kubernetes e2e suite [It] [sig-network] CVE-2021-29923 IPv4 Service Type ClusterIP with leading zeros should work interpreted as decimal
Kubernetes e2e suite [It] [sig-network] ClusterDns [Feature:Example] should create pod that uses dns
Kubernetes e2e suite [It] [sig-network] ClusterDns [Feature:Example] should create pod that uses dns
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when initial unready endpoints get ready
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when initial unready endpoints get ready
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service
Kubernetes e2e suite [It] [sig-network] Conntrack should drop INVALID conntrack entries [Privileged]
Kubernetes e2e suite [It] [sig-network] Conntrack should drop INVALID conntrack entries [Privileged]
Kubernetes e2e suite [It] [sig-network] DNS HostNetwork should resolve DNS of partial qualified names for services on hostNetwork pods with dnsPolicy: ClusterFirstWithHostNet [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS HostNetwork should resolve DNS of partial qualified names for services on hostNetwork pods with dnsPolicy: ClusterFirstWithHostNet [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS should provide /etc/hosts entries for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide /etc/hosts entries for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for ExternalName services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for ExternalName services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Hostname [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Hostname [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Provider:GCE]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Provider:GCE]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for the cluster [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for the cluster [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod DNS nameservers [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod DNS nameservers [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod resolv.conf
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod resolv.conf
Kubernetes e2e suite [It] [sig-network] DNS should work with the pod containing more than 6 DNS search paths and longer than 256 search list characters
Kubernetes e2e suite [It] [sig-network] DNS should work with the pod containing more than 6 DNS search paths and longer than 256 search list characters
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create Endpoints and EndpointSlices for Pods matching a Service [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create Endpoints and EndpointSlices for Pods matching a Service [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should support creating EndpointSlice API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should support creating EndpointSlice API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoint with multiple subsets and same IP address
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoint with multiple subsets and same IP address
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]
Kubernetes e2e suite [It] [sig-network] Firewall rule [Slow] [Serial] should create valid firewall rules for LoadBalancer type service
Kubernetes e2e suite [It] [sig-network] Firewall rule [Slow] [Serial] should create valid firewall rules for LoadBalancer type service
Kubernetes e2e suite [It] [sig-network] Firewall rule control plane should not expose well-known ports
Kubernetes e2e suite [It] [sig-network] Firewall rule control plane should not expose well-known ports
Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster
Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster
Kubernetes e2e suite [It] [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Ingress API should support creating Ingress API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] Ingress API should support creating Ingress API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass API should support creating IngressClass API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass API should support creating IngressClass API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should allow IngressClass to have Namespace-scoped parameters [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should allow IngressClass to have Namespace-scoped parameters [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should choose the one with the later CreationTimestamp, if equal the one with the lower name when two ingressClasses are marked as default[Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should choose the one with the later CreationTimestamp, if equal the one with the lower name when two ingressClasses are marked as default[Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should not set default value if no default IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should not set default value if no default IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should set default value on new IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should set default value on new IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] KubeProxy should set TCP CLOSE_WAIT timeout [Privileged]
Kubernetes e2e suite [It] [sig-network] KubeProxy should set TCP CLOSE_WAIT timeout [Privileged]
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should handle updates to ExternalTrafficPolicy field
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should handle updates to ExternalTrafficPolicy field
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should only target nodes with endpoints
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should only target nodes with endpoints
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=LoadBalancer
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=LoadBalancer
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=NodePort
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=NodePort
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work from pods
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work from pods
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a TCP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a TCP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a UDP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a UDP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create LoadBalancer Service without NodePort and change it [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create LoadBalancer Service without NodePort and change it [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create an internal type load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create an internal type load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should handle load balancer cleanup finalizer for service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should handle load balancer cleanup finalizer for service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should only allow access from service loadbalancer source ranges [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should only allow access from service loadbalancer source ranges [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should reconcile LB health check interval [Slow][Serial][Disruptive]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should reconcile LB health check interval [Slow][Serial][Disruptive]
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] rolling update backend pods should not cause service disruption
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] rolling update backend pods should not cause service disruption
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to create a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to create a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to switch between IG and NEG modes
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to switch between IG and NEG modes
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should create NEGs for all ports with the Ingress annotation, and NEGs for the standalone annotation otherwise
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should create NEGs for all ports with the Ingress annotation, and NEGs for the standalone annotation otherwise
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints for both Ingress-referenced NEG and standalone NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints for both Ingress-referenced NEG and standalone NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints to NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints to NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 Scalability GCE [Slow] [Serial] [Feature:IngressScale] Creating and updating ingresses should happen promptly with small/medium/large amount of ingresses
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 Scalability GCE [Slow] [Serial] [Feature:IngressScale] Creating and updating ingresses should happen promptly with small/medium/large amount of ingresses
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API with endport field
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API with endport field
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy with Status subresource [Feature:NetworkPolicyStatus]
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy with Status subresource [Feature:NetworkPolicyStatus]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from all pods in a namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from all pods in a namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from pods based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from pods based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress from pods on other namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress from pods on other namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce ingress policy allowing any port traffic to a server on a specific protocol [Feature:NetworkPolicy] [Feature:UDP]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce ingress policy allowing any port traffic to a server on a specific protocol [Feature:NetworkPolicy] [Feature:UDP]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Multiple PodSelectors and NamespaceSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Multiple PodSelectors and NamespaceSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on any PodSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on any PodSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic for a target [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic for a target [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic from pods in all namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic from pods in all namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic based on NamespaceSelector with MatchLabels using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic based on NamespaceSelector with MatchLabels using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not allow access by TCP when a policy specifies only UDP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not allow access by TCP when a policy specifies only UDP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not mistakenly treat 'protocol: SCTP' as 'protocol: TCP', even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not mistakenly treat 'protocol: SCTP' as 'protocol: TCP', even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should properly isolate pods that are selected by a policy allowing SCTP, even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should properly isolate pods that are selected by a policy allowing SCTP, even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support denying of egress traffic on the client side (even if the server explicitly allows this traffic) [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support denying of egress traffic on the client side (even if the server explicitly allows this traffic) [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should work with Ingress, Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should work with Ingress, Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] NetworkPolicy API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP [Feature:NetworkPolicy] [Serial]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP [Feature:NetworkPolicy] [Serial]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should work with Ingress,Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should work with Ingress,Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for multiple endpoint-Services with same selector
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for multiple endpoint-Services with same selector
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should support basic nodePort: udp functionality
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should support basic nodePort: udp functionality
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: http [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: http [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]
Kubernetes e2e suite [It] [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2
Kubernetes e2e suite [It] [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2
Kubernetes e2e suite [It] [sig-network] Networking should allow creating a Pod with an SCTP HostPort [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Networking should allow creating a Pod with an SCTP HostPort [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Networking should check kube-proxy urls
Kubernetes e2e suite [It] [sig-network] Networking should check kube-proxy urls
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv4]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv4]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv6][Experimental][LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv6][Experimental][LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking should provide unchanging, static URL paths for kubernetes api services
Kubernetes e2e suite [It] [sig-network] Networking should provide unchanging, static URL paths for kubernetes api services
Kubernetes e2e suite [It] [sig-network] Networking should provider Internet connection for containers using DNS [Feature:Networking-DNS]
Kubernetes e2e suite [It] [sig-network] Networking should provider Internet connection for containers using DNS [Feature:Networking-DNS]
Kubernetes e2e suite [It] [sig-network] Networking should recreate its iptables rules if they are deleted [Disruptive]
Kubernetes e2e suite [It] [sig-network] Networking should recreate its iptables rules if they are deleted [Disruptive]
Kubernetes e2e suite [It] [sig-network] NoSNAT [Feature:NoSNAT] [Slow] Should be able to send traffic between Pods without SNAT
Kubernetes e2e suite [It] [sig-network] NoSNAT [Feature:NoSNAT] [Slow] Should be able to send traffic between Pods without SNAT
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service Proxy [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service Proxy [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node with explicit kubelet port using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node with explicit kubelet port using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance]
Kubernetes e2e suite [It] [sig-network] Service endpoints latency should not be very high [Conformance]
Kubernetes e2e suite [It] [sig-network] Service endpoints latency should not be very high [Conformance]
Kubernetes e2e suite [It] [sig-network] Services GCE [Slow] should be able to create and tear down a standard-tier load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] Services GCE [Slow] should be able to create and tear down a standard-tier load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] Services should allow creating a basic SCTP service with pod and endpoints [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Services should allow creating a basic SCTP service with pod and endpoints [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Services should allow pods to hairpin back to themselves through services
Kubernetes e2e suite [It] [sig-network] Services should allow pods to hairpin back to themselves through services
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is true
Kubernetes e2e suite [It] [sig-network] Services should be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is true
Kubernetes e2e suite [It] [sig-network] Services should be able to create a functioning NodePort service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to create a functioning NodePort service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to up and down services
Kubernetes e2e suite [It] [sig-network] Services should be able to up and down services
Kubernetes e2e suite [It] [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols
Kubernetes e2e suite [It] [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols
Kubernetes e2e suite [It] [sig-network] Services should be possible to connect to a service via ExternalIP when the external IP is not assigned to a node
Kubernetes e2e suite [It] [sig-network] Services should be possible to connect to a service via ExternalIP when the external IP is not assigned to a node
Kubernetes e2e suite [It] [sig-network] Services should be rejected for evicted pods (no endpoints exist)
Kubernetes e2e suite [It] [sig-network] Services should be rejected for evicted pods (no endpoints exist)
Kubernetes e2e suite [It] [sig-network] Services should be rejected when no endpoints exist
Kubernetes e2e suite [It] [sig-network] Services should be rejected when no endpoints exist
Kubernetes e2e suite [It] [sig-network] Services should be updated after adding or deleting ports
Kubernetes e2e suite [It] [sig-network] Services should be updated after adding or deleting ports
Kubernetes e2e suite [It] [sig-network] Services should check NodePort out-of-range
Kubernetes e2e suite [It] [sig-network] Services should check NodePort out-of-range
Kubernetes e2e suite [It] [sig-network] Services should complete a service status lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should complete a service status lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should create endpoints for unready pods
Kubernetes e2e suite [It] [sig-network] Services should create endpoints for unready pods
Kubernetes e2e suite [It] [sig-network] Services should delete a collection of services [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should delete a collection of services [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should fail health check node port if there are only terminating endpoints [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fail health check node port if there are only terminating endpoints [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with externallTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with externallTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should find a service from listing all namespaces [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should find a service from listing all namespaces [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/headless
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/headless
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/service-proxy-name
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/service-proxy-name
Kubernetes e2e suite [It] [sig-network] Services should not be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is false
Kubernetes e2e suite [It] [sig-network] Services should not be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is false
Kubernetes e2e suite [It] [sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should prevent NodePort collisions
Kubernetes e2e suite [It] [sig-network] Services should prevent NodePort collisions
Kubernetes e2e suite [It] [sig-network] Services should provide secure master service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should provide secure master service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should release NodePorts on delete
Kubernetes e2e suite [It] [sig-network] Services should release NodePorts on delete
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should serve a basic endpoint from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve a basic endpoint from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve endpoints on same port and different protocol for internal traffic on Type LoadBalancer
Kubernetes e2e suite [It] [sig-network] Services should serve endpoints on same port and different protocol for internal traffic on Type LoadBalancer
Kubernetes e2e suite [It] [sig-network] Services should serve multiport endpoints from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve multiport endpoints from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should test the lifecycle of an Endpoint [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should test the lifecycle of an Endpoint [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting apiserver [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting apiserver [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting kube-proxy [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting kube-proxy [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after the service has been recreated
Kubernetes e2e suite [It] [sig-network] Services should work after the service has been recreated
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should be able to reach pod on ipv4 and ipv6 ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should be able to reach pod on ipv4 and ipv6 ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create a single stack service with cluster ip from primary service range
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create a single stack service with cluster ip from primary service range
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create pod, add ipv6 and ipv4 ip to pod ips
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create pod, add ipv6 and ipv4 ip to pod ips
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4,v6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4,v6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6,v4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6,v4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should have ipv4 and ipv6 internal node ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should have ipv4 and ipv6 internal node ip
Kubernetes e2e suite [It] [sig-network] [Feature:PerformanceDNS][Serial] Should answer DNS query for maximum number of services per cluster
Kubernetes e2e suite [It] [sig-network] [Feature:PerformanceDNS][Serial] Should answer DNS query for maximum number of services per cluster
Kubernetes e2e suite [It] [sig-network] [Feature:Topology Hints] should distribute endpoints evenly
Kubernetes e2e suite [It] [sig-network] [Feature:Topology Hints] should distribute endpoints evenly
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Downgrade kube-proxy from a DaemonSet to static pods should maintain a functioning cluster [Feature:KubeProxyDaemonSetDowngrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Downgrade kube-proxy from a DaemonSet to static pods should maintain a functioning cluster [Feature:KubeProxyDaemonSetDowngrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Upgrade kube-proxy from static pods to a DaemonSet should maintain a functioning cluster [Feature:KubeProxyDaemonSetUpgrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Upgrade kube-proxy from static pods to a DaemonSet should maintain a functioning cluster [Feature:KubeProxyDaemonSetUpgrade]
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles can disable an AppArmor profile, using unconfined
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles can disable an AppArmor profile, using unconfined
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles should enforce an AppArmor profile
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles should enforce an AppArmor profile
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should update ConfigMap successfully
Kubernetes e2e suite [It] [sig-node] ConfigMap should update ConfigMap successfully
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop https hook properly [MinimumKubeletVersion:1.23] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message as empty when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message as empty when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message from log output if TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message from log output if TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set as non-root user and at a non-default path [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set as non-root user and at a non-default path [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should be able to pull from private registry with secret [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should be able to pull from private registry with secret [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should be able to pull image [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should be able to pull image [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should not be able to pull from private registry without secret [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should not be able to pull from private registry without secret [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should not be able to pull image from invalid registry [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when running a container with a new image should not be able to pull image from invalid registry [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when starting a container that exits should run with the expected status [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Runtime blackbox test when starting a container that exits should run with the expected status [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default arguments (container cmd) [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default arguments (container cmd) [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default command (container entrypoint) [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default command (container entrypoint) [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default command and arguments [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should be able to override the image's default command and arguments [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should use the image defaults if command and args are blank [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Containers should use the image defaults if command and args are blank [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports external claim referenced by multiple containers of multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports external claim referenced by multiple containers of multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports external claim referenced by multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports external claim referenced by multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports init containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports init containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports inline claim referenced by multiple containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports inline claim referenced by multiple containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports simple pod referencing external resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports simple pod referencing external resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports simple pod referencing inline resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with delayed allocation supports simple pod referencing inline resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports external claim referenced by multiple containers of multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports external claim referenced by multiple containers of multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports external claim referenced by multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports external claim referenced by multiple pods
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports init containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports init containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports inline claim referenced by multiple containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports inline claim referenced by multiple containers
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports simple pod referencing external resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports simple pod referencing external resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports simple pod referencing inline resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] cluster with immediate allocation supports simple pod referencing inline resource claim
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] driver supports claim and class parameters
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] driver supports claim and class parameters
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must not run a pod if a claim is not reserved for it
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must not run a pod if a claim is not reserved for it
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must retry NodePrepareResource
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must retry NodePrepareResource
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must unprepare resources for force-deleted pod
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet must unprepare resources for force-deleted pod
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet registers plugin
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] kubelet registers plugin
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple drivers work
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple drivers work
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes reallocation works
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes reallocation works
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with network-attached resources schedules onto different nodes
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with network-attached resources schedules onto different nodes
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with node-local resources with delayed allocation uses all resources
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with node-local resources with delayed allocation uses all resources
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with node-local resources with immediate allocation uses all resources
Kubernetes e2e suite [It] [sig-node] DRA [Feature:DynamicResourceAllocation] multiple nodes with node-local resources with immediate allocation uses all resources
Kubernetes e2e suite [It] [sig-node] Downward API [Serial] [Disruptive] [NodeFeature:DownwardAPIHugePages] Downward API tests for hugepages should provide container's limits.hugepages-<pagesize> and requests.hugepages-<pagesize> as env vars
Kubernetes e2e suite [It] [sig-node] Downward API [Serial] [Disruptive] [NodeFeature:DownwardAPIHugePages] Downward API tests for hugepages should provide container's limits.hugepages-<pagesize> and requests.hugepages-<pagesize> as env vars
Kubernetes e2e suite [It] [sig-node] Downward API [Serial] [Disruptive] [NodeFeature:DownwardAPIHugePages] Downward API tests for hugepages should provide default limits.hugepages-<pagesize> from node allocatable
Kubernetes e2e suite [It] [sig-node] Downward API [Serial] [Disruptive] [NodeFeature:DownwardAPIHugePages] Downward API tests for hugepages should provide default limits.hugepages-<pagesize> from node allocatable
Kubernetes e2e suite [It] [sig-node] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide host IP and pod IP as an env var if pod uses host network [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Downward API should provide host IP and pod IP as an env var if pod uses host network [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Downward API should provide host IP as an env var [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide host IP as an env var [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide pod name, namespace and IP address as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Downward API should provide pod name, namespace and IP address as env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Ephemeral Containers [NodeConformance] will start an ephemeral container in an existing pod [Conformance]
Kubernetes e2e suite [It] [sig-node] Ephemeral Containers [NodeConformance] will start an ephemeral container in an existing pod [Conformance]
Kubernetes e2e suite [It] [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running
Kubernetes e2e suite [It] [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartAlways pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartAlways pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should not start app containers if init containers fail on a RestartAlways pod [Conformance]
Kubernetes e2e suite [It] [sig-node] InitContainer [NodeConformance] should not start app containers if init containers fail on a RestartAlways pod [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] experimental resource usage tracking [Feature:ExperimentalResourceUsageTracking] resource tracking for 100 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] experimental resource usage tracking [Feature:ExperimentalResourceUsageTracking] resource tracking for 100 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] regular resource usage tracking [Feature:RegularResourceUsageTracking] resource tracking for 0 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] regular resource usage tracking [Feature:RegularResourceUsageTracking] resource tracking for 0 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] regular resource usage tracking [Feature:RegularResourceUsageTracking] resource tracking for 100 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet [Serial] [Slow] regular resource usage tracking [Feature:RegularResourceUsageTracking] resource tracking for 100 pods per node
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command in a pod should print the output to logs [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command in a pod should print the output to logs [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a read only busybox container should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling a read only busybox container should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling an agnhost Pod with hostAliases should write entries to /etc/hosts [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Kubelet when scheduling an agnhost Pod with hostAliases should write entries to /etc/hosts [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Lease lease API should be available [Conformance]
Kubernetes e2e suite [It] [sig-node] Lease lease API should be available [Conformance]
Kubernetes e2e suite [It] [sig-node] Mount propagation should propagate mounts within defined scopes
Kubernetes e2e suite [It] [sig-node] Mount propagation should propagate mounts within defined scopes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Multiple Pods [Serial] evicts pods with minTolerationSeconds [Disruptive] [Conformance]
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Multiple Pods [Serial] evicts pods with minTolerationSeconds [Disruptive] [Conformance]
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Multiple Pods [Serial] only evicts pods without tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Multiple Pods [Serial] only evicts pods without tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] doesn't evict pod with tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] doesn't evict pod with tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] eventually evict pod with finite tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] eventually evict pod with finite tolerations from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] evicts pods from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] evicts pods from tainted nodes
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] pods evicted from tainted nodes have pod disruption condition
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] pods evicted from tainted nodes have pod disruption condition
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] removing taint cancels eviction [Disruptive] [Conformance]
Kubernetes e2e suite [It] [sig-node] NoExecuteTaintManager Single Pod [Serial] removing taint cancels eviction [Disruptive] [Conformance]
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease should have OwnerReferences set
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease should have OwnerReferences set
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease the kubelet should create and update a lease in the kube-node-lease namespace
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease the kubelet should create and update a lease in the kube-node-lease namespace
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease the kubelet should report node status infrequently
Kubernetes e2e suite [It] [sig-node] NodeLease NodeLease the kubelet should report node status infrequently
Kubernetes e2e suite [It] [sig-node] NodeProblemDetector should run without error
Kubernetes e2e suite [It] [sig-node] NodeProblemDetector should run without error
Kubernetes e2e suite [It] [sig-node] Pod garbage collector [Feature:PodGarbageCollector] [Slow] should handle the creation of 1000 pods
Kubernetes e2e suite [It] [sig-node] Pod garbage collector [Feature:PodGarbageCollector] [Slow] should handle the creation of 1000 pods
Kubernetes e2e suite [It] [sig-node] PodOSRejection [NodeConformance] Kubelet should reject pod when the node OS doesn't match pod's OS
Kubernetes e2e suite [It] [sig-node] PodOSRejection [NodeConformance] Kubelet should reject pod when the node OS doesn't match pod's OS
Kubernetes e2e suite [It] [sig-node] PodTemplates should delete a collection of pod templates [Conformance]
Kubernetes e2e suite [It] [sig-node] PodTemplates should delete a collection of pod templates [Conformance]
Kubernetes e2e suite [It] [sig-node] PodTemplates should replace a pod template [Conformance]
Kubernetes e2e suite [It] [sig-node] PodTemplates should replace a pod template [Conformance]
Kubernetes e2e suite [It] [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]
Kubernetes e2e suite [It] [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods Extended Delete Grace Period should be submitted and removed
Kubernetes e2e suite [It] [sig-node] Pods Extended Delete Grace Period should be submitted and removed
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container Status should never report container start when an init container fails
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container Status should never report success for a pending container
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container Status should never report success for a pending container
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container lifecycle evicted pods should be terminal
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container lifecycle evicted pods should be terminal
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container lifecycle should not create extra sandbox if all containers are done
Kubernetes e2e suite [It] [sig-node] Pods Extended Pod Container lifecycle should not create extra sandbox if all containers are done
Kubernetes e2e suite [It] [sig-node] Pods Extended Pods Set QOS Class should be set on Pods with matching resource requests and limits for memory and cpu [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods Extended Pods Set QOS Class should be set on Pods with matching resource requests and limits for memory and cpu [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should be submitted and removed [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should be submitted and removed [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should be updated [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should be updated [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should cap back-off at MaxContainerBackOff [Slow][NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should cap back-off at MaxContainerBackOff [Slow][NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should contain environment variables for services [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should contain environment variables for services [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should delete a collection of pods [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should delete a collection of pods [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should get a host IP [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should get a host IP [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should have their auto-restart back-off timer reset on image update [Slow][NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should have their auto-restart back-off timer reset on image update [Slow][NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should patch a pod status [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should patch a pod status [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should support pod readiness gates [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should support pod readiness gates [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Pods should support remote command execution over websockets [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should support remote command execution over websockets [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should support retrieving logs from the container over websockets [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Pods should support retrieving logs from the container over websockets [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process
Kubernetes e2e suite [It] [sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process
Kubernetes e2e suite [It] [sig-node] PreStop should call prestop when killing a pod [Conformance]
Kubernetes e2e suite [It] [sig-node] PreStop should call prestop when killing a pod [Conformance]
Kubernetes e2e suite [It] [sig-node] PrivilegedPod [NodeConformance] should enable privileged commands [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] PrivilegedPod [NodeConformance] should enable privileged commands [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted by liveness probe because startup probe delays it
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted by liveness probe because startup probe delays it
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a GRPC liveness probe [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a GRPC liveness probe [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a exec "cat /tmp/health" liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a exec "cat /tmp/health" liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a non-local redirect http liveness probe
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a non-local redirect http liveness probe
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be ready immediately after startupProbe succeeds
Kubernetes e2e suite [It] [sig-node] Probing container should be ready immediately after startupProbe succeeds
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted by liveness probe after startup probe enables it
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted by liveness probe after startup probe enables it
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted startup probe fails
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted startup probe fails
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a GRPC liveness probe [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a GRPC liveness probe [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a exec "cat /tmp/health" liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a exec "cat /tmp/health" liveness probe [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a failing exec liveness probe that took longer than the timeout
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a failing exec liveness probe that took longer than the timeout
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a local redirect http liveness probe
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with a local redirect http liveness probe
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with an exec liveness probe with timeout [MinimumKubeletVersion:1.20] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should be restarted with an exec liveness probe with timeout [MinimumKubeletVersion:1.20] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should have monotonically increasing restart count [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should have monotonically increasing restart count [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container should mark readiness on pods to false and disable liveness probes while pod is in progress of terminating
Kubernetes e2e suite [It] [sig-node] Probing container should mark readiness on pods to false and disable liveness probes while pod is in progress of terminating
Kubernetes e2e suite [It] [sig-node] Probing container should mark readiness on pods to false while pod is in progress of terminating when a pod has a readiness probe
Kubernetes e2e suite [It] [sig-node] Probing container should mark readiness on pods to false while pod is in progress of terminating when a pod has a readiness probe
Kubernetes e2e suite [It] [sig-node] Probing container should not be ready with an exec readiness probe timeout [MinimumKubeletVersion:1.20] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should not be ready with an exec readiness probe timeout [MinimumKubeletVersion:1.20] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Probing container should override timeoutGracePeriodSeconds when LivenessProbe field is set [Feature:ProbeTerminationGracePeriod]
Kubernetes e2e suite [It] [sig-node] Probing container should override timeoutGracePeriodSeconds when LivenessProbe field is set [Feature:ProbeTerminationGracePeriod]
Kubernetes e2e suite [It] [sig-node] Probing container should override timeoutGracePeriodSeconds when StartupProbe field is set [Feature:ProbeTerminationGracePeriod]
Kubernetes e2e suite [It] [sig-node] Probing container should override timeoutGracePeriodSeconds when StartupProbe field is set [Feature:ProbeTerminationGracePeriod]
Kubernetes e2e suite [It] [sig-node] Probing container with readiness probe should not be ready before initial delay and never restart [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container with readiness probe should not be ready before initial delay and never restart [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Probing container with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should support RuntimeClasses API operations [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should support RuntimeClasses API operations [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a RuntimeClass with an unconfigured handler [NodeFeature:RuntimeHandler]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a RuntimeClass with an unconfigured handler [NodeFeature:RuntimeHandler]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a RuntimeClass with conflicting node selector
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a RuntimeClass with conflicting node selector
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a deleted RuntimeClass [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a deleted RuntimeClass [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a non-existent RuntimeClass [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should reject a Pod requesting a non-existent RuntimeClass [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with a configured handler [NodeFeature:RuntimeHandler]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with a configured handler [NodeFeature:RuntimeHandler]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with scheduling with taints [Serial]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with scheduling with taints [Serial]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with scheduling without taints
Kubernetes e2e suite [It] [sig-node] RuntimeClass should run a Pod requesting a RuntimeClass with scheduling without taints
Kubernetes e2e suite [It] [sig-node] RuntimeClass should schedule a Pod requesting a RuntimeClass and initialize its Overhead [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should schedule a Pod requesting a RuntimeClass and initialize its Overhead [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should schedule a Pod requesting a RuntimeClass without PodOverhead [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] RuntimeClass should schedule a Pod requesting a RuntimeClass without PodOverhead [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] SSH should SSH to all nodes and run commands
Kubernetes e2e suite [It] [sig-node] SSH should SSH to all nodes and run commands
Kubernetes e2e suite [It] [sig-node] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should fail to create secret due to empty secret key [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should fail to create secret due to empty secret key [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should patch a secret [Conformance]
Kubernetes e2e suite [It] [sig-node] Secrets should patch a secret [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should not run with an explicit root user ID [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should not run with an explicit root user ID [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should not run without a specified user ID
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should not run without a specified user ID
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should run with an explicit non-root user ID [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should run with an explicit non-root user ID [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should run with an image specified user ID
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsNonRoot should run with an image specified user ID
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsUser should run the container with uid 0 [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsUser should run the container with uid 0 [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsUser should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a container with runAsUser should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers must create the user namespace if set to false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers must create the user namespace if set to false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers must not create the user namespace if set to true [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers must not create the user namespace if set to true [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers should mount all volumes with proper permissions with hostUsers=false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers should mount all volumes with proper permissions with hostUsers=false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers should set FSGroup to user inside the container with hostUsers=false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with HostUsers should set FSGroup to user inside the container with hostUsers=false [LinuxOnly] [Feature:UserNamespacesStatelessPodsSupport]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with privileged should run the container as privileged when true [LinuxOnly] [NodeFeature:HostAccess]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with privileged should run the container as privileged when true [LinuxOnly] [NodeFeature:HostAccess]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with privileged should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with privileged should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with readOnlyRootFilesystem should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with readOnlyRootFilesystem should run the container with readonly rootfs when readOnlyRootFilesystem=true [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context When creating a pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context should support container.SecurityContext.RunAsUser And container.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context should support container.SecurityContext.RunAsUser And container.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context should support container.SecurityContext.RunAsUser [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support container.SecurityContext.RunAsUser [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.SupplementalGroups [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support pod.Spec.SecurityContext.SupplementalGroups [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp default which is unconfined [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp default which is unconfined [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp runtime/default [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp runtime/default [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp unconfined on the container [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp unconfined on the container [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp unconfined on the pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support seccomp unconfined on the pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling when using hostIPC [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling when using hostIPC [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling when using hostPID [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context should support volume SELinux relabeling when using hostPID [Flaky] [LinuxOnly]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when not explicitly set and uid != 0 [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when not explicitly set and uid != 0 [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when true [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when true [LinuxOnly] [NodeConformance]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Security Context when if the container's primary UID belongs to some groups in the image [LinuxOnly] should add pod.Spec.SecurityContext.SupplementalGroups to them [LinuxOnly] in resultant supplementary groups for the container processes
Kubernetes e2e suite [It] [sig-node] Security Context when if the container's primary UID belongs to some groups in the image [LinuxOnly] should add pod.Spec.SecurityContext.SupplementalGroups to them [LinuxOnly] in resultant supplementary groups for the container processes
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should not launch unsafe, but not explicitly enabled sysctls on the node [MinimumKubeletVersion:1.21]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should not launch unsafe, but not explicitly enabled sysctls on the node [MinimumKubeletVersion:1.21]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should reject invalid sysctls [MinimumKubeletVersion:1.21] [Conformance]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should reject invalid sysctls [MinimumKubeletVersion:1.21] [Conformance]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls [MinimumKubeletVersion:1.21] [Conformance]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls [MinimumKubeletVersion:1.21] [Conformance]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls with slashes as separator [MinimumKubeletVersion:1.23]
Kubernetes e2e suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls with slashes as separator [MinimumKubeletVersion:1.23]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow composing env vars into new env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow composing env vars into new env vars [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a container's args [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a container's args [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a container's command [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a container's command [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a volume subpath [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should allow substituting values in a volume subpath [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should fail substituting values in a volume subpath with absolute path [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should fail substituting values in a volume subpath with absolute path [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should fail substituting values in a volume subpath with backticks [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should fail substituting values in a volume subpath with backticks [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should succeed in writing subpaths in container [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should succeed in writing subpaths in container [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should verify that a failing subpath expansion can be modified during the lifecycle of a container [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] Variable Expansion should verify that a failing subpath expansion can be modified during the lifecycle of a container [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Downward API should create a pod that prints his name and namespace
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Downward API should create a pod that prints his name and namespace
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Liveness liveness pods should be automatically restarted
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Liveness liveness pods should be automatically restarted
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Secret should create a pod that reads a secret
Kubernetes e2e suite [It] [sig-node] [Feature:Example] Secret should create a pod that reads a secret
Kubernetes e2e suite [It] [sig-node] crictl should be able to run crictl on the node
Kubernetes e2e suite [It] [sig-node] crictl should be able to run crictl on the node
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] cluster downgrade should be able to run gpu pod after downgrade [Feature:GPUClusterDowngrade]
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] cluster downgrade should be able to run gpu pod after downgrade [Feature:GPUClusterDowngrade]
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] cluster upgrade should be able to run gpu pod after upgrade [Feature:GPUClusterUpgrade]
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] cluster upgrade should be able to run gpu pod after upgrade [Feature:GPUClusterUpgrade]
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] master upgrade should NOT disrupt gpu pod [Feature:GPUMasterUpgrade]
Kubernetes e2e suite [It] [sig-node] gpu Upgrade [Feature:GPUUpgrade] master upgrade should NOT disrupt gpu pod [Feature:GPUMasterUpgrade]
Kubernetes e2e suite [It] [sig-node] kubelet Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s.
Kubernetes e2e suite [It] [sig-node] kubelet Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s.
Kubernetes e2e suite [It] [sig-node] kubelet host cleanup with volume mounts [HostCleanup][Flaky] Host cleanup after disrupting NFS volume [NFS] after stopping the nfs-server and deleting the (active) client pod, the NFS mount and the pod's UID directory should be removed.
Kubernetes e2e suite [It] [sig-node] kubelet host cleanup with volume mounts [HostCleanup][Flaky] Host cleanup after disrupting NFS volume [NFS] after stopping the nfs-server and deleting the (active) client pod, the NFS mount and the pod's UID directory should be removed.
Kubernetes e2e suite [It] [sig-node] kubelet host cleanup with volume mounts [HostCleanup][Flaky] Host cleanup after disrupting NFS volume [NFS] after stopping the nfs-server and deleting the (sleeping) client pod, the NFS mount and the pod's UID directory should be removed.
Kubernetes e2e suite [It] [sig-node] kubelet host cleanup with volume mounts [HostCleanup][Flaky] Host cleanup after disrupting NFS volume [NFS] after stopping the nfs-server and deleting the (sleeping) client pod, the NFS mount and the pod's UID directory should be removed.
Kubernetes e2e suite [It] [sig-scheduling] GPUDevicePluginAcrossRecreate [Feature:Recreate] run Nvidia GPU Device Plugin tests with a recreation
Kubernetes e2e suite [It] [sig-scheduling] GPUDevicePluginAcrossRecreate [Feature:Recreate] run Nvidia GPU Device Plugin tests with a recreation
Kubernetes e2e suite [It] [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] LimitRange should list, patch and delete a LimitRange by collection [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] LimitRange should list, patch and delete a LimitRange by collection [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] Multi-AZ Clusters should spread the pods of a replication controller across zones [Serial]
Kubernetes e2e suite [It] [sig-scheduling] Multi-AZ Clusters should spread the pods of a replication controller across zones [Serial]
Kubernetes e2e suite [It] [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]
Kubernetes e2e suite [It] [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] PodTopologySpread Filtering validates 4 pods with MaxSkew=1 are evenly distributed into 2 nodes
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] PodTopologySpread Filtering validates 4 pods with MaxSkew=1 are evenly distributed into 2 nodes
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates Pods with non-empty schedulingGates are blocked on scheduling [Feature:PodSchedulingReadiness] [alpha]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates Pods with non-empty schedulingGates are blocked on scheduling [Feature:PodSchedulingReadiness] [alpha]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates local ephemeral storage resource limits of pods that are allowed to run [Feature:LocalStorageCapacityIsolation]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates local ephemeral storage resource limits of pods that are allowed to run [Feature:LocalStorageCapacityIsolation]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates pod overhead is considered along with resource limits of pods that are allowed to run verify pod overhead is accounted for
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates pod overhead is considered along with resource limits of pods that are allowed to run verify pod overhead is accounted for
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPredicates [Serial] validates that there is no conflict between pods with same hostPort but different hostIP and protocol
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PodTopologySpread Preemption validates proper pods are preempted
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PodTopologySpread Preemption validates proper pods are preempted
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PriorityClass endpoints verify PriorityClass endpoints can be operated with different HTTP methods [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] PriorityClass endpoints verify PriorityClass endpoints can be operated with different HTTP methods [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance]
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates pod disruption condition is added to the preempted pod
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPreemption [Serial] validates pod disruption condition is added to the preempted pod
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] Pod should be preferably scheduled to nodes pod can tolerate
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] Pod should be preferably scheduled to nodes pod can tolerate
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] Pod should be scheduled to node that don't match the PodAntiAffinity terms
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] Pod should be scheduled to node that don't match the PodAntiAffinity terms
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] PodTopologySpread Scoring validates pod should be preferably scheduled to node which makes the matching pods more evenly distributed
Kubernetes e2e suite [It] [sig-scheduling] SchedulerPriorities [Serial] PodTopologySpread Scoring validates pod should be preferably scheduled to node which makes the matching pods more evenly distributed
Kubernetes e2e suite [It] [sig-scheduling] [Feature:GPUDevicePlugin] run Nvidia GPU Device Plugin tests
Kubernetes e2e suite [It] [sig-scheduling] [Feature:GPUDevicePlugin] run Nvidia GPU Device Plugin tests
Kubernetes e2e suite [It] [sig-storage] CSI Mock fsgroup as mount option Delegate FSGroup to CSI driver [LinuxOnly] should not pass FSGroup to CSI driver if it is set in pod and driver supports VOLUME_MOUNT_GROUP
Kubernetes e2e suite [It] [sig-storage] CSI Mock fsgroup as mount option Delegate FSGroup to CSI driver [LinuxOnly] should not pass FSGroup to CSI driver if it is set in pod and driver supports VOLUME_MOUNT_GROUP
Kubernetes e2e suite [It] [sig-storage] CSI Mock fsgroup as mount option Delegate FSGroup to CSI driver [LinuxOnly] should pass FSGroup to CSI driver if it is set in pod and driver supports VOLUME_MOUNT_GROUP
Kubernetes e2e suite [It] [sig-storage] CSI Mock fsgroup as mount option Delegate FSGroup to CSI driver [LinuxOnly] should pass FSGroup to CSI driver if it is set in pod and driver supports VOLUME_MOUNT_GROUP
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should add SELinux mount option to existing mount options
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should add SELinux mount option to existing mount options
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for CSI driver that does not support SELinux mount
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for CSI driver that does not support SELinux mount
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for Pod without SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for Pod without SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for RWO volume
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not pass SELinux mount option for RWO volume
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not unstage volume when starting a second pod with the same SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should not unstage volume when starting a second pod with the same SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should pass SELinux mount option for RWOP volume and Pod with SELinux context set
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should pass SELinux mount option for RWOP volume and Pod with SELinux context set
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should unstage volume when starting a second pod with different SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock selinux on mount SELinuxMount [LinuxOnly][Feature:SELinux][Feature:SELinuxMountReadWriteOncePod] should unstage volume when starting a second pod with different SELinux context
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI CSIDriver deployment after pod creation using non-attachable mock driver should bringup pod after deploying CSIDriver attach=false [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI CSIDriver deployment after pod creation using non-attachable mock driver should bringup pod after deploying CSIDriver attach=false [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should not require VolumeAttach for drivers without attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should not require VolumeAttach for drivers without attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should preserve attachment policy when no CSIDriver present
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should preserve attachment policy when no CSIDriver present
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should require VolumeAttach for drivers with attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should require VolumeAttach for drivers with attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should require VolumeAttach for ephemermal volume and drivers with attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume attach CSI attach test using mock driver should require VolumeAttach for ephemermal volume and drivers with attachment
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume by restarting pod if attach=off, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume by restarting pod if attach=off, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume by restarting pod if attach=on, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume by restarting pod if attach=on, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume without restarting pod if nodeExpansion=off
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should expand volume without restarting pod if nodeExpansion=off
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should not expand volume if resizingOnDriver=off, resizingOnSC=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI Volume expansion should not expand volume if resizingOnDriver=off, resizingOnSC=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI online volume expansion should expand volume without restarting pod if attach=off, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI online volume expansion should expand volume without restarting pod if attach=off, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI online volume expansion should expand volume without restarting pod if attach=on, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion CSI online volume expansion should expand volume without restarting pod if attach=on, nodeExpansion=on
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] recovery should not be possible in partially expanded volumes
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] recovery should not be possible in partially expanded volumes
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] should allow recovery if controller expansion fails with final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] should allow recovery if controller expansion fails with final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] should record target size in allocated resources
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume expansion Expansion with recovery[Feature:RecoverVolumeExpansionFailure] should record target size in allocated resources
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=File
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=File
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=default
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should modify fsGroup if fsGroupPolicy=default
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should not modify fsGroup if fsGroupPolicy=None
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume fsgroup policies CSI FSGroupPolicy [LinuxOnly] should not modify fsGroup if fsGroupPolicy=None
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit for generic ephemeral volume when persistent volume is attached [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit for generic ephemeral volume when persistent volume is attached [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit for persistent volume when generic ephemeral volume is attached [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit for persistent volume when generic ephemeral volume is attached [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit when limit is bigger than 0 [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume limit CSI volume limit information using mock driver should report attach limit when limit is bigger than 0 [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should call NodeUnstage after NodeStage ephemeral error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should call NodeUnstage after NodeStage ephemeral error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should call NodeUnstage after NodeStage success
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should call NodeUnstage after NodeStage success
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should not call NodeUnstage after NodeStage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should not call NodeUnstage after NodeStage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should retry NodeStage after NodeStage ephemeral error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should retry NodeStage after NodeStage ephemeral error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should retry NodeStage after NodeStage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeStage error cases [Slow] should retry NodeStage after NodeStage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] should call NodeStage after NodeUnstage success
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] should call NodeStage after NodeUnstage success
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] two pods: should call NodeStage after previous NodeUnstage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] two pods: should call NodeStage after previous NodeUnstage final error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] two pods: should call NodeStage after previous NodeUnstage transient error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume node stage CSI NodeUnstage error cases [Slow] two pods: should call NodeStage after previous NodeUnstage transient error
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should be plumbed down when csiServiceAccountTokenEnabled=true
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should be plumbed down when csiServiceAccountTokenEnabled=true
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should not be plumbed down when CSIDriver is not deployed
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should not be plumbed down when CSIDriver is not deployed
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should not be plumbed down when csiServiceAccountTokenEnabled=false
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume service account token CSIServiceAccountToken token should not be plumbed down when csiServiceAccountTokenEnabled=false
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Snapshot Controller metrics [Feature:VolumeSnapshotDataSource] snapshot controller should emit dynamic CreateSnapshot, CreateSnapshotAndReady, and DeleteSnapshot metrics
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Snapshot Controller metrics [Feature:VolumeSnapshotDataSource] snapshot controller should emit dynamic CreateSnapshot, CreateSnapshotAndReady, and DeleteSnapshot metrics
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Snapshot Controller metrics [Feature:VolumeSnapshotDataSource] snapshot controller should emit pre-provisioned CreateSnapshot, CreateSnapshotAndReady, and DeleteSnapshot metrics
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Snapshot Controller metrics [Feature:VolumeSnapshotDataSource] snapshot controller should emit pre-provisioned CreateSnapshot, CreateSnapshotAndReady, and DeleteSnapshot metrics
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Volume Snapshots [Feature:VolumeSnapshotDataSource] volumesnapshotcontent and pvc in Bound state with deletion timestamp set should not get deleted while snapshot finalizer exists
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Volume Snapshots [Feature:VolumeSnapshotDataSource] volumesnapshotcontent and pvc in Bound state with deletion timestamp set should not get deleted while snapshot finalizer exists
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Volume Snapshots secrets [Feature:VolumeSnapshotDataSource] volume snapshot create/delete with secrets
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume snapshot CSI Volume Snapshots secrets [Feature:VolumeSnapshotDataSource] volume snapshot create/delete with secrets
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity disabled
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity disabled
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity unused
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity unused
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, have capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, have capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, insufficient capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, insufficient capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, no capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity CSIStorageCapacity CSIStorageCapacity used, no capacity
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, immediate binding
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, immediate binding
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, late binding, no topology
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, late binding, no topology
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, late binding, with topology
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity exhausted, late binding, with topology
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity unlimited
Kubernetes e2e suite [It] [sig-storage] CSI Mock volume storage capacity storage capacity unlimited
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver contain ephemeral=true when using inline volume
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver contain ephemeral=true when using inline volume
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should be passed when podInfoOnMount=true
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should be passed when podInfoOnMount=true
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when CSIDriver does not exist
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when CSIDriver does not exist
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when podInfoOnMount=false
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when podInfoOnMount=false
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when podInfoOnMount=nil
Kubernetes e2e suite [It] [sig-storage] CSI Mock workload info CSI workload information using mock driver should not be passed when podInfoOnMount=nil
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] capacity provides storage capacity information
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] capacity provides storage capacity information
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (delayed binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (delayed binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance should provision volumes at scale within performance constraints [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance should provision volumes at scale within performance constraints [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (immediate binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (immediate binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Inline-volume (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: CSI Ephemeral-volume (default fs)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down cleans up when the kubelet returns.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (block volmode)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] capacity provides storage capacity information
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] capacity provides storage capacity information
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (Always)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with different fsgroup applied to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] read-write-once-pod[Feature:ReadWriteOncePod] should block a second pod from using an in-use ReadWriteOncePod volume on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volume-stress multiple pods should access different volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (default fs)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (delayed binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (delayed binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext3)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext3)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ext4)] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv used in a pod that is force deleted while the kubelet is down is usable by a new pod with a different SELinux context when kubelet returns [Feature:SELinux][Feature:SELinuxMountReadWriteOncePod].
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart.
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance should provision volumes at scale within performance constraints [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volume-lifecycle-performance should provision volumes at scale within performance constraints [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should fail to use a volume in a pod with mismatched mode [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode should not mount / map unused volumes in a pod [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (immediate binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (immediate binding)] topology should fail to schedule a pod which has topologies that conflict with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand Verify if offline PVC expansion works
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)(allowExpansion)][Feature:Windows] volume-expand should resize volume when PVC is edited while pod is using it
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should mount multiple PV pointing to the same storage on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with any volume data source [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with mount options
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with pvc data source in parallel [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] provisioning should provision storage with snapshot data source [Feature:VolumeSnapshotDataSource]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volume-expand should not allow expansion of pvcs without AllowVolumeExpansion property
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (ntfs)][Feature:Windows] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on different node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the single volume from pods on the same node
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and its clone from pods on the same node [LinuxOnly][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] multiVolume [Slow] should concurrently access the volume and restored snapshot from pods on the same node [LinuxOnly][Feature:VolumeSnapshotDataSource][Feature:VolumeSourceXFS]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] volumes should allow exec of files on the volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic PV (xfs)][Slow] volumes should store data
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable-stress[Feature:VolumeSnapshotDataSource] should support snapshotting of many volumes repeatedly [Slow] [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral)
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read-only inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support expansion of pvcs created for ephemeral pvcs
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support multiple inline ephemeral volumes
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should support two pods which have the same volume definition
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should support volume limits [Serial]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Generic Ephemeral-volume (default fs)] volumeLimits should verify that all csinodes have volume limits
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath directory is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath file is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support creating multiple subpath from same volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing directories when readOnly specified in the volumeSource
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing directory
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support existing single file [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support non-existent path
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using directory as subpath [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should support restarting containers using file as subpath [Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is force deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] volumeIO should write files of various sizes, verify size, validate content [Slow]
Kubernetes e2e suite [It] [sig-storage] CSI Volumes [Driver: pd.csi.storage.gke.io][Serial] [Testpattern: Inline-volume (default fs)] volumeIO should write files of various sizes, verify