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 ·[38;5;243m@ 08/29/24 05:45:52.174 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:45:52.174 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [71.174 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active ·[38;5;243mWhen 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 ·[38;5;204m[windows-prefix-delegation-disabled, windows-minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:339 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:46:07.191 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:46:07.191 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:46:07.191 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 ·[38;5;243m@ 08/29/24 05:46:57.201 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:47:54.28 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:47:54.28 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:47:54.28 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:48:11.481 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:48:11.481 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [139.310 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active ·[38;5;243mWhen 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 ·[38;5;204m[windows-prefix-delegation-disabled, windows-minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:375 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:48:26.502 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:48:26.502 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:48:26.502 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 ·[38;5;243m@ 08/29/24 05:49:23.217 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:49:23.217 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [71.733 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active ·[38;5;243mWhen 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 ·[38;5;204m[windows-prefix-delegation-disabled, windows-minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:388 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:49:38.232 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:49:38.232 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:49:38.232 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 ·[38;5;243m@ 08/29/24 05:50:34.376 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:50:34.376 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [71.159 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active ·[38;5;243mWhen 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 ·[38;5;204m[windows-prefix-delegation-disabled, windows-minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:400 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:50:49.393 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:50:49.393 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:50:49.393 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 ·[38;5;243m@ 08/29/24 05:51:39.399 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:52:17.447 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:52:17.447 Waiting 5 seconds for warmpool to reconciliate after creating new pod(s)... STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:52:32.629 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:52:32.629 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [118.251 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap secondary IP mode tests when prefix delegation is disabled and secondary IP mode is active ·[38;5;243mWhen windows-warm-ip-target and windows-min-ip-target set to 0 should result in warm-ip-target=1 and min-ip-target=0 ·[38;5;204m[windows-prefix-delegation-disabled, windows-warm-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:432 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:52:47.644 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:52:47.644 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:52:47.644 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 ·[38;5;243m@ 08/29/24 05:53:43.792 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:53:43.792 Updated amazon-vpc-cni config map data: map[enable-windows-ipam:true enable-windows-prefix-delegation:false] Waiting 5 seconds for pool reconciliation... ·[38;5;10m• [71.165 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243m[CANARY] When enable-windows-prefix-delegation is true pod should be running and assigned ips are from prefix ·[38;5;204m[windows-prefix-delegation] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:520 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:53:58.8 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:53:58.808 STEP: creating pod and waiting for ready ·[38;5;243m@ 08/29/24 05:54:08.815 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:54:27.948 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:54:29.966 ·[38;5;10m• [47.185 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen warm-prefix-target is set to 2 two prefixes should be assigned ·[38;5;204m[windows-prefix-delegation, warm-prefix-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:545 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:54:45.985 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:54:45.994 STEP: creating pod and waiting for ready should have 1 new prefix assigned ·[38;5;243m@ 08/29/24 05:55:26.122 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:55:45.147 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:55:47.354 ·[38;5;10m• [77.384 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen warm-ip-target is set to 15 should assign new prefix when 2nd pod is launched ·[38;5;204m[windows-prefix-delegation, warm-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:576 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:56:03.369 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:56:03.378 STEP: creating 1 pod and waiting for ready should not create new prefix ·[38;5;243m@ 08/29/24 05:56:43.504 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:57:02.6 STEP: creating 2nd pod and waiting for ready should have 1 more prefix assigned ·[38;5;243m@ 08/29/24 05:57:02.6 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 05:57:21.724 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:57:25.78 ·[38;5;10m• [98.426 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen minimum-ip-target is set to 20 should have 2 prefixes to satisfy minimum-ip-target when no pods running ·[38;5;204m[windows-prefix-delegation, minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:623 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 05:57:41.795 STEP: updating the configmap ·[38;5;243m@ 08/29/24 05:57:41.803 STEP: adding labels to selected nodes for testing ·[38;5;243m@ 08/29/24 05:57:51.81 STEP: creating 33 pods and waiting for ready should have 3 prefixes attached ·[38;5;243m@ 08/29/24 05:58:21.937 STEP: deleting 33 pods should still have 2 prefixes attached ·[38;5;243m@ 08/29/24 05:59:34.083 STEP: removing labels on selected nodes for testing ·[38;5;243m@ 08/29/24 06:00:36.206 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:00:36.231 ·[38;5;10m• [192.455 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen windows-warm-prefix-target is set to 2 two prefixes should be assigned ·[38;5;204m[windows-prefix-delegation, windows-warm-prefix-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:678 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:00:54.25 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:00:54.257 STEP: creating pod and waiting for ready should have 1 new prefix assigned ·[38;5;243m@ 08/29/24 06:01:34.329 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:01:53.357 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:01:55.553 ·[38;5;10m• [77.320 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen windows-warm-ip-target is set to 15 should assign new prefix when 2nd pod is launched ·[38;5;204m[windows-prefix-delegation, windows-warm-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:708 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:02:11.57 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:02:11.579 STEP: creating 1 pod and waiting for ready should not create new prefix ·[38;5;243m@ 08/29/24 06:02:51.718 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:03:10.791 STEP: creating 2nd pod and waiting for ready should have 1 more prefix assigned ·[38;5;243m@ 08/29/24 06:03:10.791 STEP: matching the prefix-deconstructed IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:03:29.928 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:03:34.552 ·[38;5;10m• [98.996 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen windows-minimum-ip-target is set to 20 should have 2 prefixes to satisfy windows-minimum-ip-target when no pods running ·[38;5;204m[windows-prefix-delegation, windows-minimum-ip-target] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:754 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:03:50.566 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:03:50.579 STEP: adding labels to selected nodes for testing ·[38;5;243m@ 08/29/24 06:04:00.586 STEP: creating 33 pods and waiting for ready should have 3 prefixes attached ·[38;5;243m@ 08/29/24 06:04:30.736 STEP: deleting 33 pods should still have 2 prefixes attached ·[38;5;243m@ 08/29/24 06:05:40.88 STEP: removing labels on selected nodes for testing ·[38;5;243m@ 08/29/24 06:06:43.019 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:06:43.038 ·[38;5;10m• [190.487 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243m[CANARY] When enable-windows-prefix-delegation is toggled to false prefixes should be released ·[38;5;204m[windows-prefix-delegation] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:807 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:07:01.053 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:07:01.063 STEP: creating pod and waiting for ready should have secondary IP assigned ·[38;5;243m@ 08/29/24 06:07:41.191 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:08:00.222 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:08:19.237 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:08:19.352 ·[38;5;10m• [94.312 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen enable-windows-prefix-delegation is incorrect pod should be running with secondary ip assigned and not prefix ip ·[38;5;204m[windows-prefix-delegation] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:842 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:08:35.366 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:08:35.376 STEP: creating pod and waiting for ready ·[38;5;243m@ 08/29/24 06:08:45.384 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:09:04.408 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:09:04.409 ·[38;5;10m• [45.059 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mWhen PD flag present but IPAM flag is missing pod should not be running and should not have resource limits ·[38;5;204m[windows-prefix-delegation] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:855 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:09:20.425 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:09:20.434 STEP: creating pod and waiting for timeout ·[38;5;243m@ 08/29/24 06:09:30.441 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:13:35.46 ·[38;5;10m• [271.050 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mconfigMap enable-windows-prefix-delegation tests when prefix delegation is enabled ·[38;5;243mwhen enable-windows-prefix-delegation is set to true but old controller deployment exists pod should fail to create ·[38;5;204m[windows-prefix-delegation] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:870 STEP: checking nodes have capacity present ·[38;5;243m@ 08/29/24 06:13:51.475 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:13:51.486 STEP: creating a dummy deployment for vpc-resource-controller ·[38;5;243m@ 08/29/24 06:14:01.493 STEP: creating windows pod and waiting for it to timeout ·[38;5;243m@ 08/29/24 06:14:09.507 STEP: deleting the old controller dummy deployment ·[38;5;243m@ 08/29/24 06:18:16.544 STEP: creating windows pod and waiting for it to run ·[38;5;243m@ 08/29/24 06:18:18.554 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:18:37.58 ·[38;5;10m• [302.121 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows connectivity tests when multiples jobs are created that try connect to a service all job should complete ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:940 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:18:53.705 STEP: verifying the job has same IPv4 Address as allocated by the controller ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.726 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:20:27.727 [controller-runtime] log.SetLogger(...) was never called; logs will not be displayed. Detected at: > goroutine 821 [running]: > runtime/debug.Stack() > /root/.goenv/versions/1.21.11/src/runtime/debug/stack.go:24 +0x5e > sigs.k8s.io/controller-runtime/pkg/log.eventuallyFulfillRoot() > /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/log.go:60 +0xcd > sigs.k8s.io/controller-runtime/pkg/log.(*delegatingLogSink).Enabled(0xc0006584c0, 0x700000000000000?) > /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/deleg.go:111 +0x32 > github.com/go-logr/logr.Logger.Info({{0x211e1b8?, 0xc0006584c0?}, 0xc00054a600?}, {0xc00054a600, 0xa3}, {0x0, 0x0, 0x0}) > /go/pkg/mod/github.com/go-logr/logr@v1.4.2/logr.go:276 +0x72 > sigs.k8s.io/controller-runtime/pkg/log.(*KubeAPIWarningLogger).HandleWarningHeader(0xc0006ab5c0?, 0x1?, {0x1b7d336?, 0x7?}, {0xc00054a600?, 0xa3?}) > /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/log/warning_handler.go:65 +0x167 > k8s.io/client-go/rest.handleWarnings(0xc000e9d440?, {0x2100be0?, 0xc0006ab5c0?}) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/warnings.go:144 +0xef > k8s.io/client-go/rest.(*Request).transformResponse(0xc000dc7e60, 0xc000d4d8c0, 0xc000c86100) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1179 +0x5c8 > k8s.io/client-go/rest.(*Request).Do.func1(0xc00100dd80?, 0x0?) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1064 +0x31 > k8s.io/client-go/rest.(*Request).request.func3.1(...) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1039 > k8s.io/client-go/rest.(*Request).request.func3(0xc000d4d8c0, 0xc000a4fc48, {0x211b4a8?, 0xc00100dd80?}, 0x0?, 0x0?, 0x0?, {0x0?, 0x0?}, 0x1c9c868) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1046 +0xd7 > k8s.io/client-go/rest.(*Request).request(0xc000dc7e60, {0x211ad30, 0x2fd0d20}, 0x0?) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1048 +0x4ed > k8s.io/client-go/rest.(*Request).Do(0xc000dc7e60, {0x211ad30, 0x2fd0d20}) > /go/pkg/mod/k8s.io/client-go@v0.29.3/rest/request.go:1063 +0xb0 > sigs.k8s.io/controller-runtime/pkg/client.(*typedClient).Delete(0x8?, {0x211ad30, 0x2fd0d20}, {0x212fe38?, 0xc0000cd900}, {0x0, 0x0, 0x8e98b9?}) > /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/client/typed_client.go:87 +0x35d > sigs.k8s.io/controller-runtime/pkg/client.(*client).Delete(0xc0000e43f0?, {0x211ad30?, 0x2fd0d20?}, {0x212fe38?, 0xc0000cd900?}, {0x0?, 0x0?, 0x0?}) > /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.0/pkg/client/client.go:321 +0x10a > github.com/aws/amazon-vpc-resource-controller-k8s/test/framework/resource/k8s/jobs.(*defaultManager).DeleteAndWaitTillJobIsDeleted(0xc000752fa0, {0x211ad30, 0x2fd0d20}, 0xc0000cd900) > /codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/framework/resource/k8s/jobs/manager.go:103 +0x5d > github.com/aws/amazon-vpc-resource-controller-k8s/test/integration/windows_test.glob..func4.7.3() > /codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:927 +0x42 > github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x8ef2e8, 0xc0008ce300}) > /go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/node.go:472 +0x13 > github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() > /go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/suite.go:894 +0x8d > created by github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 16 > /go/pkg/mod/github.com/onsi/ginkgo/v2@v2.19.0/internal/suite.go:881 +0xddb ·[38;5;10m• [108.639 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows connectivity tests when creating window job to connect to unreachable port all jobs should fail ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:957 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:20:42.245 ·[38;5;10m• [134.085 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows connectivity tests when connecting to internet should connect ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:969 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:22:56.328 ·[38;5;10m• [68.193 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows connectivity tests when connecting to invalid url should fail to connect ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:982 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:24:04.522 ·[38;5;10m• [74.114 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows service tests when a deployment behind lb service is created load balancer service pods should be reachable ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1061 STEP: creating a deployment running a web server ·[38;5;243m@ 08/29/24 06:25:18.639 STEP: creating a service of type LoadBalancer ·[38;5;243m@ 08/29/24 06:25:52.657 STEP: creating testers to connect to service windows-service-loadbalancer on 10.100.175.165 on 80 ·[38;5;243m@ 08/29/24 06:27:54.68 ·[38;5;10m• [260.276 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows service tests when a deployment behind cluster ip is created clusterIP service pods should be reachable ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1070 STEP: creating a deployment running a web server ·[38;5;243m@ 08/29/24 06:29:38.914 STEP: creating a service of type ClusterIP ·[38;5;243m@ 08/29/24 06:30:12.921 STEP: creating testers to connect to service windows-service-clusterip on 10.100.84.60 on 80 ·[38;5;243m@ 08/29/24 06:30:44.941 ·[38;5;10m• [150.806 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243m[CANARY] windows service tests when a deployment behind cluster ip is created nodeport service pods should be reachable ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1079 STEP: creating a deployment running a web server ·[38;5;243m@ 08/29/24 06:32:09.719 STEP: creating a service of type NodePort ·[38;5;243m@ 08/29/24 06:32:43.728 STEP: creating testers to connect to service windows-service-nodeport on 10.100.61.24 on 80 ·[38;5;243m@ 08/29/24 06:33:15.763 ·[38;5;10m• [148.270 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mwhen creating pod with same namespace and name should successfully run the pod each time ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1090 STEP: run # 0: creating pod with same ns/name ·[38;5;243m@ 08/29/24 06:34:37.99 STEP: run # 1: creating pod with same ns/name ·[38;5;243m@ 08/29/24 06:35:21.043 STEP: run # 2: creating pod with same ns/name ·[38;5;243m@ 08/29/24 06:36:04.092 STEP: run # 3: creating pod with same ns/name ·[38;5;243m@ 08/29/24 06:36:47.131 STEP: run # 4: creating pod with same ns/name ·[38;5;243m@ 08/29/24 06:37:18.171 ·[38;5;10m• [209.234 seconds] ·[38;5;243m------------------------------ Windows Integration Test ·[38;5;243mwindows deployment tests creating a deployment multiple times deployment should be ready each time ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_test.go:1110 STEP: run # 0: creating the deployment ·[38;5;243m@ 08/29/24 06:38:07.231 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:38:47.242 STEP: run # 1: creating the deployment ·[38;5;243m@ 08/29/24 06:38:49.252 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:39:29.263 STEP: run # 2: creating the deployment ·[38;5;243m@ 08/29/24 06:39:31.271 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:13.282 STEP: run # 3: creating the deployment ·[38;5;243m@ 08/29/24 06:40:15.29 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.302 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:40:55.303 STEP: run # 4: creating the deployment ·[38;5;243m@ 08/29/24 06:40:57.311 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.325 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 STEP: matching the IPv4 from annotation to the pod IP ·[38;5;243m@ 08/29/24 06:41:37.326 ·[38;5;10m• [230.133 seconds] ·[38;5;243m------------------------------ ·[38;5;14mS·[38;5;14mS·[38;5;14mS·[38;5;14mS·[38;5;14mS·[38;5;14mS ·[38;5;243m------------------------------ [AfterSuite] ·[38;5;243m/codebuild/output/src1677917187/src/github.com/tzifudzi/amazon-vpc-resource-controller-k8s/test/integration/windows/windows_suite_test.go:89 STEP: updating the configmap ·[38;5;243m@ 08/29/24 06:41:57.347 STEP: revoking the security group ingress for HTTP traffic ·[38;5;243m@ 08/29/24 06:42:07.355 ·[38;5;10m[AfterSuite] PASSED [10.233 seconds] ·[38;5;243m------------------------------ ·[38;5;10mRan 34 of 40 Specs in 4898.371 seconds ·[38;5;10mSUCCESS! -- ·[38;5;10m34 Passed | ·[38;5;9m0 Failed | ·[38;5;11m0 Pending | ·[38;5;14m6 Skipped PASS Ginkgo ran 1 suite in 1h22m15.795687635s Test Suite Passed [Container] 2024/08/29 06:42:07.594208 Phase complete: BUILD State: SUCCEEDED [Container] 2024/08/29 06:42:07.594229 Phase context status code: Message: [Container] 2024/08/29 06:42:07.628690 Entering phase POST_BUILD [Container] 2024/08/29 06:42:07.629435 Running command echo "Windows Integration Tests completed" Windows Integration Tests completed [Container] 2024/08/29 06:42:07.635951 Phase complete: POST_BUILD State: SUCCEEDED [Container] 2024/08/29 06:42:07.635986 Phase context status code: Message: [Container] 2024/08/29 06:42:07.678347 Set report auto-discover timeout to 5 seconds [Container] 2024/08/29 06:42:07.678388 Expanding base directory path: . [Container] 2024/08/29 06:42:07.681476 Assembling file list [Container] 2024/08/29 06:42:07.681490 Expanding . [Container] 2024/08/29 06:42:07.684591 Expanding file paths for base directory . [Container] 2024/08/29 06:42:07.684602 Assembling file list [Container] 2024/08/29 06:42:07.684605 Expanding **/* [Container] 2024/08/29 06:42:07.689157 No matching auto-discover report paths found [Container] 2024/08/29 06:42:07.689184 Report auto-discover file discovery took 0.010837 seconds [Container] 2024/08/29 06:42:07.689207 Phase complete: UPLOAD_ARTIFACTS State: SUCCEEDED [Container] 2024/08/29 06:42:07.689215 Phase context status code: Message: