Recent runs || View in Spyglass
PR | k8s-infra-cherrypick-robot: [release-1.1] [aks pipeline] CLUSTER_CONFIG_PATH can be set by users |
Result | FAILURE |
Tests | 2 failed / 44 succeeded |
Started | |
Elapsed | 2h20m |
Revision | 580549857619ebf64798e41f1097dcbb6c4c20e1 |
Refs |
2799 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\s\[It\]\sAzure\snode\sresources\sshould\sset\scorrect\sprivate\sIP\saddress\sfor\severy\snode\s\[Node\]$'
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:201 sigs.k8s.io/cloud-provider-azure/tests/e2e/network.glob..func4.4() /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:201 +0x439from junit_01.xml
Nov 18 09:35:50.914: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:50.914: 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:63] Nov 18 09:35:50.945: INFO: Created a test namespace "e2e-tests-node-resources-h8wp4" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:109] Nov 18 09:35:50.945: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:50.945: 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:63] Nov 18 09:35:50.985: INFO: getting all NICs of availabilitySet VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:133] Nov 18 09:35:50.985: INFO: getting network interfaces list in resource group capz-azozvf [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_interface_utils.go:36] Nov 18 09:35:51.192: INFO: getting all VMs managed by availabilitySet [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:137] Nov 18 09:35:51.316: INFO: getting all scale sets [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:176] Nov 18 09:35:51.463: INFO: getting all NICs of VMSSes [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:180] Nov 18 09:35:52.164: INFO: getting all NICs of VMSS VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:194] Nov 18 09:35:52.164: INFO: Checking 824639022944 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:52.196: INFO: Checking 824635845584 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:52.228: INFO: Checking 824635846800 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:52.257: INFO: Deleting namespace e2e-tests-node-resources-h8wp4 [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:134] Ginkgo: Attempt #1 Failed. Retrying... Nov 18 09:35:58.345: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:58.345: 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:63] Nov 18 09:35:58.376: INFO: Created a test namespace "e2e-tests-node-resources-sfk9z" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:109] Nov 18 09:35:58.376: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:58.376: 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:63] Nov 18 09:35:58.424: INFO: getting all NICs of availabilitySet VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:133] Nov 18 09:35:58.424: INFO: getting network interfaces list in resource group capz-azozvf [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/network_interface_utils.go:36] Nov 18 09:35:58.637: INFO: getting all VMs managed by availabilitySet [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:137] Nov 18 09:35:58.768: INFO: getting all scale sets [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:176] Nov 18 09:35:58.867: INFO: getting all NICs of VMSSes [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:180] Nov 18 09:35:59.545: INFO: getting all NICs of VMSS VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:194] Nov 18 09:35:59.545: INFO: Checking 824639118784 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:59.577: INFO: Checking 824636050768 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:59.608: INFO: Checking 824636051808 VMSS VM %!q(MISSING) [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:196] Nov 18 09:35:59.639: INFO: Deleting namespace e2e-tests-node-resources-sfk9z [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:134]
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\s\[It\]\sAzure\snode\sresources\sshould\sset\snode\sprovider\sid\scorrectly\s\[Node\]$'
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:118 sigs.k8s.io/cloud-provider-azure/tests/e2e/network.glob..func4.3() /home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:118 +0x466from junit_01.xml
Nov 18 09:35:37.346: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:37.346: 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:63] Nov 18 09:35:37.378: INFO: Created a test namespace "e2e-tests-node-resources-hpjgs" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:109] Nov 18 09:35:37.378: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:37.378: 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:63] Nov 18 09:35:37.417: INFO: getting meta info of test environment [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:78] Nov 18 09:35:37.417: INFO: getting VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:83] Nov 18 09:35:37.770: INFO: getting VMSS VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:104] Nov 18 09:35:38.050: INFO: Deleting namespace e2e-tests-node-resources-hpjgs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:134] Ginkgo: Attempt #1 Failed. Retrying... Nov 18 09:35:44.140: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:44.140: 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:63] Nov 18 09:35:44.171: INFO: Created a test namespace "e2e-tests-node-resources-8hg8m" [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:109] Nov 18 09:35:44.171: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:55] Nov 18 09:35:44.171: 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:63] Nov 18 09:35:44.216: INFO: getting meta info of test environment [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:78] Nov 18 09:35:44.216: INFO: getting VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:83] Nov 18 09:35:44.466: INFO: getting VMSS VMs [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/node.go:104] Nov 18 09:35:44.824: INFO: Deleting namespace e2e-tests-node-resources-8hg8m [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:134]
Filter through log files
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 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 address [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support multiple external services sharing one preset public IP address [LB]
Cloud provider Azure e2e suite [It] Ensure LoadBalancer should support multiple internal services sharing one IP address [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] Lifecycle of VMSS should add node object when VMSS instance allocated [VMSS]
Cloud provider Azure e2e suite [It] Lifecycle of VMSS should delete node object when VMSS instance deallocated [VMSS]
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 add the rule when expose a service [NSG]
Cloud provider Azure e2e suite [It] Network security group should support service annotation `service.beta.kubernetes.io/azure-deny-all-except-load-balancer-source-ranges` [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 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-health-probe-num-of-probe' 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-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-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] 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]