kubernetes-sigs/cloud-provider-azure PR #1632 pull-cloud-provider-azure-e2e-ccm-vmss-1-20 #1520327662805979136
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | feiskyer: fix-0.7: update probe when protocol or request path change |
| Result | FAILURE |
| Tests | 2 failed / 44 succeeded |
| Started | |
| Elapsed | 1h31m |
| Revision | 65a732a36b121c440abef0b609ab9957d0ce5959 |
| Refs |
1632 |
| job-version | v1.20.16-rc.0.3+4a89df5617b8e1 |
| kubetest-version | |
| revision | v1.20.16-rc.0.3+4a89df5617b8e1 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Cloud\sprovider\sAzure\se2e\ssuite\sService\swith\sannotation\sshould\ssupport\sservice\sannotation\s\`service\.beta\.kubernetes\.io\/azure\-pip\-name\`$'
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:78
Unexpected error:
<*errors.errorString | 0xc0002c2d00>: {
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:97
[BeforeEach] Service with annotation
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:78
Apr 30 10:14:13.568: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:57]
Apr 30 10:14:13.568: INFO: Kubernetes configuration file name: /root/tmp2244981025/kubeconfig/kubeconfig.uksouth.json [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:65]
Apr 30 10:14:13.570: INFO: Creating a test namespace [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:89]
Apr 30 10:14:13.676: INFO: Creating deployment annotation-test [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:86]
Apr 30 10:14:13.786: INFO: Waiting for backend pods to be ready [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:91]
Apr 30 10:14:13.990: INFO: 5 pods in namespace e2e-tests-service-hr4th are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:83]
Apr 30 10:14:24.197: INFO: 0 pods in namespace e2e-tests-service-hr4th are pending [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/pod_utils.go:83]
Apr 30 10:14:24.197: INFO: Creating Azure clients [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:95]
Apr 30 10:14:24.197: INFO: Creating a kubernetes client [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:57]
Apr 30 10:14:24.198: INFO: Kubernetes configuration file name: /root/tmp2244981025/kubeconfig/kubeconfig.uksouth.json [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:65]
Apr 30 10:14:24.505: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:14:34.914: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:14:44.914: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:14:54.917: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:04.914: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:14.913: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:24.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:34.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:44.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:15:54.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:04.917: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:14.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:24.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:34.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:44.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:16:54.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:04.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:14.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:24.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:34.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:44.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:17:54.917: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:04.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:14.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:24.914: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:34.916: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:44.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:18:54.917: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:19:04.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:19:14.915: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:19:24.914: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:19:25.025: INFO: the providerID of node k8s-agentpool1-21269726-vmss000003 is empty, will retry soon [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:92]
Apr 30 10:19:25.025: INFO: error when waiting for the result: timed out waiting for the condition [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/node_utils.go:101]
[AfterEach] Service with annotation
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:100
Apr 30 10:19:25.136: INFO: Deleting namespace e2e-tests-service-hr4th [/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/utils/utils.go:137]
from junit_01.xml
Filter through log files
error during make test-ccm-e2e: exit status 2
from junit_runner.xml
Filter through log files
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 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 node label `node.kubernetes.io/exclude-from-external-load-balancers`
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 Multi-ports service When ExternalTrafficPolicy is updated Should not have error occurred
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-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 [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
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 [[Multi-Nodepool]][VMSS] should support service annotation `service.beta.kubernetes.io/azure-load-balancer-mode`