Recent runs || View in Spyglass
PR | lzhecheng: [e2e] Support dual-stack - ensureloadbalancer & nsg |
Result | FAILURE |
Tests | 2 failed / 44 succeeded |
Started | |
Elapsed | 2h57m |
Revision | 042f5f6fb86efd5c1e0888f11dd544fffe7590e0 |
Refs |
3268 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\s\[It\]\sNetwork\ssecurity\sgroup\sshould\sadd\sthe\srule\swhen\sexpose\sa\sservice\s\[NSG\]$'
[FAILED] Security rule for service nsg-test not exists Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:104 @ 02/01/23 14:30:00.847 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:25:12.021 Feb 1 14:25:12.021: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:25:12.021: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:25:12.128: INFO: Created a test namespace "e2e-tests-nsg-c2qcn" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:110] Feb 1 14:25:12.128: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:25:12.128: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:25:12.266: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:25:12.266: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig cluster-info dump | grep service-cluster-ip-range' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:25:18.235: INFO: Creating deployment nsg-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:69] Feb 1 14:25:18.343: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:74] Feb 1 14:25:18.469: INFO: 5 pods in namespace e2e-tests-nsg-c2qcn are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] Feb 1 14:25:28.609: INFO: 0 pods in namespace e2e-tests-nsg-c2qcn are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] < Exit [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:25:28.609 (16.587s) > Enter [It] should add the rule when expose a service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:91 @ 02/01/23 14:25:28.609 STEP: Creating a service and expose it - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:92 @ 02/01/23 14:25:28.609 Feb 1 14:25:28.609: INFO: Creating service nsg-test in namespace e2e-tests-nsg-c2qcn [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1219] Feb 1 14:25:28.753: INFO: Successfully created LoadBalancer service nsg-test in namespace e2e-tests-nsg-c2qcn [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1223] Feb 1 14:25:28.753: INFO: Waiting service to expose... [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1226] Feb 1 14:25:28.856: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:25:38.959: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:25:48.966: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:25:58.967: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:26:08.965: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:26:18.958: INFO: Exposure successfully, get external ip: [51.142.210.71] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:26:18.958: INFO: Creating a hostNetwork Pod exec-agnhost-pod in namespace e2e-tests-nsg-c2qcn to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:26:18.958: INFO: creating pod exec-agnhost-pod in namespace e2e-tests-nsg-c2qcn [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:26:19.174: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] Feb 1 14:26:29.289: INFO: checking the connectivity of address 51.142.210.71 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:133] Feb 1 14:26:29.289: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:26:29.289: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-c2qcn exec exec-agnhost-pod -- /bin/sh -x -c nc -vz -w 4 51.142.210.71 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:26:30.443: INFO: stderr: "+ nc -vz -w 4 51.142.210.71 80\nConnection to 51.142.210.71 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:26:30.443: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:26:30.443: INFO: Validation succeeded: Service addr 51.142.210.71 and port 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:26:30.561: INFO: Deleting pod exec-agnhost-pod in namespace e2e-tests-nsg-c2qcn [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] STEP: Validating ip exists in Security Group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:100 @ 02/01/23 14:26:30.663 Feb 1 14:26:30.663: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:26:31.553: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] Feb 1 14:26:31.553: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:372] Feb 1 14:26:31.553: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:372] STEP: Cleaning up - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:95 @ 02/01/23 14:26:31.553 Feb 1 14:26:31.553: INFO: Deleting service "nsg-test" in namespace "e2e-tests-nsg-c2qcn" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:47] [FAILED] Failure recorded during attempt 1: Security rule for service nsg-test not exists Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:104 @ 02/01/23 14:27:31.865 < Exit [It] should add the rule when expose a service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:91 @ 02/01/23 14:27:31.865 (2m3.256s) > Enter [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:27:31.865 Feb 1 14:27:31.971: INFO: Deleting namespace e2e-tests-nsg-c2qcn [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:135] < Exit [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:27:38.28 (6.415s) Attempt #1 Failed. Retrying ↺ @ 02/01/23 14:27:38.28 > Enter [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:27:38.28 Feb 1 14:27:38.280: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:27:38.280: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:27:38.386: INFO: Created a test namespace "e2e-tests-nsg-26mkw" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:110] Feb 1 14:27:38.386: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:27:38.387: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:27:38.526: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:27:38.526: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig cluster-info dump | grep service-cluster-ip-range' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:27:44.593: INFO: Creating deployment nsg-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:69] Feb 1 14:27:44.698: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:74] Feb 1 14:27:44.829: INFO: 5 pods in namespace e2e-tests-nsg-26mkw are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] Feb 1 14:27:54.968: INFO: 0 pods in namespace e2e-tests-nsg-26mkw are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] < Exit [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:27:54.968 (16.688s) > Enter [It] should add the rule when expose a service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:91 @ 02/01/23 14:27:54.968 STEP: Creating a service and expose it - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:92 @ 02/01/23 14:27:54.968 Feb 1 14:27:54.969: INFO: Creating service nsg-test in namespace e2e-tests-nsg-26mkw [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1219] Feb 1 14:27:55.083: INFO: Successfully created LoadBalancer service nsg-test in namespace e2e-tests-nsg-26mkw [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1223] Feb 1 14:27:55.083: INFO: Waiting service to expose... [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:1226] Feb 1 14:27:55.186: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:05.289: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:15.299: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:25.289: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:35.300: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:45.289: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:28:55.299: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:29:05.293: INFO: Exposure successfully, get external ip: [51.142.211.137] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:29:05.293: INFO: Creating a hostNetwork Pod exec-agnhost-pod in namespace e2e-tests-nsg-26mkw to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:29:05.293: INFO: creating pod exec-agnhost-pod in namespace e2e-tests-nsg-26mkw [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:29:05.509: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] Feb 1 14:29:15.616: INFO: checking the connectivity of address 51.142.211.137 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:133] Feb 1 14:29:15.616: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:29:15.616: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-26mkw exec exec-agnhost-pod -- /bin/sh -x -c nc -vz -w 4 51.142.211.137 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:29:16.768: INFO: stderr: "+ nc -vz -w 4 51.142.211.137 80\nConnection to 51.142.211.137 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:29:16.769: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:29:16.769: INFO: Validation succeeded: Service addr 51.142.211.137 and port 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:29:16.886: INFO: Deleting pod exec-agnhost-pod in namespace e2e-tests-nsg-26mkw [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] STEP: Validating ip exists in Security Group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:100 @ 02/01/23 14:29:16.988 Feb 1 14:29:16.989: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:29:18.314: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] Feb 1 14:29:18.314: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:372] Feb 1 14:29:18.314: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:372] STEP: Cleaning up - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:95 @ 02/01/23 14:29:18.314 Feb 1 14:29:18.314: INFO: Deleting service "nsg-test" in namespace "e2e-tests-nsg-26mkw" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:47] [FAILED] Security rule for service nsg-test not exists Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:104 @ 02/01/23 14:30:00.847 < Exit [It] should add the rule when expose a service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:91 @ 02/01/23 14:30:00.847 (2m5.879s) > Enter [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:30:00.847 Feb 1 14:30:00.970: INFO: Deleting namespace e2e-tests-nsg-26mkw [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:135] < Exit [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:30:07.281 (6.434s)
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\s\[It\]\sNetwork\ssecurity\sgroup\sshould\ssupport\sservice\sannotation\s\`service\.beta\.kubernetes\.io\/azure\-deny\-all\-except\-load\-balancer\-source\-ranges\`\s\[NSG\]$'
[FAILED] Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:296 @ 02/01/23 14:45:01.478 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:36:15.398 Feb 1 14:36:15.398: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:36:15.398: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:36:15.505: INFO: Created a test namespace "e2e-tests-nsg-7knbg" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:110] Feb 1 14:36:15.505: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:36:15.505: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:36:15.646: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:36:15.646: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig cluster-info dump | grep service-cluster-ip-range' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:36:21.640: INFO: Creating deployment nsg-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:69] Feb 1 14:36:21.745: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:74] Feb 1 14:36:21.874: INFO: 5 pods in namespace e2e-tests-nsg-7knbg are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] Feb 1 14:36:32.015: INFO: 0 pods in namespace e2e-tests-nsg-7knbg are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] < Exit [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:36:32.015 (16.616s) > Enter [It] should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:227 @ 02/01/23 14:36:32.015 STEP: Creating a test service with the deny rule annotation but without `service.Spec.LoadBalancerSourceRanges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:228 @ 02/01/23 14:36:32.015 STEP: Waiting for the service to expose - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:237 @ 02/01/23 14:36:32.134 Feb 1 14:36:32.236: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:36:42.344: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:36:52.345: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:02.348: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:12.346: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:22.347: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:32.346: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:42.345: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:37:52.348: INFO: Exposure successfully, get external ip: [10.1.0.6] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:37:52.348: INFO: Creating a hostNetwork Pod exec-agnhost-pod in namespace e2e-tests-nsg-7knbg to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:37:52.348: INFO: creating pod exec-agnhost-pod in namespace e2e-tests-nsg-7knbg [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:37:52.565: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] Feb 1 14:38:02.680: INFO: checking the connectivity of address 10.1.0.6 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:133] Feb 1 14:38:02.680: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:38:02.680: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-7knbg exec exec-agnhost-pod -- /bin/sh -x -c nc -vz -w 4 10.1.0.6 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:38:03.863: INFO: stderr: "+ nc -vz -w 4 10.1.0.6 80\nConnection to 10.1.0.6 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:38:03.863: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:38:03.863: INFO: Validation succeeded: Service addr 10.1.0.6 and port 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:38:03.981: INFO: Deleting pod exec-agnhost-pod in namespace e2e-tests-nsg-7knbg [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] STEP: Checking if there is a deny_all rule - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:241 @ 02/01/23 14:38:04.082 Feb 1 14:38:04.082: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:38:04.968: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] Feb 1 14:38:04.968: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:455] Feb 1 14:38:04.968: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:455] STEP: Deleting the service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:247 @ 02/01/23 14:38:04.968 Feb 1 14:38:04.968: INFO: Deleting service "nsg-test" in namespace "e2e-tests-nsg-7knbg" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:47] STEP: Creating a test service with the deny rule annotation and `service.Spec.LoadBalancerSourceRanges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:251 @ 02/01/23 14:38:41.278 Feb 1 14:38:41.278: INFO: Creating a hostNetwork Pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-7knbg to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:38:41.278: INFO: creating pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-7knbg [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:38:41.493: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] STEP: Waiting for the service to expose - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:281 @ 02/01/23 14:38:51.824 Feb 1 14:38:51.926: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:02.034: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:12.029: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:22.036: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:32.028: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:42.033: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:39:52.042: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:40:02.029: INFO: Exposure successfully, get external ip: [10.1.0.6] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:40:02.029: INFO: checking the connectivity of addr 10.1.0.6:80 with protocol [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:286] Feb 1 14:40:02.029: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:40:02.029: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-7knbg exec exec-agnhost-pod-deny-all-except-lb-range -- /bin/sh -x -c nc -vz -w 4 10.1.0.6 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:40:03.183: INFO: stderr: "+ nc -vz -w 4 10.1.0.6 80\nConnection to 10.1.0.6 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:40:03.183: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:40:03.183: INFO: Validation succeeded: Service addr 10.1.0.6 and port 80 with protocol [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:40:03.183: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:40:03.761: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] STEP: Checking if there is a LoadBalancerSourceRanges rule - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:294 @ 02/01/23 14:40:03.761 Feb 1 14:40:03.761: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:423] Feb 1 14:40:03.761: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:423] Feb 1 14:40:03.878: INFO: Deleting pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-7knbg [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] [FAILED] Failure recorded during attempt 1: Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:296 @ 02/01/23 14:40:03.993 < Exit [It] should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:227 @ 02/01/23 14:40:03.993 (3m31.979s) > Enter [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:40:03.993 Feb 1 14:40:04.098: INFO: Deleting namespace e2e-tests-nsg-7knbg [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:135] < Exit [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:41:12.407 (1m8.414s) Attempt #1 Failed. Retrying ↺ @ 02/01/23 14:41:12.407 > Enter [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:41:12.407 Feb 1 14:41:12.408: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:41:12.408: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:41:12.512: INFO: Created a test namespace "e2e-tests-nsg-697wp" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:110] Feb 1 14:41:12.512: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:56] Feb 1 14:41:12.512: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:64] Feb 1 14:41:12.650: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:41:12.650: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig cluster-info dump | grep service-cluster-ip-range' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:41:18.691: INFO: Creating deployment nsg-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:69] Feb 1 14:41:18.798: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:74] Feb 1 14:41:18.927: INFO: 5 pods in namespace e2e-tests-nsg-697wp are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] Feb 1 14:41:29.064: INFO: 0 pods in namespace e2e-tests-nsg-697wp are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:87] < Exit [BeforeEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:58 @ 02/01/23 14:41:29.065 (16.657s) > Enter [It] should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:227 @ 02/01/23 14:41:29.065 STEP: Creating a test service with the deny rule annotation but without `service.Spec.LoadBalancerSourceRanges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:228 @ 02/01/23 14:41:29.065 STEP: Waiting for the service to expose - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:237 @ 02/01/23 14:41:29.194 Feb 1 14:41:29.297: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:41:39.400: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:41:49.401: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:41:59.404: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:42:09.409: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:42:19.404: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:42:29.401: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:42:39.401: INFO: Exposure successfully, get external ip: [10.1.0.6] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:42:39.401: INFO: Creating a hostNetwork Pod exec-agnhost-pod in namespace e2e-tests-nsg-697wp to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:42:39.401: INFO: creating pod exec-agnhost-pod in namespace e2e-tests-nsg-697wp [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:42:39.616: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] Feb 1 14:42:49.729: INFO: checking the connectivity of address 10.1.0.6 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:133] Feb 1 14:42:49.729: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:42:49.729: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-697wp exec exec-agnhost-pod -- /bin/sh -x -c nc -vz -w 4 10.1.0.6 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:42:50.869: INFO: stderr: "+ nc -vz -w 4 10.1.0.6 80\nConnection to 10.1.0.6 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:42:50.869: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:42:50.869: INFO: Validation succeeded: Service addr 10.1.0.6 and port 80 with protocol TCP [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:42:50.990: INFO: Deleting pod exec-agnhost-pod in namespace e2e-tests-nsg-697wp [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] STEP: Checking if there is a deny_all rule - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:241 @ 02/01/23 14:42:51.091 Feb 1 14:42:51.091: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:42:52.086: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] Feb 1 14:42:52.086: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:455] Feb 1 14:42:52.086: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:455] STEP: Deleting the service - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:247 @ 02/01/23 14:42:52.086 Feb 1 14:42:52.086: INFO: Deleting service "nsg-test" in namespace "e2e-tests-nsg-697wp" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:47] STEP: Creating a test service with the deny rule annotation and `service.Spec.LoadBalancerSourceRanges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:251 @ 02/01/23 14:43:38.396 Feb 1 14:43:38.396: INFO: Creating a hostNetwork Pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-697wp to exec [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:159] Feb 1 14:43:38.396: INFO: creating pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-697wp [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:152] Feb 1 14:43:38.608: INFO: waiting for the pod status to be Running, current status: Pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:317] STEP: Waiting for the service to expose - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:281 @ 02/01/23 14:43:48.936 Feb 1 14:43:49.038: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:43:59.140: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:09.140: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:19.148: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:29.145: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:39.148: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:49.150: INFO: Fail to find ingress, retry in 10 seconds [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:169] Feb 1 14:44:59.141: INFO: Exposure successfully, get external ip: [10.1.0.6] [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:189] Feb 1 14:44:59.141: INFO: checking the connectivity of addr 10.1.0.6:80 with protocol [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:286] Feb 1 14:44:59.141: INFO: Kubernetes configuration file name: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:107] Feb 1 14:44:59.141: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig --namespace=e2e-tests-nsg-697wp exec exec-agnhost-pod-deny-all-except-lb-range -- /bin/sh -x -c nc -vz -w 4 10.1.0.6 80' [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:149] Feb 1 14:45:00.308: INFO: stderr: "+ nc -vz -w 4 10.1.0.6 80\nConnection to 10.1.0.6 80 port [tcp/http] succeeded!\n" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:176] Feb 1 14:45:00.308: INFO: stdout: "" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/kubectl.go:177] Feb 1 14:45:00.308: INFO: Validation succeeded: Service addr 10.1.0.6 and port 80 with protocol [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:210] Feb 1 14:45:00.308: INFO: Getting virtual network list [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:211] Feb 1 14:45:01.260: INFO: got sg list, length = 2 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:236] STEP: Checking if there is a LoadBalancerSourceRanges rule - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:294 @ 02/01/23 14:45:01.26 Feb 1 14:45:01.260: INFO: Checking security rule "allow_ssh" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:423] Feb 1 14:45:01.260: INFO: Checking security rule "allow_apiserver" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:423] Feb 1 14:45:01.376: INFO: Deleting pod exec-agnhost-pod-deny-all-except-lb-range in namespace e2e-tests-nsg-697wp [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:138] [FAILED] Expected <bool>: false to be true In [It] at: /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:296 @ 02/01/23 14:45:01.478 < Exit [It] should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges` - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:227 @ 02/01/23 14:45:01.478 (3m32.413s) > Enter [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:45:01.478 Feb 1 14:45:01.584: INFO: Deleting namespace e2e-tests-nsg-697wp [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:135] < Exit [AfterEach] Network security group - /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/network_security_group.go:79 @ 02/01/23 14:46:01.893 (1m0.415s)
Filter through log files | View test history on testgrid
Cloud provider Azure e2e suite [It] Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly [Credential]
Cloud provider Azure e2e suite [It] Azure node resources should set correct private IP address for every node [Node]
Cloud provider Azure e2e suite [It] Azure node resources should set node provider id correctly [Node]
Cloud provider Azure e2e suite [It] Azure node resources should set route table correctly when the cluster is enabled by kubenet [Node, Kubenet]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support BYO public IP [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support assigning to specific IP when updating public service [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support disabling floating IP in load balancer rule with kubernetes service annotations [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support mixed protocol services [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support multiple external services sharing one newly created public IP addresses [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support multiple external services sharing preset public IP addresses [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support multiple internal services sharing IP addresses [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support updating an internal service to a public service with assigned IP [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support updating internal IP when updating internal service [LB]
Cloud provider Azure e2e suite [It] EnsureLoadBalancer should not update any resources when service config is not changed should respect internal service with various configurations [LB]
Cloud provider Azure e2e suite [It] EnsureLoadBalancer should not update any resources when service config is not changed should respect service with BYO public IP prefix with various configurations [LB]
Cloud provider Azure e2e suite [It] EnsureLoadBalancer should not update any resources when service config is not changed should respect service with BYO public IP with various configurations [LB]
Cloud provider Azure e2e suite [It] EnsureLoadBalancer should not update any resources when service config is not changed should respect service with various configurations [LB]
Cloud provider Azure e2e suite [It] Multi-ports service When ExternalTrafficPolicy is updated Should not have error occurred [Multi-Ports]
Cloud provider Azure e2e suite [It] Network security group can set source IP prefixes automatically according to corresponding service tag [NSG]
Cloud provider Azure e2e suite [It] Network security group should support service annotation `service.beta.kubernetes.io/azure-disable-load-balancer-floating-ip` [NSG]
Cloud provider Azure e2e suite [It] Network security group should support service annotation `service.beta.kubernetes.io/azure-shared-securityrule` [NSG]
Cloud provider Azure e2e suite [It] Private link service should support multiple internal services sharing one private link service [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-auto-approval' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-create' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-fqdns' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-ip-configuration-ip-address' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-ip-configuration-ip-address-count' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-ip-configuration-subnet' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-name' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-proxy-protocol' [PLS]
Cloud provider Azure e2e suite [It] Private link service should support service annotation 'service.beta.kubernetes.io/azure-pls-visibility' [PLS]
Cloud provider Azure e2e suite [It] Service with annotation should generate health probe configs in multi-port scenario [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-dns-label-name' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-enable-high-availability-ports' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-health-probe-num-of-probe', 'service.beta.kubernetes.io/azure-load-balancer-health-probe-interval', 'service.beta.kubernetes.io/azure-load-balancer-health-probe-protocol' and port specific configs [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-internal' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-internal-subnet' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-ip' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation `service.beta.kubernetes.io/azure-additional-public-ips` [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation `service.beta.kubernetes.io/azure-pip-name` [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation `service.beta.kubernetes.io/azure-pip-prefix-id` [ServiceAnnotation]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation `service.beta.kubernetes.io/azure-pip-tags` [ServiceAnnotation]
Cloud provider Azure e2e suite [It] [StandardLoadBalancer] Standard load balancer should add all nodes in different agent pools to backends [Multi-Nodepool]
Cloud provider Azure e2e suite [It] Azure nodes should expose zones correctly after created [VMSS, Serial, Slow]
Cloud provider Azure e2e suite [It] Azure nodes should support crossing resource groups [Multi-Group, AvailabilitySet]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should balance the sizes of multiple node group if the `--balance-node-groups` is set to true [Feature:Autoscaling, Serial, Slow, Multi-Nodepool]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should scale up or down if deployment replicas leave nodes busy or idle [Feature:Autoscaling, Serial, Slow]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should scale up, deploy a statefulset with disks attached, scale down, and certain pods + disks should be evicted to a new node [Feature:Autoscaling, Serial, Slow]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should support multiple node pools with quick scaling [Feature:Autoscaling, Serial, Slow, Multi-Nodepool]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should support one node pool with slow scaling [Feature:Autoscaling, Serial, Slow, Single-Nodepool]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should support scaling up or down Azure Spot VM [Feature:Autoscaling, Serial, Slow, VMSS, Spot-VM]
Cloud provider Azure e2e suite [It] Cluster size autoscaler should support scaling up or down due to the consuming of GPU resource [Feature:Autoscaling, Serial, Slow]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should have no operation since no change in service when update [LB, Slow]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support node label `node.kubernetes.io/exclude-from-external-load-balancers` [LB]
Cloud provider Azure e2e suite [It] Lifecycle of VMSS should add node object when VMSS instance allocated [VMSS, VMSS-Scale]
Cloud provider Azure e2e suite [It] Lifecycle of VMSS should delete node object when VMSS instance deallocated [VMSS, VMSS-Scale]
Cloud provider Azure e2e suite [It] Multiple VMSS should support service annotation `service.beta.kubernetes.io/azure-load-balancer-mode` [Multi-Nodepool, VMSS]
Cloud provider Azure e2e suite [It] Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-resource-group' [ServiceAnnotation]
Cloud provider Azure e2e suite [It] [StandardLoadBalancer] Standard load balancer should make outbound IP of pod same as in SLB's outbound rules [SLBOutbound]