This job view page is being replaced by Spyglass soon. Check out the new job view.
PRweijiehu: Improves unittest CC for azure_storageaccountclient
ResultFAILURE
Tests 0 failed / 262 succeeded
Started2020-05-18 09:07
Elapsed2h0m
Revision428dc7de571247a28f36debae992dafbca4374fb
Refs 91197
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/7faee231-80b8-44c9-93ee-9c770d3d0b67/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/7faee231-80b8-44c9-93ee-9c770d3d0b67/targets/test

No Test Failures!


Show 262 Passed Tests

Show 4464 Skipped Tests

Error lines from build-log.txt

... skipping 282 lines ...

Running in parallel across 30 nodes

May 18 09:44:48.775: INFO: >>> kubeConfig: /root/tmp746072548/kubeconfig/kubeconfig.westus2.json
May 18 09:44:48.827: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
May 18 09:44:49.474: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
May 18 09:44:49.952: INFO: The status of Pod azure-cni-networkmonitor-rvlkd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: The status of Pod blobfuse-flexvol-installer-8xwzl is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: The status of Pod blobfuse-flexvol-installer-ckvzg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: The status of Pod keyvault-flexvolume-wsqgw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: The status of Pod kubernetes-dashboard-5f6bff5cf5-qtb6s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:49.952: INFO: 10 / 16 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
May 18 09:44:49.952: INFO: expected 3 pod replicas in namespace 'kube-system', 2 are Running and Ready.
May 18 09:44:49.952: INFO: POD                                    NODE                                PHASE    GRACE  CONDITIONS
May 18 09:44:49.952: INFO: azure-cni-networkmonitor-rvlkd         k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:49.952: INFO: blobfuse-flexvol-installer-8xwzl       k8s-agentpool1-25342784-vmss000000  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:30 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:30 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:30 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:49.952: INFO: blobfuse-flexvol-installer-ckvzg       k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:49.952: INFO: keyvault-flexvolume-n6g4d              k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:49.952: INFO: keyvault-flexvolume-wsqgw              k8s-agentpool1-25342784-vmss000000  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:49.957: INFO: kubernetes-dashboard-5f6bff5cf5-qtb6s  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:49.957: INFO: 
May 18 09:44:52.341: INFO: The status of Pod azure-cni-networkmonitor-rvlkd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:52.341: INFO: The status of Pod blobfuse-flexvol-installer-ckvzg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:52.341: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:52.341: INFO: The status of Pod kube-scheduler-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:52.341: INFO: The status of Pod kubernetes-dashboard-5f6bff5cf5-qtb6s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:52.341: INFO: 12 / 17 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
May 18 09:44:52.341: INFO: expected 3 pod replicas in namespace 'kube-system', 2 are Running and Ready.
May 18 09:44:52.341: INFO: POD                                    NODE                                PHASE    GRACE  CONDITIONS
May 18 09:44:52.341: INFO: azure-cni-networkmonitor-rvlkd         k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:52.341: INFO: blobfuse-flexvol-installer-ckvzg       k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:52.341: INFO: keyvault-flexvolume-n6g4d              k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:52.341: INFO: kube-scheduler-k8s-master-25342784-0   k8s-master-25342784-0               Pending         []
May 18 09:44:52.341: INFO: kubernetes-dashboard-5f6bff5cf5-qtb6s  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:52.341: INFO: 
May 18 09:44:54.339: INFO: The status of Pod azure-cni-networkmonitor-rvlkd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:54.339: INFO: The status of Pod blobfuse-flexvol-installer-ckvzg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:54.339: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:54.339: INFO: The status of Pod kube-scheduler-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:54.339: INFO: The status of Pod kubernetes-dashboard-5f6bff5cf5-qtb6s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:54.339: INFO: 12 / 17 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
May 18 09:44:54.339: INFO: expected 3 pod replicas in namespace 'kube-system', 2 are Running and Ready.
May 18 09:44:54.339: INFO: POD                                    NODE                                PHASE    GRACE  CONDITIONS
May 18 09:44:54.339: INFO: azure-cni-networkmonitor-rvlkd         k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:54.339: INFO: blobfuse-flexvol-installer-ckvzg       k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:54.339: INFO: keyvault-flexvolume-n6g4d              k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:54.339: INFO: kube-scheduler-k8s-master-25342784-0   k8s-master-25342784-0               Pending         []
May 18 09:44:54.339: INFO: kubernetes-dashboard-5f6bff5cf5-qtb6s  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:54.339: INFO: 
May 18 09:44:56.305: INFO: The status of Pod azure-cni-networkmonitor-rvlkd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:56.305: INFO: The status of Pod blobfuse-flexvol-installer-ckvzg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:56.305: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:56.305: INFO: The status of Pod kube-scheduler-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:56.305: INFO: The status of Pod kubernetes-dashboard-5f6bff5cf5-qtb6s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:56.305: INFO: 12 / 17 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
May 18 09:44:56.305: INFO: expected 3 pod replicas in namespace 'kube-system', 2 are Running and Ready.
May 18 09:44:56.305: INFO: POD                                    NODE                                PHASE    GRACE  CONDITIONS
May 18 09:44:56.305: INFO: azure-cni-networkmonitor-rvlkd         k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [azure-cnms]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:56.306: INFO: blobfuse-flexvol-installer-ckvzg       k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:56.306: INFO: keyvault-flexvolume-n6g4d              k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:56.306: INFO: kube-scheduler-k8s-master-25342784-0   k8s-master-25342784-0               Pending         []
May 18 09:44:56.306: INFO: kubernetes-dashboard-5f6bff5cf5-qtb6s  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [kubernetes-dashboard]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:56.306: INFO: 
May 18 09:44:58.342: INFO: The status of Pod blobfuse-flexvol-installer-ckvzg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:58.342: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:44:58.342: INFO: 15 / 17 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
May 18 09:44:58.342: INFO: expected 3 pod replicas in namespace 'kube-system', 3 are Running and Ready.
May 18 09:44:58.342: INFO: POD                               NODE                                PHASE    GRACE  CONDITIONS
May 18 09:44:58.342: INFO: blobfuse-flexvol-installer-ckvzg  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC ContainersNotReady containers with unready status: [blobfuse-flexvol-installer]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:29 +0000 UTC  }]
May 18 09:44:58.342: INFO: keyvault-flexvolume-n6g4d         k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:44:58.342: INFO: 
May 18 09:45:00.310: INFO: The status of Pod keyvault-flexvolume-n6g4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:00.310: INFO: 16 / 17 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
May 18 09:45:00.310: INFO: expected 3 pod replicas in namespace 'kube-system', 3 are Running and Ready.
May 18 09:45:00.310: INFO: POD                        NODE                                PHASE    GRACE  CONDITIONS
May 18 09:45:00.310: INFO: keyvault-flexvolume-n6g4d  k8s-agentpool1-25342784-vmss000001  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC ContainersNotReady containers with unready status: [keyvault-flexvolume]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-05-18 09:44:28 +0000 UTC  }]
May 18 09:45:00.310: INFO: 
May 18 09:45:02.319: INFO: The status of Pod kube-addon-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:02.319: INFO: The status of Pod kube-controller-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:02.319: INFO: 17 / 19 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
May 18 09:45:02.319: INFO: expected 3 pod replicas in namespace 'kube-system', 3 are Running and Ready.
May 18 09:45:02.319: INFO: POD                                            NODE                   PHASE    GRACE  CONDITIONS
May 18 09:45:02.319: INFO: kube-addon-manager-k8s-master-25342784-0       k8s-master-25342784-0  Pending         []
May 18 09:45:02.319: INFO: kube-controller-manager-k8s-master-25342784-0  k8s-master-25342784-0  Pending         []
May 18 09:45:02.319: INFO: 
May 18 09:45:04.295: INFO: The status of Pod kube-addon-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:04.295: INFO: The status of Pod kube-controller-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:04.295: INFO: 17 / 19 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
May 18 09:45:04.295: INFO: expected 3 pod replicas in namespace 'kube-system', 3 are Running and Ready.
May 18 09:45:04.295: INFO: POD                                            NODE                   PHASE    GRACE  CONDITIONS
May 18 09:45:04.295: INFO: kube-addon-manager-k8s-master-25342784-0       k8s-master-25342784-0  Pending         []
May 18 09:45:04.295: INFO: kube-controller-manager-k8s-master-25342784-0  k8s-master-25342784-0  Pending         []
May 18 09:45:04.295: INFO: 
May 18 09:45:06.267: INFO: The status of Pod kube-addon-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:06.267: INFO: The status of Pod kube-controller-manager-k8s-master-25342784-0 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
May 18 09:45:06.267: INFO: 17 / 19 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
May 18 09:45:06.267: INFO: expected 3 pod replicas in namespace 'kube-system', 3 are Running and Ready.
May 18 09:45:06.267: INFO: POD                                            NODE                   PHASE    GRACE  CONDITIONS
May 18 09:45:06.267: INFO: kube-addon-manager-k8s-master-25342784-0       k8s-master-25342784-0  Pending         []
May 18 09:45:06.267: INFO: kube-controller-manager-k8s-master-25342784-0  k8s-master-25342784-0  Pending         []
May 18 09:45:06.267: INFO: 
... skipping 155 lines ...
May 18 09:45:09.177: INFO: >>> kubeConfig: /root/tmp746072548/kubeconfig/kubeconfig.westus2.json
STEP: Building a namespace api object, basename configmap
May 18 09:45:10.156: INFO: Found PodSecurityPolicies; assuming PodSecurityPolicy is enabled.
May 18 09:45:10.318: INFO: Found ClusterRoles; assuming RBAC is enabled.
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in configmap-8995
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to create ConfigMap with empty key [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
STEP: Creating configMap that has name configmap-test-emptyKey-582dc220-65e3-422e-b058-afe9bca2cb84
[AfterEach] [sig-node] ConfigMap
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
May 18 09:45:10.699: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-8995" for this suite.

•
------------------------------
{"msg":"PASSED [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]","total":-1,"completed":1,"skipped":8,"failed":0}

SSSSSSSSSSSSS
------------------------------
[BeforeEach] [sig-cli] Kubectl client
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 14 lines ...
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
May 18 09:45:11.439: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubectl-14" for this suite.

•
------------------------------
{"msg":"PASSED [sig-cli] Kubectl client Kubectl version should check is all data is printed  [Conformance]","total":-1,"completed":1,"skipped":13,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [sig-api-machinery] Watchers
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 16 lines ...
• [SLOW TEST:9.419 seconds]
[sig-api-machinery] Watchers
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
  should receive events on concurrent watches in same order [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]","total":-1,"completed":1,"skipped":13,"failed":0}

S
------------------------------
[BeforeEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 4 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in security-context-test-9424
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should allow privilege escalation when true [LinuxOnly] [NodeConformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:362
May 18 09:45:09.844: INFO: Waiting up to 5m0s for pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37" in namespace "security-context-test-9424" to be "Succeeded or Failed"
May 18 09:45:09.914: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37": Phase="Pending", Reason="", readiness=false. Elapsed: 69.877415ms
May 18 09:45:11.973: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129461903s
May 18 09:45:14.029: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37": Phase="Pending", Reason="", readiness=false. Elapsed: 4.184639162s
May 18 09:45:16.093: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37": Phase="Pending", Reason="", readiness=false. Elapsed: 6.248739302s
May 18 09:45:18.161: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.316685757s
May 18 09:45:18.161: INFO: Pod "alpine-nnp-true-a61742d3-fba7-41af-9241-4b0a38df2f37" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
May 18 09:45:18.257: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-9424" for this suite.


... skipping 2 lines ...
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:592
  when creating containers with AllowPrivilegeEscalation
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:291
    should allow privilege escalation when true [LinuxOnly] [NodeConformance]
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:362
------------------------------
{"msg":"PASSED [k8s.io] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when true [LinuxOnly] [NodeConformance]","total":-1,"completed":1,"skipped":6,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 4 lines ...
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in security-context-test-1675
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
[It] should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
May 18 09:45:09.796: INFO: Waiting up to 5m0s for pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e" in namespace "security-context-test-1675" to be "Succeeded or Failed"
May 18 09:45:09.853: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Pending", Reason="", readiness=false. Elapsed: 56.334909ms
May 18 09:45:11.908: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111404293s
May 18 09:45:13.963: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Pending", Reason="", readiness=false. Elapsed: 4.16627269s
May 18 09:45:16.014: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217741387s
May 18 09:45:18.070: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Pending", Reason="", readiness=false. Elapsed: 8.273708151s
May 18 09:45:20.125: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.329031594s
May 18 09:45:20.125: INFO: Pod "busybox-readonly-false-ccacfa36-879c-460c-ba31-8833ce4f8e9e" satisfied condition "Succeeded or Failed"
[AfterEach] [k8s.io] Security Context
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
May 18 09:45:20.125: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "security-context-test-1675" for this suite.


... skipping 2 lines ...
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:592
  When creating a pod with readOnlyRootFilesystem
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:166
    should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":16,"failed":0}

SSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[BeforeEach] [sig-storage] EmptyDir volumes
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 3 lines ...
May 18 09:45:09.225: INFO: Found ClusterRoles; assuming RBAC is enabled.
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in emptydir-5229
STEP: Waiting for a default service account to be provisioned in namespace
[It] should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
STEP: Creating a pod to test emptydir 0777 on node default medium
May 18 09:45:09.654: INFO: Waiting up to 5m0s for pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b" in namespace "emptydir-5229" to be "Succeeded or Failed"
May 18 09:45:09.712: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Pending", Reason="", readiness=false. Elapsed: 57.695956ms
May 18 09:45:11.763: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108665123s
May 18 09:45:13.814: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.159415073s
May 18 09:45:15.876: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221137205s
May 18 09:45:17.941: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Pending", Reason="", readiness=false. Elapsed: 8.286494028s
May 18 09:45:20.004: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.349636355s
STEP: Saw pod success
May 18 09:45:20.004: INFO: Pod "pod-720a8b6d-d096-40be-a6ab-f728ab97712b" satisfied condition "Succeeded or Failed"
May 18 09:45:20.055: INFO: Trying to get logs from node k8s-agentpool1-25342784-vmss000000 pod pod-720a8b6d-d096-40be-a6ab-f728ab97712b container test-container: <nil>
STEP: delete the pod
May 18 09:45:20.534: INFO: Waiting for pod pod-720a8b6d-d096-40be-a6ab-f728ab97712b to disappear
May 18 09:45:20.595: INFO: Pod pod-720a8b6d-d096-40be-a6ab-f728ab97712b no longer exists
[AfterEach] [sig-storage] EmptyDir volumes
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
... skipping 4 lines ...
• [SLOW TEST:12.007 seconds]
[sig-storage] EmptyDir volumes
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:42
  should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":33,"failed":0}

SSSSSSSSSS
------------------------------
[BeforeEach] [k8s.io] Pods
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 23 lines ...
• [SLOW TEST:12.019 seconds]
[k8s.io] Pods
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:592
  should be updated [NodeConformance] [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [k8s.io] Pods should be updated [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":5,"failed":0}

SS
------------------------------
[BeforeEach] [k8s.io] Kubelet
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 18 lines ...
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:592
  when scheduling a read only busybox container
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/kubelet.go:188
    should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:597
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a read only busybox container should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":5,"failed":0}

SSS
------------------------------
[BeforeEach] [k8s.io] InitContainer [NodeConformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
May 18 09:45:18.520: INFO: >>> kubeConfig: /root/tmp746072548/kubeconfig/kubeconfig.westus2.json
STEP: Building a namespace api object, basename init-container
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in init-container