kubernetes-sigs/cloud-provider-azure PR #524 pull-cloud-provider-azure-e2e-ccm #1365480078368051200
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | CecileRobertMichon: enable gosec linter |
| Result | FAILURE |
| Tests | 2 failed / 36 succeeded |
| Started | |
| Elapsed | 1h30m |
| Revision | 6f6f0cb00fa695b9212ba98103f1b65dc063354b |
| Refs |
524 |
| job-version | v1.20.5-rc.0.10+165e5664b0e65d |
| revision | v1.20.5-rc.0.10+165e5664b0e65d |
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:379
Unexpected error:
<*errors.errorString | 0xc0006fc590>: {
s: "Cannot find Ingress in limited time",
}
Cannot find Ingress in limited time
occurred
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:404
[BeforeEach] Service with annotation
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:79
Feb 27 02:14:28.773: INFO: Creating a kubernetes client
Feb 27 02:14:28.774: INFO: Kubernetes configuration file name: /root/tmp656918858/kubeconfig/kubeconfig.westus2.json
Feb 27 02:14:28.775: INFO: Creating a test namespace
Feb 27 02:14:28.828: INFO: Creating deployment annotation-test
Feb 27 02:14:28.882: INFO: Creating Azure clients
Feb 27 02:14:28.882: INFO: Creating a kubernetes client
Feb 27 02:14:28.882: INFO: Kubernetes configuration file name: /root/tmp656918858/kubeconfig/kubeconfig.westus2.json
[It] should support service annotation `service.beta.kubernetes.io/azure-pip-name`
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:379
�[1mSTEP�[0m: Creating two test pips
Feb 27 02:14:29.048: INFO: Creating public IP resource named pip1
Feb 27 02:14:32.815: INFO: Creating public IP resource named pip2
�[1mSTEP�[0m: Creating a service referring to the first pip
�[1mSTEP�[0m: Waiting for the service to expose
Feb 27 02:14:36.024: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:14:46.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:14:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:26.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:15:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:16:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:06.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:46.086: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:17:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:18:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:19:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:16.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:26.111: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:36.148: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:46.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:20:56.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:06.089: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:36.087: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:46.087: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:21:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:16.086: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:26.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:36.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:46.085: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:22:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:06.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:16.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:26.085: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:36.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:23:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:06.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:36.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:24:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:06.083: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:16.085: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:26.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:36.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:46.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:25:56.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:06.083: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:16.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:26.089: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:26:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:16.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:26.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:46.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:27:56.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:06.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:16.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:26.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:36.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:46.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:28:56.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:06.083: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:16.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:26.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:36.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:46.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:29:56.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:36.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:46.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:30:56.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:46.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:31:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:26.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:32:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:36.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:33:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:06.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:26.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:46.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:34:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:16.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:26.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:35:56.076: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:06.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:26.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:36.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:46.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:36:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:06.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:16.087: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:26.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:36.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:37:56.085: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:06.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:26.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:36.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:46.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:38:56.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:06.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:16.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:36.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:46.084: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:39:56.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:26.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:36.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:40:56.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:06.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:16.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:26.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:36.082: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:41:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:06.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:16.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:26.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:36.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:46.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:42:56.080: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:16.081: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:26.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:46.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:43:56.079: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:44:06.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:44:16.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:44:26.078: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:44:36.077: INFO: Fail to find ingress, retry it in 10 seconds
Feb 27 02:44:36.128: INFO: Fail to find ingress, retry it in 10 seconds
�[1mSTEP�[0m: Cleaning up test service
Feb 27 02:44:36.194: INFO: Deleting service annotation-test in namespace e2e-tests-service-j8xmp
�[1mSTEP�[0m: Cleaning up test PIPs
[AfterEach] Service with annotation
/home/prow/go/src/sigs.k8s.io/cloud-provider-azure/tests/e2e/network/service_annotations.go:97
Feb 27 02:45:00.371: INFO: Deleting namespace e2e-tests-service-j8xmp
from junit_01.xml
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
Build
Check APIReachability
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 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 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-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
Deferred TearDown
DumpClusterLogs
IsUp
TearDown
TearDown Previous
Timeout
Up
kubectl version
list nodes
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`