Recent runs || View in Spyglass
PR | jwtty: [Release-1.0]feat: Private Link Service Integration for k8s service |
Result | FAILURE |
Tests | 2 failed / 43 succeeded |
Started | |
Elapsed | 2h17m |
Revision | e49b036a93145e29ff59c4ccb8bd3c514dc33269 |
Refs |
1683 |
job-version | v1.21.13-rc.0.14+e74362de8497d8 |
kubetest-version | |
revision | v1.21.13-rc.0.14+e74362de8497d8 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\sMulti\-ports\sservice\sWhen\sExternalTrafficPolicy\sis\supdated\sShould\snot\shave\serror\soccurred$'
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:632 Unexpected error: <*errors.errorString | 0xc0002c04b0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:713from junit_01.xml
May 7 03:15:42.270: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:57] May 7 03:15:42.270: INFO: Kubernetes configuration file name: /root/tmp1134302031/kubeconfig/kubeconfig.westus2.json [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:65] May 7 03:15:42.271: INFO: Creating a test namespace [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:89] May 7 03:15:42.338: INFO: Creating deployment multiport-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:605] May 7 03:15:42.396: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:610] May 7 03:15:42.520: INFO: 5 pods in namespace e2e-tests-mpservice-78h9c are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:83] May 7 03:15:52.632: INFO: 0 pods in namespace e2e-tests-mpservice-78h9c are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:83] May 7 03:15:52.632: INFO: Creating Azure clients [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:614] May 7 03:15:52.632: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:57] May 7 03:15:52.632: INFO: Kubernetes configuration file name: /root/tmp1134302031/kubeconfig/kubeconfig.westus2.json [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:65] �[1mSTEP�[0m: Getting the service May 7 03:15:52.797: INFO: Creating service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:635] May 7 03:15:52.888: INFO: Successfully created LoadBalancer service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:639] May 7 03:15:52.888: INFO: Waiting service to expose... [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:642] May 7 03:15:52.942: 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:132] May 7 03:16:02.999: 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:132] May 7 03:16:12.998: 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:132] May 7 03:16:23.000: INFO: Exposure successfully, get external ip: 20.236.38.245 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:147] May 7 03:16:23.000: INFO: checking the connectivity of the public IP 20.236.38.245 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:96] May 7 03:16:30.343: INFO: succeeded [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:178] May 7 03:16:30.343: INFO: validation finished [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:186] �[1mSTEP�[0m: Changing ExternalTrafficPolicy of the service to Local May 7 03:16:30.343: INFO: Updating service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:657] May 7 03:16:30.469: INFO: Successfully updated LoadBalancer service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:668] �[1mSTEP�[0m: Getting updated service object from server May 7 03:16:30.526: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:30.959: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:30.960: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:30.960: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:30.960: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:30.960: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] �[1mSTEP�[0m: Changing ExternalTrafficPolicy of the service to Cluster May 7 03:16:31.194: INFO: Updating service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:693] May 7 03:16:31.329: INFO: Successfully updated LoadBalancer service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:704] May 7 03:16:31.329: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:31.545: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:31.545: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:31.545: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:31.545: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:31.545: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:16:36.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:36.994: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:36.995: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:36.995: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:36.995: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:36.995: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:16:41.760: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:41.970: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:41.971: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:41.971: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:41.971: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:41.971: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:16:46.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:46.975: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:46.976: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:46.976: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:46.976: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:46.976: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:16:51.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:51.854: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:51.854: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:51.854: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:51.854: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:51.854: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:16:56.759: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:16:56.974: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:16:56.974: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:16:56.974: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:16:56.974: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:16:56.974: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:01.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:01.974: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:01.974: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:01.974: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:01.974: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:01.974: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:06.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:07.041: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:07.041: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:07.041: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:07.041: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:07.041: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:11.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:11.980: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:11.980: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:11.980: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:11.980: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:11.980: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:16.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:17.002: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:17.002: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:17.002: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:17.002: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:17.002: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:21.759: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:21.996: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:21.996: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:21.996: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:21.996: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:21.996: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:26.758: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:26.865: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:26.865: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:26.865: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:26.865: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:26.865: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:31.759: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:31.975: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:31.975: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:31.975: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:31.975: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:31.975: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] May 7 03:17:32.197: INFO: Getting public IPs in the resourceGroup kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:734] May 7 03:17:32.421: INFO: Getting public IP frontend configuration ID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:738] May 7 03:17:32.421: INFO: Successfully obtained PIP front config id: /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-fwmxtxsm/providers/Microsoft.Network/loadBalancers/kubetest-fwmxtxsm/frontendIPConfigurations/ae8829ef33de44fdbacfa40f742dd5b3 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:751] May 7 03:17:32.421: INFO: Getting loadBalancer name from pipFrontendConfigurationID [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:753] May 7 03:17:32.421: INFO: Got loadBalancerName "kubetest-fwmxtxsm" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:758] May 7 03:17:32.421: INFO: Getting loadBalancer [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:760] �[1mSTEP�[0m: Cleaning up service and public IP May 7 03:17:32.642: INFO: Deleting service multiport-test in namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/service_utils.go:48] May 7 03:19:16.847: INFO: Deleting public IP resource named 20.236.38.245 in resource group kubetest-fwmxtxsm [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_utils.go:200] May 7 03:19:17.268: INFO: Deleting namespace e2e-tests-mpservice-78h9c [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:137]
Filter through log files | View test history on testgrid
error during make test-ccm-e2e: exit status 2
from junit_runner.xml
Filter through log files | View test history on testgrid
Cloud provider Azure e2e suite Azure Credential Provider should be able to pull private images from acr without docker secrets set explicitly
Cloud provider Azure e2e suite Azure node resources should set correct private IP address for every node
Cloud provider Azure e2e suite Azure node resources should set node provider id correctly
Cloud provider Azure e2e suite Azure node resources should set route table correctly when the cluster is enabled by kubenet [Kubenet]
Cloud provider Azure e2e suite Ensure LoadBalancer should have no operation since no change in service when update [Slow]
Cloud provider Azure e2e suite Ensure LoadBalancer should support BYO public IP
Cloud provider Azure e2e suite Ensure LoadBalancer should support assigning to specific IP when updating public service
Cloud provider Azure e2e suite Ensure LoadBalancer should support mixed protocol services
Cloud provider Azure e2e suite Ensure LoadBalancer should support multiple external services sharing one newly created public IP address
Cloud provider Azure e2e suite Ensure LoadBalancer should support multiple external services sharing one preset public IP address
Cloud provider Azure e2e suite Ensure LoadBalancer should support multiple internal services sharing one IP address
Cloud provider Azure e2e suite Ensure LoadBalancer should support updating an internal service to a public service with assigned IP
Cloud provider Azure e2e suite Ensure LoadBalancer should support updating internal IP when updating internal service
Cloud provider Azure e2e suite Lifecycle of VMSS should add node object when VMSS instance allocated
Cloud provider Azure e2e suite Lifecycle of VMSS should delete node object when VMSS instance deallocated
Cloud provider Azure e2e suite Network security group can set source IP prefixes automatically according to corresponding service tag
Cloud provider Azure e2e suite Network security group should add the rule when expose a service
Cloud provider Azure e2e suite Network security group should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges`
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-dns-label-name'
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-health-probe-num-of-probe' and port specific configs
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-health-probe-protocol' and port specific configs
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-internal'
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-internal-subnet'
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-resource-group'
Cloud provider Azure e2e suite Service with annotation should support service annotation 'service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout'
Cloud provider Azure e2e suite Service with annotation should support service annotation `service.beta.kubernetes.io/azure-pip-name`
Cloud provider Azure e2e suite Service with annotation should support service annotation `service.beta.kubernetes.io/azure-pip-tags`
Cloud provider Azure e2e suite Service with annotation should support service annotation `service.beta.kubernetes.io/azure-shared-securityrule`
Cloud provider Azure e2e suite [[Multi-Nodepool]][VMSS] should support service annotation `service.beta.kubernetes.io/azure-load-balancer-mode`
kubetest Build
kubetest Check APIReachability
kubetest Deferred TearDown
kubetest DumpClusterLogs
kubetest GetDeployer
kubetest IsUp
kubetest Prepare
kubetest TearDown
kubetest TearDown Previous
kubetest Timeout
kubetest Up
kubetest kubectl version
kubetest list nodes
kubetest test setup
Cloud provider Azure e2e suite Azure nodes should expose zones correctly after created [VMSS][Serial][Slow]
Cloud provider Azure e2e suite Azure nodes should support crossing resource groups [Multi-Group][AvailabilitySet]
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should balance the sizes of multiple node group if the `--balance-node-groups` is set to true [Multi-Nodepool]
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should scale up or down if deployment replicas leave nodes busy or idle
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should scale up, deploy a statefulset with disks attached, scale down, and certain pods + disks should be evicted to a new node
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should support multiple node pools with quick scaling [Multi-Nodepool]
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should support one node pool with slow scaling [Single Nodepool]
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should support scaling up or down Azure Spot VM [VMSS][Spot VM]
Cloud provider Azure e2e suite Cluster size autoscaler [Feature:Autoscaling][Serial][Slow] should support scaling up or down due to the consuming of GPU resource
Cloud provider Azure e2e suite Ensure LoadBalancer should support node label `node.kubernetes.io/exclude-from-external-load-balancers`
Cloud provider Azure e2e suite [StandardLoadBalancer] Standard load balancer should add all nodes in different agent pools to backends [MultipleAgentPools]
Cloud provider Azure e2e suite [StandardLoadBalancer] Standard load balancer should make outbound IP of pod same as in SLB's outbound rules