[tzifudzi:~/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows] feature/secondary-ip-configs(+11/-15,1)+* 3h0m40s 130 ± ginkgo --skip=Stress -v --timeout 180m -- --cluster-kubeconfig='/Users/tzifudzi/.kube/config' --cluster-name=$CLUSTER_NAME --aws-region=$AWS_REGION --aws-vpc-id=$VPC_ID --ginkgo.skip="stress" Ginkgo detected a version mismatch between the Ginkgo CLI and the version of Ginkgo imported by your packages: Ginkgo CLI Version: 2.11.0 Mismatched package versions found: 2.19.0 used by windows Ginkgo will continue to attempt to run but you may see errors (including flag parsing errors) and should either update your go.mod or your version of the Ginkgo CLI to match. To install the matching version of the CLI run go install github.com/onsi/ginkgo/v2/ginkgo from a path that contains a go.mod file. Alternatively you can use go run github.com/onsi/ginkgo/v2/ginkgo from a path that contains a go.mod file to invoke the matching version of the Ginkgo CLI. If you are attempting to test multiple packages that each have a different version of the Ginkgo library with a single Ginkgo CLI that is currently unsupported. Running Suite: Windows Integration Test Suite - /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows ========================================================================================================================================== Random Seed: 1721744136 Will run 34 of 40 specs ------------------------------ [BeforeSuite] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_suite_test.go:53 STEP: creating the configmap with flag set to true if not exists @ 07/23/24 07:15:42.249 STEP: updating the configmap @ 07/23/24 07:15:43.085 STEP: getting the list of Windows node @ 07/23/24 07:15:53.135 STEP: checking nodes have capacity present @ 07/23/24 07:15:53.136 STEP: getting the instance ID for the first node @ 07/23/24 07:15:53.237 STEP: getting the security group associated with the instance @ 07/23/24 07:15:53.237 STEP: authorizing the security group ingress for HTTP traffic @ 07/23/24 07:15:53.491 [BeforeSuite] PASSED [11.521 seconds] ------------------------------ SSSSSS ------------------------------ Windows Integration Test configMap enable-windows-ipam tests when configmap created [CANARY] when enable-windows-ipam is True pod should be running and have resourceLimit injected /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:122 STEP: updating the configmap @ 07/23/24 07:15:53.779 STEP: creating pod and waiting for ready @ 07/23/24 07:16:03.805 STEP: updating the configmap @ 07/23/24 07:16:42.866 • [67.228 seconds] ------------------------------ Windows Integration Test configMap enable-windows-ipam tests when configmap created when enable-windows-ipam is incorrect pod should not be running and should not have resource limits /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:134 STEP: updating the configmap @ 07/23/24 07:17:01.022 STEP: creating pod and waiting for timeout @ 07/23/24 07:17:11.067 STEP: updating the configmap @ 07/23/24 07:21:26.145 • [283.284 seconds] ------------------------------ Windows Integration Test configMap enable-windows-ipam tests when configmap created When data is missing pod should not be running and should not have resource limits /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:146 STEP: updating the configmap @ 07/23/24 07:21:44.298 STEP: creating pod and wait for timeout @ 07/23/24 07:21:54.323 STEP: updating the configmap @ 07/23/24 07:26:09.454 • [283.309 seconds] ------------------------------ Windows Integration Test configMap enable-windows-ipam tests when configmap created when enable-windows-ipam is set to true but old controller deployment exists pod should fail to create /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:155 STEP: updating the configmap @ 07/23/24 07:26:27.642 STEP: creating a dummy deployment for vpc-resource-controller @ 07/23/24 07:26:37.675 STEP: creating windows pod and waiting for it to timout @ 07/23/24 07:26:53.759 STEP: deleting the old controller dummy deployment @ 07/23/24 07:31:10.85 STEP: creating windows pod and waiting for it to run @ 07/23/24 07:31:12.878 STEP: updating the configmap @ 07/23/24 07:31:51.943 • [344.449 seconds] ------------------------------ Windows Integration Test configMap enable-windows-ipam tests [CANARY] when configmap not created pod should not be running and should not have resource limits /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:203 STEP: deleting the configmap @ 07/23/24 07:32:12.097 STEP: creating pod and waiting for timeout @ 07/23/24 07:32:22.151 STEP: creating the configmap @ 07/23/24 07:36:37.27 • [281.271 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-prefix-target is set to non zero value if windows-warm-prefix-target is 2 the value should be ignored and no prefixes should be assigned [windows-prefix-delegation-disabled, windows-warm-prefix-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:261 STEP: checking nodes have capacity present @ 07/23/24 07:36:53.369 STEP: updating the configmap @ 07/23/24 07:36:53.369 STEP: updating the configmap @ 07/23/24 07:36:53.369 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-warm-prefix-target:2] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: creating 1 Windows pod and waiting until in ready status with timeout of 240 seconds @ 07/23/24 07:37:43.394 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:38:22.451 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap @ 07/23/24 07:38:35.809 STEP: updating the configmap @ 07/23/24 07:38:35.809 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [117.499 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target is set to non zero value if windows-warm-ip-target is 1 should have 1 warm IPs available when 0 pods were running [windows-prefix-delegation-disabled, windows-warm-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:285 STEP: checking nodes have capacity present @ 07/23/24 07:38:50.868 STEP: updating the configmap @ 07/23/24 07:38:50.868 STEP: updating the configmap @ 07/23/24 07:38:50.868 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:0 windows-warm-ip-target:1] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: updating the configmap @ 07/23/24 07:39:47.176 STEP: updating the configmap @ 07/23/24 07:39:47.176 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [71.366 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target is 5 should have 7 warm IPs available when 2 pods were running [windows-prefix-delegation-disabled, windows-warm-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:298 STEP: checking nodes have capacity present @ 07/23/24 07:40:02.254 STEP: updating the configmap @ 07/23/24 07:40:02.254 STEP: updating the configmap @ 07/23/24 07:40:02.254 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-warm-ip-target:5] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: creating 2 Windows pods and waiting until in ready status with timeout of 240 seconds @ 07/23/24 07:40:52.302 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:42:10.424 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:42:10.424 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap @ 07/23/24 07:42:25.955 STEP: updating the configmap @ 07/23/24 07:42:25.955 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [158.782 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-minimum-ip-target is set to non zero value if windows-minimum-ip-target is 6 should have 6 warm IPs available when 0 pods were running [windows-prefix-delegation-disabled, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:327 STEP: checking nodes have capacity present @ 07/23/24 07:42:41.068 STEP: updating the configmap @ 07/23/24 07:42:41.068 STEP: updating the configmap @ 07/23/24 07:42:41.068 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:6] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: updating the configmap @ 07/23/24 07:43:37.345 STEP: updating the configmap @ 07/23/24 07:43:37.345 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [71.383 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-minimum-ip-target is set to 6 with 3 pods running if windows-minimum-ip-target is 6 should have 6 IPs assigned to the node when 3 pods were running [windows-prefix-delegation-disabled, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:339 STEP: checking nodes have capacity present @ 07/23/24 07:43:52.404 STEP: updating the configmap @ 07/23/24 07:43:52.404 STEP: updating the configmap @ 07/23/24 07:43:52.404 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:6] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: creating 3 Windows pods and waiting until in ready status with timeout of 240 seconds @ 07/23/24 07:44:42.433 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:46:40.263 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:46:40.263 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:46:40.263 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap @ 07/23/24 07:46:57.71 STEP: updating the configmap @ 07/23/24 07:46:57.71 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [200.371 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target and windows-minimum-ip-target set to non zero values windows-minimum-ip-target=3 and windows-warm-ip-target=6 if should have 6 IPs assigned and 6 warm IPs available when 0 pods were running [windows-prefix-delegation-disabled, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:375 STEP: checking nodes have capacity present @ 07/23/24 07:47:12.785 STEP: updating the configmap @ 07/23/24 07:47:12.785 STEP: updating the configmap @ 07/23/24 07:47:12.786 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:3 windows-warm-ip-target:6] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: updating the configmap @ 07/23/24 07:48:09.122 STEP: updating the configmap @ 07/23/24 07:48:09.122 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [71.417 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target and windows-minimum-ip-target set to non zero values windows-minimum-ip-target=8 and windows-warm-ip-target=4 should have 8 IPs assigned and 8 warm IPs available when 0 pods were running [windows-prefix-delegation-disabled, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:388 STEP: checking nodes have capacity present @ 07/23/24 07:48:24.195 STEP: updating the configmap @ 07/23/24 07:48:24.195 STEP: updating the configmap @ 07/23/24 07:48:24.195 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:8 windows-warm-ip-target:4] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: updating the configmap @ 07/23/24 07:49:20.49 STEP: updating the configmap @ 07/23/24 07:49:20.491 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [71.348 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target and windows-minimum-ip-target set to non zero values windows-minimum-ip-target=2 and windows-warm-ip-target=4 should have 6 IPs assigned and 4 warm IPs available when 2 pods were running [windows-prefix-delegation-disabled, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:400 STEP: checking nodes have capacity present @ 07/23/24 07:49:35.555 STEP: updating the configmap @ 07/23/24 07:49:35.555 STEP: updating the configmap @ 07/23/24 07:49:35.555 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false warm-ip-target:4 windows-minimum-ip-target:2] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: creating 2 Windows pods and waiting until in ready status with timeout of 240 seconds @ 07/23/24 07:50:25.591 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:51:43.732 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 07:51:43.732 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap @ 07/23/24 07:51:59.159 STEP: updating the configmap @ 07/23/24 07:51:59.159 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [158.668 seconds] ------------------------------ Windows Integration Test configMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active When windows-warm-ip-target and windows-min-ip-target set to 0 should result in warm-ip-target=1 and min-ip-target=0 [windows-prefix-delegation-disabled, windows-warm-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:432 STEP: checking nodes have capacity present @ 07/23/24 07:52:14.222 STEP: updating the configmap @ 07/23/24 07:52:14.222 STEP: updating the configmap @ 07/23/24 07:52:14.222 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false windows-minimum-ip-target:0 windows-warm-ip-target:0] Waiting 5 seconds for pool reconciliation... Waiting 35 seconds for cooldown period... STEP: updating the configmap @ 07/23/24 07:53:12.519 STEP: updating the configmap @ 07/23/24 07:53:12.519 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... • [73.357 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled [CANARY] When enable-windows-prefix-delegation is true pod should be running and assigned ips are from prefix [windows-prefix-delegation] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:520 STEP: checking nodes have capacity present @ 07/23/24 07:53:27.552 STEP: updating the configmap @ 07/23/24 07:53:27.584 STEP: creating pod and waiting for ready @ 07/23/24 07:53:37.608 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 07:54:16.803 STEP: updating the configmap @ 07/23/24 07:54:18.85 • [67.378 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When warm-prefix-target is set to 2 two prefixes should be assigned [windows-prefix-delegation, warm-prefix-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:545 STEP: checking nodes have capacity present @ 07/23/24 07:54:34.93 STEP: updating the configmap @ 07/23/24 07:54:34.956 STEP: creating pod and waiting for ready should have 1 new prefix assigned @ 07/23/24 07:55:15.221 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 07:55:54.278 STEP: updating the configmap @ 07/23/24 07:55:56.457 • [97.579 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When warm-ip-target is set to 15 should assign new prefix when 2nd pod is launched [windows-prefix-delegation, warm-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:576 STEP: checking nodes have capacity present @ 07/23/24 07:56:12.513 STEP: updating the configmap @ 07/23/24 07:56:12.542 STEP: creating 1 pod and waiting for ready should not create new prefix @ 07/23/24 07:56:52.731 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 07:57:31.876 STEP: creating 2nd pod and waiting for ready should have 1 more prefix assigned @ 07/23/24 07:57:31.876 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 07:58:11.064 STEP: updating the configmap @ 07/23/24 07:58:15.147 • [138.686 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When minimum-ip-target is set to 20 should have 2 prefixes to satisfy minimum-ip-target when no pods running [windows-prefix-delegation, minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:623 STEP: checking nodes have capacity present @ 07/23/24 07:58:31.198 STEP: updating the configmap @ 07/23/24 07:58:31.234 STEP: adding labels to selected nodes for testing @ 07/23/24 07:58:41.261 STEP: creating 33 pods and waiting for ready should have 3 prefixes attached @ 07/23/24 07:59:11.427 STEP: deleting 33 pods should still have 2 prefixes attached @ 07/23/24 08:02:05.714 STEP: removing labels on selected nodes for testing @ 07/23/24 08:03:07.895 STEP: updating the configmap @ 07/23/24 08:03:07.959 • [296.821 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When windows-warm-prefix-target is set to 2 two prefixes should be assigned [windows-prefix-delegation, windows-warm-prefix-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:678 STEP: checking nodes have capacity present @ 07/23/24 08:03:28.022 STEP: updating the configmap @ 07/23/24 08:03:28.058 STEP: creating pod and waiting for ready should have 1 new prefix assigned @ 07/23/24 08:04:08.218 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 08:04:47.273 STEP: updating the configmap @ 07/23/24 08:04:49.447 • [97.509 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When windows-warm-ip-target is set to 15 should assign new prefix when 2nd pod is launched [windows-prefix-delegation, windows-warm-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:708 STEP: checking nodes have capacity present @ 07/23/24 08:05:05.533 STEP: updating the configmap @ 07/23/24 08:05:05.565 STEP: creating 1 pod and waiting for ready should not create new prefix @ 07/23/24 08:05:45.763 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 08:06:24.922 STEP: creating 2nd pod and waiting for ready should have 1 more prefix assigned @ 07/23/24 08:06:24.922 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP @ 07/23/24 08:07:04.219 STEP: updating the configmap @ 07/23/24 08:07:08.347 • [138.889 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When windows-minimum-ip-target is set to 20 should have 2 prefixes to satisfy windows-minimum-ip-target when no pods running [windows-prefix-delegation, windows-minimum-ip-target] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:754 STEP: checking nodes have capacity present @ 07/23/24 08:07:24.423 STEP: updating the configmap @ 07/23/24 08:07:24.509 STEP: adding labels to selected nodes for testing @ 07/23/24 08:07:34.548 STEP: creating 33 pods and waiting for ready should have 3 prefixes attached @ 07/23/24 08:08:04.735 STEP: deleting 33 pods should still have 2 prefixes attached @ 07/23/24 08:10:57.007 STEP: removing labels on selected nodes for testing @ 07/23/24 08:11:59.175 STEP: updating the configmap @ 07/23/24 08:12:04.293 • [299.936 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled [CANARY] When enable-windows-prefix-delegation is toggled to false prefixes should be released [windows-prefix-delegation] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:807 STEP: checking nodes have capacity present @ 07/23/24 08:12:24.363 STEP: updating the configmap @ 07/23/24 08:12:24.394 STEP: creating pod and waiting for ready should have secondary IP assigned @ 07/23/24 08:13:04.561 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:13:44.312 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:14:23.363 STEP: updating the configmap @ 07/23/24 08:14:23.595 • [135.297 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When enable-windows-prefix-delegation is incorrect pod should be running with secondary ip assigned and not prefix ip [windows-prefix-delegation] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:842 STEP: checking nodes have capacity present @ 07/23/24 08:14:39.661 STEP: updating the configmap @ 07/23/24 08:14:39.8 STEP: creating pod and waiting for ready @ 07/23/24 08:14:49.89 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:15:28.979 STEP: updating the configmap @ 07/23/24 08:15:28.98 • [65.371 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled When PD flag present but IPAM flag is missing pod should not be running and should not have resource limits [windows-prefix-delegation] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:855 STEP: checking nodes have capacity present @ 07/23/24 08:15:45.033 STEP: updating the configmap @ 07/23/24 08:15:45.065 STEP: creating pod and waiting for timeout @ 07/23/24 08:15:55.094 STEP: updating the configmap @ 07/23/24 08:20:10.147 • [281.208 seconds] ------------------------------ Windows Integration Test configMap enable-windows-prefix-delegation tests when prefix delegation is enabled when enable-windows-prefix-delegation is set to true but old controller deployment exists pod should fail to create [windows-prefix-delegation] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:870 STEP: checking nodes have capacity present @ 07/23/24 08:20:26.244 STEP: updating the configmap @ 07/23/24 08:20:26.299 STEP: creating a dummy deployment for vpc-resource-controller @ 07/23/24 08:20:36.324 STEP: creating windows pod and waiting for it to timeout @ 07/23/24 08:20:54.36 STEP: deleting the old controller dummy deployment @ 07/23/24 08:25:11.531 STEP: creating windows pod and waiting for it to run @ 07/23/24 08:25:13.566 STEP: updating the configmap @ 07/23/24 08:25:52.649 • [342.484 seconds] ------------------------------ Windows Integration Test [CANARY] windows connectivity tests when multiples jobs are created that try connect to a service all job should complete /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:940 STEP: updating the configmap @ 07/23/24 08:26:08.867 STEP: verifying the job has same IPv4 Address as allocated by the controller @ 07/23/24 08:29:13.045 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.046 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:29:13.047 [controller-runtime] log.SetLogger(...) was never called; logs will not be displayed. Detected at: > goroutine 857 [running]: > runtime/debug.Stack() > /usr/local/go/src/runtime/debug/stack.go:24 +0x64 > sigs.k8s.io/controller-runtime/pkg/log.eventuallyFulfillRoot() > /Users/tzifudzi/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/log.go:60 +0xf4 > sigs.k8s.io/controller-runtime/pkg/log.(*delegatingLogSink).Enabled(0x14000830200, 0x0) > /Users/tzifudzi/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/deleg.go:111 +0x30 > github.com/go-logr/logr.Logger.Info({{0x102c8acb0?, 0x14000830200?}, 0x1400062e400?}, {0x1400062e400, 0xa3}, {0x0, 0x0, 0x0}) > /Users/tzifudzi/go/pkg/mod/github.com/go-logr/logr@v1.4.2/logr.go:276 +0x5c > sigs.k8s.io/controller-runtime/pkg/log.(*KubeAPIWarningLogger).HandleWarningHeader(0x1400080ac60?, 0x14000e3fe60?, {0x1021ec01a?, 0x7?}, {0x1400062e400?, 0xa3?}) > /Users/tzifudzi/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/warning_handler.go:65 +0x184 > k8s.io/client-go/rest.handleWarnings(0x14000bd61e0?, {0x102c6c340?, 0x1400080ac60?}) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/warnings.go:144 +0xd8 > k8s.io/client-go/rest.(*Request).transformResponse(0x14000f58240, 0x140000af710, 0x14000f58360) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1179 +0x2d0 > k8s.io/client-go/rest.(*Request).Do.func1(0x1400098fb80?, 0xa?) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1064 +0x34 > k8s.io/client-go/rest.(*Request).request.func3.1(...) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1039 > k8s.io/client-go/rest.(*Request).request.func3(0x140000af710, 0x14000055c60, {0x102c86fa8?, 0x1400098fb80?}, 0x140000af710?, 0x0?, 0x14000f58360, {0x0?, 0x0?}, 0x14000083b08?) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1046 +0xc0 > k8s.io/client-go/rest.(*Request).request(0x14000f58240, {0x102c86830, 0x103b74e40}, 0x14000055c60) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1048 +0x3a0 > k8s.io/client-go/rest.(*Request).Do(0x14000f58240, {0x102c86830, 0x103b74e40}) > /Users/tzifudzi/go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1063 +0x8c > sigs.k8s.io/controller-runtime/pkg/client.(*typedClient).Delete(0x1400077def0?, {0x102c86830, 0x103b74e40}, {0x102c9a2f8?, 0x140006b2508?}, {0x0, 0x0, 0x100f32fd4?}) > /Users/tzifudzi/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/client/typed_client.go:87 +0x30c > sigs.k8s.io/controller-runtime/pkg/client.(*client).Delete(0x1400077def0?, {0x102c86830?, 0x103b74e40?}, {0x102c9a2f8?, 0x140006b2508?}, {0x0?, 0x0?, 0x0?}) > /Users/tzifudzi/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/client/client.go:321 +0x8c > github.com/aws/amazon-vpc-resource-controller-k8s/test/framework/resource/k8s/jobs.(*defaultManager).DeleteAndWaitTillJobIsDeleted(0x14000aac030, {0x102c86830, 0x103b74e40}, 0x140006b2508) > /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/framework/resource/k8s/jobs/manager.go:103 +0x58 > github.com/aws/amazon-vpc-resource-controller-k8s/test/integration/windows_test.init.func4.7.3() > /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:927 +0x48 > github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x14000913fa8?, 0x1013dc664?}) > /Users/tzifudzi/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/node.go:472 +0x24 > github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() > /Users/tzifudzi/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/suite.go:894 +0x88 > created by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 13 > /Users/tzifudzi/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/suite.go:881 +0xaf8 • [202.424 seconds] ------------------------------ Windows Integration Test [CANARY] windows connectivity tests when creating window job to connect to unreachable port all jobs should fail /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:957 STEP: updating the configmap @ 07/23/24 08:29:31.186 • [144.188 seconds] ------------------------------ Windows Integration Test [CANARY] windows connectivity tests when connecting to internet should connect /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:969 STEP: updating the configmap @ 07/23/24 08:31:55.38 • [78.216 seconds] ------------------------------ Windows Integration Test [CANARY] windows connectivity tests when connecting to invalid url should fail to connect /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:982 STEP: updating the configmap @ 07/23/24 08:33:13.613 • [74.265 seconds] ------------------------------ Windows Integration Test [CANARY] windows service tests when a deployment behind lb service is created load balancer service pods should be reachable /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1061 STEP: creating a deployment running a web server @ 07/23/24 08:34:27.882 STEP: creating a service of type LoadBalancer @ 07/23/24 08:36:21.928 STEP: creating testers to connect to service windows-service-loadbalancer on 10.100.140.230 on 80 @ 07/23/24 08:38:23.95 • [432.714 seconds] ------------------------------ Windows Integration Test [CANARY] windows service tests when a deployment behind cluster ip is created clusterIP service pods should be reachable /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1070 STEP: creating a deployment running a web server @ 07/23/24 08:41:40.574 STEP: creating a service of type ClusterIP @ 07/23/24 08:43:34.604 STEP: creating testers to connect to service windows-service-clusterip on 10.100.49.207 on 80 @ 07/23/24 08:44:07.243 • [311.372 seconds] ------------------------------ Windows Integration Test [CANARY] windows service tests when a deployment behind cluster ip is created nodeport service pods should be reachable /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1079 STEP: creating a deployment running a web server @ 07/23/24 08:46:51.906 STEP: creating a service of type NodePort @ 07/23/24 08:48:45.937 STEP: creating testers to connect to service windows-service-nodeport on 10.100.49.86 on 80 @ 07/23/24 08:49:17.992 • [314.815 seconds] ------------------------------ Windows Integration Test when creating pod with same namespace and name should successfully run the pod each time /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1090 STEP: run # 0: creating pod with same ns/name @ 07/23/24 08:52:06.717 STEP: run # 1: creating pod with same ns/name @ 07/23/24 08:53:09.82 STEP: run # 2: creating pod with same ns/name @ 07/23/24 08:54:12.988 STEP: run # 3: creating pod with same ns/name @ 07/23/24 08:55:16.082 STEP: run # 4: creating pod with same ns/name @ 07/23/24 08:56:19.215 • [305.706 seconds] ------------------------------ Windows Integration Test windows deployment tests creating a deployment multiple times deployment should be ready each time /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1110 STEP: run # 0: creating the deployment @ 07/23/24 08:57:12.421 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.452 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 08:59:32.453 STEP: run # 1: creating the deployment @ 07/23/24 08:59:34.983 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.033 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.033 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.033 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.033 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.034 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:01:55.036 STEP: run # 2: creating the deployment @ 07/23/24 09:01:57.077 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.125 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:04:17.126 STEP: run # 3: creating the deployment @ 07/23/24 09:04:19.158 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.19 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.191 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.192 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.193 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.193 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.193 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.193 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:06:39.194 STEP: run # 4: creating the deployment @ 07/23/24 09:06:41.238 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.267 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 STEP: matching the IPv4 from annotation to the pod IP @ 07/23/24 09:09:01.268 • [732.967 seconds] ------------------------------ [AfterSuite] /Users/tzifudzi/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_suite_test.go:89 STEP: updating the configmap @ 07/23/24 09:09:25.345 STEP: revoking the security group ingress for HTTP traffic @ 07/23/24 09:09:35.368 [AfterSuite] PASSED [10.677 seconds] ------------------------------ Ran 34 of 40 Specs in 6833.774 seconds SUCCESS! -- 34 Passed | 0 Failed | 0 Pending | 6 Skipped PASS Ginkgo ran 1 suite in 1h53m59.630180542s Test Suite Passed [tzifudzi:~/GolandProjects/amazon-vpc-resource-controller-k8s/test/integration/windows] feature/secondary-ip-configs(+11/-15,1)+* 1h54m0s ±