pull-aws-efs-csi-driver-e2e #1621879403761897472 Results

Test Failures

EFS CSI Suite [efs-csi] EFS CSI [Driver: efs.csi.aws.com] should create a directory with the correct permissions when in directory provisioning mode 19s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=EFS\sCSI\sSuite\s\[efs\-csi\]\sEFS\sCSI\s\[Driver\:\sefs\.csi\.aws\.com\]\sshould\screate\sa\sdirectory\swith\sthe\scorrect\spermissions\swhen\sin\sdirectory\sprovisioning\smode$'

/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:398
Checking File Permissions of mounted folder
Expected
    <string>: 755
to equal
    <string>: 777
/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:426
				[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
�[1mSTEP�[0m: Creating a kubernetes client
Feb  4 14:44:41.531: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
�[1mSTEP�[0m: Building a namespace api object, basename efs
�[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace
[It] should create a directory with the correct permissions when in directory provisioning mode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:398
Feb  4 14:44:41.939: INFO: Created StorageClass efs-4439l9p2n
Feb  4 14:44:42.009: INFO: Waiting up to timeout=1m0s for PersistentVolumeClaims [directory-pvc-1] to have phase Bound
Feb  4 14:44:42.076: INFO: PersistentVolumeClaim directory-pvc-1 found but phase is Pending instead of Bound.
Feb  4 14:44:47.148: INFO: PersistentVolumeClaim directory-pvc-1 found and phase=Bound (5.138931342s)
Feb  4 14:44:47.215: INFO: Created PVC efs-4439l9p2n, bound to PV directory-pvc-1 by dynamic provisioning
%!(EXTRA string=pvc-008e0453-562f-4010-8b89-d82460ce1786)Feb  4 14:44:57.559: INFO: ExecWithOptions {Command:[/bin/sh -c stat -c "%a" /mnt/volume1/dynamic_provisioning/pvc-008e0453-562f-4010-8b89-d82460ce1786] Namespace:efs-4439 PodName:pvc-tester-nxdgc ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
Feb  4 14:44:57.559: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
Feb  4 14:44:58.071: INFO: Perms Output: 755
Feb  4 14:44:58.288: INFO: Deleted StorageClass efs-4439l9p2n
[AfterEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
�[1mSTEP�[0m: Collecting events from namespace "efs-4439".
�[1mSTEP�[0m: Found 8 events.
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:41 +0000 UTC - event for directory-pvc-1: {efs.csi.aws.com_efs-csi-controller-6574c5f996-8wcbr_5adffd3a-4cd7-499c-9103-5f69a645c2ca } Provisioning: External provisioner is provisioning volume for claim "efs-4439/directory-pvc-1"
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:41 +0000 UTC - event for directory-pvc-1: {persistentvolume-controller } ExternalProvisioning: waiting for a volume to be created, either by external provisioner "efs.csi.aws.com" or manually created by system administrator
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:42 +0000 UTC - event for directory-pvc-1: {efs.csi.aws.com_efs-csi-controller-6574c5f996-8wcbr_5adffd3a-4cd7-499c-9103-5f69a645c2ca } ProvisioningSucceeded: Successfully provisioned volume pvc-008e0453-562f-4010-8b89-d82460ce1786
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:47 +0000 UTC - event for pvc-tester-nxdgc: {default-scheduler } FailedScheduling: 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:55 +0000 UTC - event for pvc-tester-nxdgc: {default-scheduler } Scheduled: Successfully assigned efs-4439/pvc-tester-nxdgc to ip-172-20-109-214.us-west-2.compute.internal
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:56 +0000 UTC - event for pvc-tester-nxdgc: {kubelet ip-172-20-109-214.us-west-2.compute.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/busybox:1.29-1" already present on machine
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:56 +0000 UTC - event for pvc-tester-nxdgc: {kubelet ip-172-20-109-214.us-west-2.compute.internal} Created: Created container write-pod
Feb  4 14:44:58.357: INFO: At 2023-02-04 14:44:56 +0000 UTC - event for pvc-tester-nxdgc: {kubelet ip-172-20-109-214.us-west-2.compute.internal} Started: Started container write-pod
Feb  4 14:44:58.425: INFO: POD               NODE                                          PHASE    GRACE  CONDITIONS
Feb  4 14:44:58.425: INFO: pvc-tester-nxdgc  ip-172-20-109-214.us-west-2.compute.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-02-04 14:44:55 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-02-04 14:44:57 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-02-04 14:44:57 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-02-04 14:44:55 +0000 UTC  }]
Feb  4 14:44:58.425: INFO: 
Feb  4 14:44:58.495: INFO: 
Logging node info for node ip-172-20-109-214.us-west-2.compute.internal
Feb  4 14:44:58.565: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-109-214.us-west-2.compute.internal    e3aa7e0a-0882-4c0d-976a-c67649bc7caf 2056 0 2023-02-04 14:39:52 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:c5.large beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-west-2 failure-domain.beta.kubernetes.io/zone:us-west-2c kops.k8s.io/instancegroup:nodes-us-west-2c kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-109-214.us-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:c5.large topology.kubernetes.io/region:us-west-2 topology.kubernetes.io/zone:us-west-2c] map[csi.volume.kubernetes.io/nodeid:{"efs.csi.aws.com":"i-08abf96f38d73d75f"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2023-02-04 14:39:52 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-02-04 14:40:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} } {kubelet Update v1 2023-02-04 14:40:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"ExternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"ExternalIP\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}} }]},Spec:NodeSpec{PodCIDR:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-2c/i-08abf96f38d73d75f,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3862945792 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3758088192 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-02-04 14:40:00 +0000 UTC,LastTransitionTime:2023-02-04 14:40:00 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:52 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:52 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:52 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:40:02 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.109.214,},NodeAddress{Type:ExternalIP,Address:35.92.73.2,},NodeAddress{Type:Hostname,Address:ip-172-20-109-214.us-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-109-214.us-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-35-92-73-2.us-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec220b9ee5fe91b706ee217ae9ee333f,SystemUUID:ec220b9e-e5fe-91b7-06ee-217ae9ee333f,BootID:cb758430-0e73-4b51-91b5-a449b2cc6b50,KernelVersion:5.15.0-1028-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.20.8,KubeProxyVersion:v1.20.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver@sha256:e82fe3e56dc252814d8f3f8103d97fdd4bf1325ec9d6605e27cbe69680aa20d8 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:32766],SizeBytes:501599518,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/jessie-dnsutils@sha256:702a992280fb7c3303e84a5801acbb4c9c7fcf48cffe0e9c8be3f0c60f74cf89 k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.4],SizeBytes:112029652,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:0c867c82a0a8ce6d093595f9d2e4b10517d6c9c26323075de9d82d9f7d056bfc k8s.gcr.io/kube-proxy:v1.20.8],SizeBytes:52056682,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:758db666ac7028534dba72e7e9bb1e57bb81b8196f976f7a5cc351ef8b3529e1 k8s.gcr.io/e2e-test-images/agnhost:2.32],SizeBytes:50002177,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar@sha256:ac2e6e8847edb7eb98b67fc6a9aaa3e270bb4abdf9e17e2fbc4cf9811fb85ec3 public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar:v2.6.1-eks-1-23-8],SizeBytes:6552778,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe@sha256:9977e7ff7147156f7cc67910d28f6085d2faba4b622a098d9e2ce696897172c8 public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe:v2.8.0-eks-1-23-8],SizeBytes:6005898,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Feb  4 14:44:58.565: INFO: 
Logging kubelet events for node ip-172-20-109-214.us-west-2.compute.internal
Feb  4 14:44:58.637: INFO: 
Logging pods the kubelet thinks is on node ip-172-20-109-214.us-west-2.compute.internal
Feb  4 14:44:58.715: INFO: coredns-8f5559c9b-ws6cv started at 2023-02-04 14:40:04 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Container coredns ready: true, restart count 0
Feb  4 14:44:58.715: INFO: efs-csi-node-4ghp6 started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Container csi-driver-registrar ready: true, restart count 0
Feb  4 14:44:58.715: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:44:58.715: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:44:58.715: INFO: efs-io-client started at 2023-02-04 14:44:40 +0000 UTC (1+1 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Init container efs-io-init ready: true, restart count 0
Feb  4 14:44:58.715: INFO: 	Container efs-io-client ready: false, restart count 0
Feb  4 14:44:58.715: INFO: pod-435c8bfe-d944-4aa5-b208-154c62d09536 started at 2023-02-04 14:44:41 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Container write-pod ready: false, restart count 0
Feb  4 14:44:58.715: INFO: pvc-tester-nxdgc started at 2023-02-04 14:44:55 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Container write-pod ready: true, restart count 0
Feb  4 14:44:58.715: INFO: kube-proxy-ip-172-20-109-214.us-west-2.compute.internal started at 2023-02-04 14:39:19 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:58.715: INFO: 	Container kube-proxy ready: true, restart count 0
Feb  4 14:44:59.053: INFO: 
Latency metrics for node ip-172-20-109-214.us-west-2.compute.internal
Feb  4 14:44:59.053: INFO: 
Logging node info for node ip-172-20-35-110.us-west-2.compute.internal
Feb  4 14:44:59.121: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-35-110.us-west-2.compute.internal    450fdd30-effb-410b-a5e5-b7235662f6ce 889 0 2023-02-04 14:38:36 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-west-2 failure-domain.beta.kubernetes.io/zone:us-west-2a kops.k8s.io/instancegroup:master-us-west-2a kops.k8s.io/kops-controller-pki: kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-35-110.us-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:master node-role.kubernetes.io/control-plane: node-role.kubernetes.io/master: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:t3.medium topology.kubernetes.io/region:us-west-2 topology.kubernetes.io/zone:us-west-2a] map[csi.volume.kubernetes.io/nodeid:{"efs.csi.aws.com":"i-014ff7d8b9270b56f"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{protokube Update v1 2023-02-04 14:38:41 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/kops-controller-pki":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/control-plane":{},"f:node-role.kubernetes.io/master":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {kube-controller-manager Update v1 2023-02-04 14:38:52 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.0.0/24\"":{}},"f:taints":{}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} } {kops-controller Update v1 2023-02-04 14:38:56 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{}}}} } {kubelet Update v1 2023-02-04 14:40:48 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"ExternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"ExternalIP\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}} }]},Spec:NodeSpec{PodCIDR:100.96.0.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-2a/i-014ff7d8b9270b56f,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[100.96.0.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{66404147200 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4051685376 0} {<nil>} 3956724Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{59763732382 0} {<nil>} 59763732382 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3946827776 0} {<nil>} 3854324Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-02-04 14:39:00 +0000 UTC,LastTransitionTime:2023-02-04 14:39:00 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-02-04 14:40:57 +0000 UTC,LastTransitionTime:2023-02-04 14:38:31 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-02-04 14:40:57 +0000 UTC,LastTransitionTime:2023-02-04 14:38:31 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-02-04 14:40:57 +0000 UTC,LastTransitionTime:2023-02-04 14:38:31 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-02-04 14:40:57 +0000 UTC,LastTransitionTime:2023-02-04 14:38:50 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.35.110,},NodeAddress{Type:ExternalIP,Address:54.191.51.55,},NodeAddress{Type:Hostname,Address:ip-172-20-35-110.us-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-35-110.us-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-191-51-55.us-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec25b5cdf98bbfc0aa2db51968d5166c,SystemUUID:ec25b5cd-f98b-bfc0-aa2d-b51968d5166c,BootID:34f40370-2e1d-409e-9a97-e3bd5880d48f,KernelVersion:5.15.0-1028-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.20.8,KubeProxyVersion:v1.20.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver@sha256:e82fe3e56dc252814d8f3f8103d97fdd4bf1325ec9d6605e27cbe69680aa20d8 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:32766],SizeBytes:501599518,},ContainerImage{Names:[k8s.gcr.io/etcdadm/etcd-manager@sha256:ebb73d3d4a99da609f9e01c556cd9f9aa7a0aecba8f5bc5588d7c45eb38e3a7e k8s.gcr.io/etcdadm/etcd-manager:3.0.20210430],SizeBytes:171082409,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:0c867c82a0a8ce6d093595f9d2e4b10517d6c9c26323075de9d82d9f7d056bfc k8s.gcr.io/kube-proxy:v1.20.8],SizeBytes:52056682,},ContainerImage{Names:[k8s.gcr.io/kops/dns-controller@sha256:f3724709f264bd47d2251f4ec5b16ec5482e8a2d65da006cd3165eb4da0bd3d1 k8s.gcr.io/kops/dns-controller:1.21.0],SizeBytes:40960953,},ContainerImage{Names:[k8s.gcr.io/kops/kops-controller@sha256:05b7d6511df0084aed954a009099402d2a7e7227adf0f410c4583204e6f76429 k8s.gcr.io/kops/kops-controller:1.21.0],SizeBytes:40618104,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver@sha256:531ffd92bd954f5c27002ce11502771146e7c867c09a6e1755631953ff584df4 k8s.gcr.io/kube-apiserver:v1.20.8],SizeBytes:30462643,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager@sha256:13509f0b36bbd4d2d142cf4c35d77f32ec3728975d96cf833b60b484effa8c43 k8s.gcr.io/kube-controller-manager:v1.20.8],SizeBytes:29554511,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler@sha256:6fc53cbc3f035ba2b0ac9127e9dc5aa7a95b73f041f7cc14c36cdfc095b13080 k8s.gcr.io/kube-scheduler:v1.20.8],SizeBytes:14243733,},ContainerImage{Names:[k8s.gcr.io/kops/kube-apiserver-healthcheck@sha256:d772e49a0ae9dea319f26aaa40d58a123860b19da6378d29898eb30208359241 k8s.gcr.io/kops/kube-apiserver-healthcheck:1.21.0],SizeBytes:11771024,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar@sha256:ac2e6e8847edb7eb98b67fc6a9aaa3e270bb4abdf9e17e2fbc4cf9811fb85ec3 public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar:v2.6.1-eks-1-23-8],SizeBytes:6552778,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe@sha256:9977e7ff7147156f7cc67910d28f6085d2faba4b622a098d9e2ce696897172c8 public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe:v2.8.0-eks-1-23-8],SizeBytes:6005898,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Feb  4 14:44:59.121: INFO: 
Logging kubelet events for node ip-172-20-35-110.us-west-2.compute.internal
Feb  4 14:44:59.216: INFO: 
Logging pods the kubelet thinks is on node ip-172-20-35-110.us-west-2.compute.internal
Feb  4 14:44:59.305: INFO: kube-apiserver-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+2 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container healthcheck ready: true, restart count 0
Feb  4 14:44:59.305: INFO: 	Container kube-apiserver ready: true, restart count 1
Feb  4 14:44:59.305: INFO: kube-controller-manager-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container kube-controller-manager ready: true, restart count 0
Feb  4 14:44:59.305: INFO: kube-proxy-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container kube-proxy ready: true, restart count 0
Feb  4 14:44:59.305: INFO: etcd-manager-main-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container etcd-manager ready: true, restart count 0
Feb  4 14:44:59.305: INFO: kube-scheduler-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container kube-scheduler ready: true, restart count 0
Feb  4 14:44:59.305: INFO: kops-controller-xrjjk started at 2023-02-04 14:38:52 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container kops-controller ready: true, restart count 0
Feb  4 14:44:59.305: INFO: dns-controller-5d59c585d8-j6qg6 started at 2023-02-04 14:38:53 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container dns-controller ready: true, restart count 0
Feb  4 14:44:59.305: INFO: efs-csi-node-887v6 started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container csi-driver-registrar ready: true, restart count 0
Feb  4 14:44:59.305: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:44:59.305: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:44:59.305: INFO: etcd-manager-events-ip-172-20-35-110.us-west-2.compute.internal started at 2023-02-04 14:37:50 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:44:59.305: INFO: 	Container etcd-manager ready: true, restart count 0
Feb  4 14:44:59.822: INFO: 
Latency metrics for node ip-172-20-35-110.us-west-2.compute.internal
Feb  4 14:44:59.822: INFO: 
Logging node info for node ip-172-20-51-74.us-west-2.compute.internal
Feb  4 14:44:59.894: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-51-74.us-west-2.compute.internal    2bba1f67-9469-4ae9-8300-49481b15243a 2040 0 2023-02-04 14:39:51 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:c5.large beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-west-2 failure-domain.beta.kubernetes.io/zone:us-west-2a kops.k8s.io/instancegroup:nodes-us-west-2a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-51-74.us-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:c5.large topology.kubernetes.io/region:us-west-2 topology.kubernetes.io/zone:us-west-2a] map[csi.volume.kubernetes.io/nodeid:{"efs.csi.aws.com":"i-06e68d6b3259cb03e"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2023-02-04 14:39:51 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-02-04 14:40:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} } {kubelet Update v1 2023-02-04 14:40:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"ExternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"ExternalIP\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}} }]},Spec:NodeSpec{PodCIDR:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-2a/i-06e68d6b3259cb03e,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3892305920 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3787448320 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-02-04 14:40:00 +0000 UTC,LastTransitionTime:2023-02-04 14:40:00 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:51 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:51 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:51 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-02-04 14:44:22 +0000 UTC,LastTransitionTime:2023-02-04 14:39:59 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.51.74,},NodeAddress{Type:ExternalIP,Address:54.244.209.43,},NodeAddress{Type:Hostname,Address:ip-172-20-51-74.us-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-51-74.us-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-244-209-43.us-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2d1965d36b6407649f40521dceba18,SystemUUID:ec2d1965-d36b-6407-649f-40521dceba18,BootID:4dace727-4f9f-4246-8af9-80b909169801,KernelVersion:5.15.0-1028-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.20.8,KubeProxyVersion:v1.20.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver@sha256:e82fe3e56dc252814d8f3f8103d97fdd4bf1325ec9d6605e27cbe69680aa20d8 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:32766],SizeBytes:501599518,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/jessie-dnsutils@sha256:702a992280fb7c3303e84a5801acbb4c9c7fcf48cffe0e9c8be3f0c60f74cf89 k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.4],SizeBytes:112029652,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:0c867c82a0a8ce6d093595f9d2e4b10517d6c9c26323075de9d82d9f7d056bfc k8s.gcr.io/kube-proxy:v1.20.8],SizeBytes:52056682,},ContainerImage{Names:[k8s.gcr.io/cpa/cluster-proportional-autoscaler@sha256:67640771ad9fc56f109d5b01e020f0c858e7c890bb0eb15ba0ebd325df3285e7 k8s.gcr.io/cpa/cluster-proportional-autoscaler:1.8.3],SizeBytes:15191740,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/external-provisioner@sha256:968bbebc038892e1685f187feffbeccc13e327ab1672fb3ab332cca835085cd1 public.ecr.aws/eks-distro/kubernetes-csi/external-provisioner:v3.3.0-eks-1-23-8],SizeBytes:13992487,},ContainerImage{Names:[docker.io/coredns/coredns@sha256:642ff9910da6ea9a8624b0234eef52af9ca75ecbec474c5507cb096bdfbae4e5 docker.io/coredns/coredns:1.8.3],SizeBytes:12893350,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar@sha256:ac2e6e8847edb7eb98b67fc6a9aaa3e270bb4abdf9e17e2fbc4cf9811fb85ec3 public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar:v2.6.1-eks-1-23-8],SizeBytes:6552778,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe@sha256:9977e7ff7147156f7cc67910d28f6085d2faba4b622a098d9e2ce696897172c8 public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe:v2.8.0-eks-1-23-8],SizeBytes:6005898,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Feb  4 14:44:59.897: INFO: 
Logging kubelet events for node ip-172-20-51-74.us-west-2.compute.internal
Feb  4 14:44:59.972: INFO: 
Logging pods the kubelet thinks is on node ip-172-20-51-74.us-west-2.compute.internal
Feb  4 14:45:00.057: INFO: kube-proxy-ip-172-20-51-74.us-west-2.compute.internal started at 2023-02-04 14:39:18 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:45:00.057: INFO: 	Container kube-proxy ready: true, restart count 0
Feb  4 14:45:00.057: INFO: coredns-autoscaler-6f594f4c58-q6gfp started at 2023-02-04 14:40:01 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:45:00.057: INFO: 	Container autoscaler ready: true, restart count 0
Feb  4 14:45:00.057: INFO: coredns-8f5559c9b-w5xd7 started at 2023-02-04 14:40:02 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:45:00.057: INFO: 	Container coredns ready: true, restart count 0
Feb  4 14:45:00.057: INFO: efs-csi-node-z7n7w started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:45:00.057: INFO: 	Container csi-driver-registrar ready: true, restart count 0
Feb  4 14:45:00.057: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:45:00.057: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:45:00.057: INFO: efs-csi-controller-6574c5f996-8wcbr started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:45:00.057: INFO: 	Container csi-provisioner ready: true, restart count 0
Feb  4 14:45:00.057: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:45:00.057: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:45:00.332: INFO: 
Latency metrics for node ip-172-20-51-74.us-west-2.compute.internal
Feb  4 14:45:00.332: INFO: 
Logging node info for node ip-172-20-82-122.us-west-2.compute.internal
Feb  4 14:45:00.400: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-82-122.us-west-2.compute.internal    fd4b7a6f-c63d-4f3f-b445-431e2fed0b61 2073 0 2023-02-04 14:39:54 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:c5.large beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-west-2 failure-domain.beta.kubernetes.io/zone:us-west-2b kops.k8s.io/instancegroup:nodes-us-west-2b kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-82-122.us-west-2.compute.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:c5.large topology.kubernetes.io/region:us-west-2 topology.kubernetes.io/zone:us-west-2b] map[csi.volume.kubernetes.io/nodeid:{"efs.csi.aws.com":"i-0830a5883d972f25d"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] []  [{kops-controller Update v1 2023-02-04 14:39:54 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/instancegroup":{},"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-02-04 14:40:00 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} } {kubelet Update v1 2023-02-04 14:40:45 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:csi.volume.kubernetes.io/nodeid":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}},"f:status":{"f:addresses":{".":{},"k:{\"type\":\"ExternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"ExternalIP\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"Hostname\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalDNS\"}":{".":{},"f:address":{},"f:type":{}},"k:{\"type\":\"InternalIP\"}":{".":{},"f:address":{},"f:type":{}}},"f:allocatable":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:capacity":{".":{},"f:attachable-volumes-aws-ebs":{},"f:cpu":{},"f:ephemeral-storage":{},"f:hugepages-1Gi":{},"f:hugepages-2Mi":{},"f:memory":{},"f:pods":{}},"f:conditions":{".":{},"k:{\"type\":\"DiskPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"MemoryPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"PIDPressure\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:daemonEndpoints":{"f:kubeletEndpoint":{"f:Port":{}}},"f:images":{},"f:nodeInfo":{"f:architecture":{},"f:bootID":{},"f:containerRuntimeVersion":{},"f:kernelVersion":{},"f:kubeProxyVersion":{},"f:kubeletVersion":{},"f:machineID":{},"f:operatingSystem":{},"f:osImage":{},"f:systemUUID":{}}}} }]},Spec:NodeSpec{PodCIDR:100.96.3.0/24,DoNotUseExternalID:,ProviderID:aws:///us-west-2b/i-0830a5883d972f25d,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>}  BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3862937600 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-aws-ebs: {{25 0} {<nil>} 25 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3758080000 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-02-04 14:40:00 +0000 UTC,LastTransitionTime:2023-02-04 14:40:00 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:24 +0000 UTC,LastTransitionTime:2023-02-04 14:39:54 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:24 +0000 UTC,LastTransitionTime:2023-02-04 14:39:54 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-02-04 14:44:24 +0000 UTC,LastTransitionTime:2023-02-04 14:39:54 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-02-04 14:44:24 +0000 UTC,LastTransitionTime:2023-02-04 14:40:04 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.82.122,},NodeAddress{Type:ExternalIP,Address:54.212.208.68,},NodeAddress{Type:Hostname,Address:ip-172-20-82-122.us-west-2.compute.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-82-122.us-west-2.compute.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-212-208-68.us-west-2.compute.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec293cf2ec0f963318027a44676a8e80,SystemUUID:ec293cf2-ec0f-9633-1802-7a44676a8e80,BootID:b69dd774-0c4e-4a2a-a396-08b333343c6c,KernelVersion:5.15.0-1028-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:containerd://1.4.6,KubeletVersion:v1.20.8,KubeProxyVersion:v1.20.8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver@sha256:e82fe3e56dc252814d8f3f8103d97fdd4bf1325ec9d6605e27cbe69680aa20d8 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:32766],SizeBytes:501599518,},ContainerImage{Names:[k8s.gcr.io/kube-proxy@sha256:0c867c82a0a8ce6d093595f9d2e4b10517d6c9c26323075de9d82d9f7d056bfc k8s.gcr.io/kube-proxy:v1.20.8],SizeBytes:52056682,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:758db666ac7028534dba72e7e9bb1e57bb81b8196f976f7a5cc351ef8b3529e1 k8s.gcr.io/e2e-test-images/agnhost:2.32],SizeBytes:50002177,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/external-provisioner@sha256:968bbebc038892e1685f187feffbeccc13e327ab1672fb3ab332cca835085cd1 public.ecr.aws/eks-distro/kubernetes-csi/external-provisioner:v3.3.0-eks-1-23-8],SizeBytes:13992487,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar@sha256:ac2e6e8847edb7eb98b67fc6a9aaa3e270bb4abdf9e17e2fbc4cf9811fb85ec3 public.ecr.aws/eks-distro/kubernetes-csi/node-driver-registrar:v2.6.1-eks-1-23-8],SizeBytes:6552778,},ContainerImage{Names:[public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe@sha256:9977e7ff7147156f7cc67910d28f6085d2faba4b622a098d9e2ce696897172c8 public.ecr.aws/eks-distro/kubernetes-csi/livenessprobe:v2.8.0-eks-1-23-8],SizeBytes:6005898,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:732746,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:927d98197ec1141a368550822d18fa1c60bdae27b78b0c004f705f548c07814f k8s.gcr.io/pause:3.2],SizeBytes:299513,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Feb  4 14:45:00.400: INFO: 
Logging kubelet events for node ip-172-20-82-122.us-west-2.compute.internal
Feb  4 14:45:00.471: INFO: 
Logging pods the kubelet thinks is on node ip-172-20-82-122.us-west-2.compute.internal
Feb  4 14:45:00.542: INFO: kube-proxy-ip-172-20-82-122.us-west-2.compute.internal started at 2023-02-04 14:39:20 +0000 UTC (0+1 container statuses recorded)
Feb  4 14:45:00.542: INFO: 	Container kube-proxy ready: true, restart count 0
Feb  4 14:45:00.542: INFO: efs-csi-node-6dk7s started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:45:00.542: INFO: 	Container csi-driver-registrar ready: true, restart count 0
Feb  4 14:45:00.542: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:45:00.542: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:45:00.542: INFO: efs-csi-controller-6574c5f996-scpzt started at 2023-02-04 14:40:25 +0000 UTC (0+3 container statuses recorded)
Feb  4 14:45:00.542: INFO: 	Container csi-provisioner ready: true, restart count 0
Feb  4 14:45:00.542: INFO: 	Container efs-plugin ready: true, restart count 0
Feb  4 14:45:00.542: INFO: 	Container liveness-probe ready: true, restart count 0
Feb  4 14:45:00.810: INFO: 
Latency metrics for node ip-172-20-82-122.us-west-2.compute.internal
Feb  4 14:45:00.810: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
�[1mSTEP�[0m: Destroying namespace "efs-4439" for this suite.

				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid

Show 153 Skipped Tests

Error lines from build-log.txt

Raw build-log.txt

... skipping 326 lines ...
#11 3.159 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.amzn2.0.1.x86_64
#11 3.159 ---> Package perl-File-Temp.noarch 0:0.23.01-3.amzn2 will be installed
#11 3.162 ---> Package perl-Getopt-Long.noarch 0:2.40-3.amzn2 will be installed
#11 3.162 --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#11 3.163 --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.amzn2.noarch
#11 3.164 ---> Package perl-Git.noarch 0:2.39.1-1.amzn2.0.1 will be installed
#11 3.165 --> Processing Dependency: perl(Error) for package: perl-Git-2.39.1-1.amzn2.0.1.noarch
#11 3.166 ---> Package perl-PathTools.x86_64 0:3.40-5.amzn2.0.2 will be installed
#11 3.167 ---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
#11 3.169 ---> Package perl-Thread-Queue.noarch 0:3.02-2.amzn2 will be installed
#11 3.170 ---> Package perl-threads.x86_64 0:1.87-4.amzn2.0.2 will be installed
#11 3.171 ---> Package pkgconfig.x86_64 1:0.27.1-4.amzn2.0.2 will be installed
#11 3.174 ---> Package system-rpm-config.noarch 0:9.1.0-76.amzn2.0.14 will be installed
... skipping 22 lines ...
#11 3.257 --> Processing Dependency: openssh = 7.4p1-22.amzn2.0.1 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 3.259 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 3.262 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 3.263 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.amzn2.0.1.x86_64
#11 3.266 ---> Package pcre2.x86_64 0:10.23-11.amzn2.0.1 will be installed
#11 3.268 ---> Package perl-Carp.noarch 0:1.26-244.amzn2 will be installed
#11 3.269 ---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
#11 3.271 ---> Package perl-Exporter.noarch 0:5.68-3.amzn2 will be installed
#11 3.272 ---> Package perl-File-Path.noarch 0:2.09-2.amzn2 will be installed
#11 3.273 ---> Package perl-Filter.x86_64 0:1.49-3.amzn2.0.2 will be installed
#11 3.276 ---> Package perl-Pod-Simple.noarch 1:3.28-4.amzn2 will be installed
#11 3.281 --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
#11 3.284 --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.amzn2.noarch
... skipping 161 lines ...
#11 3.753  pam                       x86_64 1.1.8-23.amzn2.0.1           amzn2-core 715 k
#11 3.753  patch                     x86_64 2.7.1-12.amzn2.0.2           amzn2-core 110 k
#11 3.753  pcre2                     x86_64 10.23-11.amzn2.0.1           amzn2-core 207 k
#11 3.753  perl                      x86_64 4:5.16.3-299.amzn2.0.1       amzn2-core 8.0 M
#11 3.753  perl-Carp                 noarch 1.26-244.amzn2               amzn2-core  19 k
#11 3.753  perl-Encode               x86_64 2.51-7.amzn2.0.2             amzn2-core 1.5 M
#11 3.753  perl-Error                noarch 1:0.17020-2.amzn2            amzn2-core  32 k
#11 3.753  perl-Exporter             noarch 5.68-3.amzn2                 amzn2-core  29 k
#11 3.753  perl-File-Path            noarch 2.09-2.amzn2                 amzn2-core  27 k
#11 3.753  perl-File-Temp            noarch 0.23.01-3.amzn2              amzn2-core  56 k
#11 3.753  perl-Filter               x86_64 1.49-3.amzn2.0.2             amzn2-core  76 k
#11 3.753  perl-Getopt-Long          noarch 2.40-3.amzn2                 amzn2-core  56 k
#11 3.753  perl-Git                  noarch 2.39.1-1.amzn2.0.1           amzn2-core  41 k
... skipping 87 lines ...
#11 9.152   Installing : 1:perl-Pod-Simple-3.28-4.amzn2.noarch                      34/87 
#11 9.201   Installing : perl-Getopt-Long-2.40-3.amzn2.noarch                       35/87 
#11 9.352   Installing : 4:perl-libs-5.16.3-299.amzn2.0.1.x86_64                    36/87 
#11 11.26   Installing : 4:perl-5.16.3-299.amzn2.0.1.x86_64                         37/87 
#11 11.32   Installing : perl-Thread-Queue-3.02-2.amzn2.noarch                      38/87 
#11 11.35   Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                  39/87 
#11 11.38   Installing : 1:perl-Error-0.17020-2.amzn2.noarch                        40/87 
#11 11.43   Installing : fipscheck-lib-1.4.1-6.amzn2.0.2.x86_64                     41/87 
#11 11.47   Installing : fipscheck-1.4.1-6.amzn2.0.2.x86_64                         42/87 
#11 11.51   Installing : dwz-0.11-3.amzn2.0.3.x86_64                                43/87 
#11 11.55   Installing : 1:pkgconfig-0.27.1-4.amzn2.0.2.x86_64                      44/87 
#11 11.59   Installing : kmod-libs-25-3.amzn2.0.2.x86_64                            45/87 
#11 11.66   Installing : unzip-6.0-57.amzn2.0.1.x86_64                              46/87 
... skipping 32 lines ...
#11 16.21   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             71/87 
#11 16.31   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       72/87 
#11 16.42   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         73/87 
#11 16.53   Installing : systemd-libs-219-78.amzn2.0.21.x86_64                      74/87 
#11 16.60   Installing : 1:dbus-libs-1.10.24-7.amzn2.0.2.x86_64                     75/87 
#11 18.12   Installing : systemd-219-78.amzn2.0.21.x86_64                           76/87 
#11 18.68 Failed to get D-Bus connection: Operation not permitted
#11 18.83   Installing : 1:dbus-1.10.24-7.amzn2.0.2.x86_64                          77/87 
#11 18.87   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           78/87 
#11 18.97   Installing : elfutils-0.176-2.amzn2.x86_64                              79/87 
#11 19.14   Installing : openssh-7.4p1-22.amzn2.0.1.x86_64                          80/87 
#11 19.31   Installing : openssh-clients-7.4p1-22.amzn2.0.1.x86_64                  81/87 
#11 21.20   Installing : git-core-2.39.1-1.amzn2.0.1.x86_64                         82/87 
... skipping 57 lines ...
#11 23.28   Verifying  : util-linux-2.30.2-2.amzn2.0.11.x86_64                      53/87 
#11 23.29   Verifying  : pam-1.1.8-23.amzn2.0.1.x86_64                              54/87 
#11 23.31   Verifying  : xz-5.2.2-1.amzn2.0.3.x86_64                                55/87 
#11 23.32   Verifying  : ustr-1.0.4-16.amzn2.0.3.x86_64                             56/87 
#11 23.34   Verifying  : less-458-9.amzn2.0.2.x86_64                                57/87 
#11 23.35   Verifying  : 1:perl-Pod-Escapes-1.04-299.amzn2.0.1.noarch               58/87 
#11 23.37   Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                        59/87 
#11 23.38   Verifying  : perl-Pod-Usage-1.63-3.amzn2.noarch                         60/87 
#11 23.40   Verifying  : 1:perl-parent-0.225-244.amzn2.0.1.noarch                   61/87 
#11 23.41   Verifying  : perl-Pod-Perldoc-3.20-4.amzn2.noarch                       62/87 
#11 23.42   Verifying  : 2:tar-1.26-35.amzn2.x86_64                                 63/87 
#11 23.44   Verifying  : zip-3.0-11.amzn2.0.2.x86_64                                64/87 
#11 23.45   Verifying  : 1:dbus-libs-1.10.24-7.amzn2.0.2.x86_64                     65/87 
... skipping 65 lines ...
#11 23.90   pam.x86_64 0:1.1.8-23.amzn2.0.1                                               
#11 23.90   patch.x86_64 0:2.7.1-12.amzn2.0.2                                             
#11 23.90   pcre2.x86_64 0:10.23-11.amzn2.0.1                                             
#11 23.90   perl.x86_64 4:5.16.3-299.amzn2.0.1                                            
#11 23.90   perl-Carp.noarch 0:1.26-244.amzn2                                             
#11 23.90   perl-Encode.x86_64 0:2.51-7.amzn2.0.2                                         
#11 23.90   perl-Error.noarch 1:0.17020-2.amzn2                                           
#11 23.90   perl-Exporter.noarch 0:5.68-3.amzn2                                           
#11 23.90   perl-File-Path.noarch 0:2.09-2.amzn2                                          
#11 23.90   perl-File-Temp.noarch 0:0.23.01-3.amzn2                                       
#11 23.90   perl-Filter.x86_64 0:1.49-3.amzn2.0.2                                         
#11 23.90   perl-Getopt-Long.noarch 0:2.40-3.amzn2                                        
#11 23.90   perl-Git.noarch 0:2.39.1-1.amzn2.0.1                                          
... skipping 522 lines ...
#19 exporting layers 2.9s done
#19 writing image sha256:abac05dddb58ec7e6e851593ecd0f2325f6f92e84b5ea430f9b9263956ca54ba done
#19 naming to 607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver:32766-linux-amd64-amazon done
#19 DONE 2.9s

#7 [builder 1/6] FROM docker.io/library/golang:1.17@sha256:87262e4a4c7db56158a80a18fefdc4fee5accc41b59cde821e691d05541bbb18
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
touch .image-32766-linux-amd64-amazon
make[1]: Leaving directory '/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver'
The push refers to repository [607362164682.dkr.ecr.us-west-2.amazonaws.com/aws-efs-csi-driver]
c375dbf7654e: Preparing
45844243e65d: Preparing
54d76f2927b2: Preparing
... skipping 118 lines ...
## Validating cluster test-cluster-32766.k8s.local
#
Using cluster from kubectl context: test-cluster-32766.k8s.local

Validating cluster test-cluster-32766.k8s.local

W0204 14:36:06.317637    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 14:36:16.358954    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 14:36:26.402227    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 14:36:36.437669    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-32766-k8-b3nnl5-344369786.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0204 14:36:58.213263    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0204 14:37:19.917585    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0204 14:37:41.593370    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0204 14:38:03.275585    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0204 14:38:24.958929    5528 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
nodes-us-west-2c	Node	c5.large	1	1	us-west-2c
... skipping 6 lines ...
KIND	NAME						MESSAGE
Machine	i-06e68d6b3259cb03e				machine "i-06e68d6b3259cb03e" has not yet joined cluster
Machine	i-0830a5883d972f25d				machine "i-0830a5883d972f25d" has not yet joined cluster
Machine	i-08abf96f38d73d75f				machine "i-08abf96f38d73d75f" has not yet joined cluster
Node	ip-172-20-35-110.us-west-2.compute.internal	node "ip-172-20-35-110.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0204 14:38:45.597907    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-08abf96f38d73d75f				machine "i-08abf96f38d73d75f" has not yet joined cluster
Node	ip-172-20-35-110.us-west-2.compute.internal	node "ip-172-20-35-110.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-w5xd7		system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending
Pod	kube-system/dns-controller-5d59c585d8-j6qg6	system-cluster-critical pod "dns-controller-5d59c585d8-j6qg6" is pending

Validation Failed
W0204 14:38:57.823344    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-w5xd7		system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending

Validation Failed
W0204 14:39:10.079581    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-08abf96f38d73d75f				machine "i-08abf96f38d73d75f" has not yet joined cluster
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-w5xd7		system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending

Validation Failed
W0204 14:39:22.194361    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-08abf96f38d73d75f				machine "i-08abf96f38d73d75f" has not yet joined cluster
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-35-110.us-west-2.compute.internal	master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-w5xd7		system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending

Validation Failed
W0204 14:39:34.342273    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-08abf96f38d73d75f								machine "i-08abf96f38d73d75f" has not yet joined cluster
Node	ip-172-20-35-110.us-west-2.compute.internal					master "ip-172-20-35-110.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-w5xd7						system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-35-110.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-35-110.us-west-2.compute.internal" is pending

Validation Failed
W0204 14:39:46.467818    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-109-214.us-west-2.compute.internal	node "ip-172-20-109-214.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-74.us-west-2.compute.internal	node "ip-172-20-51-74.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-82-122.us-west-2.compute.internal	node "ip-172-20-82-122.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-w5xd7		system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-q6gfp	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-q6gfp" is pending

Validation Failed
W0204 14:39:58.468989    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 8 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-w5xd7	system-cluster-critical pod "coredns-8f5559c9b-w5xd7" is not ready (coredns)
Pod	kube-system/coredns-8f5559c9b-ws6cv	system-cluster-critical pod "coredns-8f5559c9b-ws6cv" is not ready (coredns)

Validation Failed
W0204 14:40:10.685749    5528 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 167 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:43:33.245: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 14:43:33.589: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:43:33.590: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
[1mSTEP[0m: Destroying namespace "volumemode-495" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (filesystem volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail to use a volume in a pod with mismatched mode [Slow] [It][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297[0m

      [36mDriver "efs.csi.aws.com" does not provide raw block - skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
[90m------------------------------[0m
... skipping 119 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256[0m

      [36mDriver efs.csi.aws.com doesn't support ntfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
... skipping 511 lines ...
Feb  4 14:43:39.209: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:43:39.278: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comrgw54] to have phase Bound
Feb  4 14:43:39.350: INFO: PersistentVolumeClaim efs.csi.aws.comrgw54 found but phase is Pending instead of Bound.
Feb  4 14:43:41.419: INFO: PersistentVolumeClaim efs.csi.aws.comrgw54 found and phase=Bound (2.14007621s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-484j
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:43:41.629: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-484j" in namespace "provisioning-5094" to be "Succeeded or Failed"
Feb  4 14:43:41.696: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 67.120669ms
Feb  4 14:43:43.765: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135799387s
Feb  4 14:43:45.834: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.204559814s
Feb  4 14:43:47.901: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.272283873s
Feb  4 14:43:49.970: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.341343675s
Feb  4 14:43:52.040: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.410436358s
Feb  4 14:43:54.108: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 12.478434659s
Feb  4 14:43:56.176: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 14.546617089s
Feb  4 14:43:58.245: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 16.615409306s
Feb  4 14:44:00.320: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 18.690636431s
Feb  4 14:44:02.388: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Pending", Reason="", readiness=false. Elapsed: 20.758946351s
Feb  4 14:44:04.456: INFO: Pod "pod-subpath-test-dynamicpv-484j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.826542275s
[1mSTEP[0m: Saw pod success
Feb  4 14:44:04.456: INFO: Pod "pod-subpath-test-dynamicpv-484j" satisfied condition "Succeeded or Failed"
Feb  4 14:44:04.523: INFO: Trying to get logs from node ip-172-20-82-122.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-484j container test-container-subpath-dynamicpv-484j: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:44:04.673: INFO: Waiting for pod pod-subpath-test-dynamicpv-484j to disappear
Feb  4 14:44:04.744: INFO: Pod pod-subpath-test-dynamicpv-484j no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-484j
Feb  4 14:44:04.744: INFO: Deleting pod "pod-subpath-test-dynamicpv-484j" in namespace "provisioning-5094"
... skipping 48 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278[0m

      [36mDriver efs.csi.aws.com doesn't support ntfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
... skipping 20 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240[0m

      [36mDriver supports dynamic provisioning, skipping PreprovisionedPV pattern[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
[90m------------------------------[0m
... skipping 86 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Inline-volume (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278[0m

      [36mDriver efs.csi.aws.com doesn't support InlineVolume -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
[90m------------------------------[0m
... skipping 363 lines ...

      [36mDriver efs.csi.aws.com doesn't support xfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Dynamic PV (default fs)] subPath[0m 
  [1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:44:02.746: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename provisioning
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath directory is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240
Feb  4 14:44:03.268: INFO: Creating resource for dynamic PV
Feb  4 14:44:03.269: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
[1mSTEP[0m: creating a StorageClass 
[1mSTEP[0m: creating a claim
Feb  4 14:44:03.335: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:44:03.403: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comk42sf] to have phase Bound
Feb  4 14:44:03.469: INFO: PersistentVolumeClaim efs.csi.aws.comk42sf found but phase is Pending instead of Bound.
Feb  4 14:44:05.536: INFO: PersistentVolumeClaim efs.csi.aws.comk42sf found and phase=Bound (2.133004358s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-56qn
[1mSTEP[0m: Checking for subpath error in container status
Feb  4 14:44:09.867: INFO: Deleting pod "pod-subpath-test-dynamicpv-56qn" in namespace "provisioning-2888"
Feb  4 14:44:09.934: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-56qn" to be fully deleted
[1mSTEP[0m: Deleting pod
Feb  4 14:44:20.066: INFO: Deleting pod "pod-subpath-test-dynamicpv-56qn" in namespace "provisioning-2888"
[1mSTEP[0m: Deleting pvc
Feb  4 14:44:20.131: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comk42sf"
... skipping 15 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail if subpath directory is outside the volume [Slow][LinuxOnly]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240[0m
[90m------------------------------[0m
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:44:26.017: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 14:44:26.381: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:44:26.382: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
[1mSTEP[0m: Destroying namespace "volumemode-631" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail to use a volume in a pod with mismatched mode [Slow] [It][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297[0m

      [36mDriver "efs.csi.aws.com" does not provide raw block - skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
[90m------------------------------[0m
... skipping 92 lines ...
Feb  4 14:44:23.715: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:44:23.785: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comt5pzn] to have phase Bound
Feb  4 14:44:23.853: INFO: PersistentVolumeClaim efs.csi.aws.comt5pzn found but phase is Pending instead of Bound.
Feb  4 14:44:25.921: INFO: PersistentVolumeClaim efs.csi.aws.comt5pzn found and phase=Bound (2.135198045s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-7p6w
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:44:26.150: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-7p6w" in namespace "provisioning-9703" to be "Succeeded or Failed"
Feb  4 14:44:26.221: INFO: Pod "pod-subpath-test-dynamicpv-7p6w": Phase="Pending", Reason="", readiness=false. Elapsed: 70.496985ms
Feb  4 14:44:28.290: INFO: Pod "pod-subpath-test-dynamicpv-7p6w": Phase="Pending", Reason="", readiness=false. Elapsed: 2.139548366s
Feb  4 14:44:30.359: INFO: Pod "pod-subpath-test-dynamicpv-7p6w": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.208727395s
[1mSTEP[0m: Saw pod success
Feb  4 14:44:30.359: INFO: Pod "pod-subpath-test-dynamicpv-7p6w" satisfied condition "Succeeded or Failed"
Feb  4 14:44:30.426: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-7p6w container test-container-subpath-dynamicpv-7p6w: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:44:30.570: INFO: Waiting for pod pod-subpath-test-dynamicpv-7p6w to disappear
Feb  4 14:44:30.637: INFO: Pod pod-subpath-test-dynamicpv-7p6w no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-7p6w
Feb  4 14:44:30.637: INFO: Deleting pod "pod-subpath-test-dynamicpv-7p6w" in namespace "provisioning-9703"
... skipping 772 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267[0m

      [36mDriver efs.csi.aws.com doesn't support ntfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
... skipping 125 lines ...
Feb  4 14:45:13.120: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:45:13.189: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com8jbns] to have phase Bound
Feb  4 14:45:13.256: INFO: PersistentVolumeClaim efs.csi.aws.com8jbns found but phase is Pending instead of Bound.
Feb  4 14:45:15.334: INFO: PersistentVolumeClaim efs.csi.aws.com8jbns found and phase=Bound (2.144999816s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-rdnh
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:45:15.547: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rdnh" in namespace "provisioning-856" to be "Succeeded or Failed"
Feb  4 14:45:15.615: INFO: Pod "pod-subpath-test-dynamicpv-rdnh": Phase="Pending", Reason="", readiness=false. Elapsed: 67.767659ms
Feb  4 14:45:17.683: INFO: Pod "pod-subpath-test-dynamicpv-rdnh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135770442s
Feb  4 14:45:19.753: INFO: Pod "pod-subpath-test-dynamicpv-rdnh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.205468277s
[1mSTEP[0m: Saw pod success
Feb  4 14:45:19.753: INFO: Pod "pod-subpath-test-dynamicpv-rdnh" satisfied condition "Succeeded or Failed"
Feb  4 14:45:19.820: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-rdnh container test-container-subpath-dynamicpv-rdnh: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:45:19.963: INFO: Waiting for pod pod-subpath-test-dynamicpv-rdnh to disappear
Feb  4 14:45:20.035: INFO: Pod pod-subpath-test-dynamicpv-rdnh no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-rdnh
Feb  4 14:45:20.035: INFO: Deleting pod "pod-subpath-test-dynamicpv-rdnh" in namespace "provisioning-856"
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-rdnh
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:45:20.171: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-rdnh" in namespace "provisioning-856" to be "Succeeded or Failed"
Feb  4 14:45:20.240: INFO: Pod "pod-subpath-test-dynamicpv-rdnh": Phase="Pending", Reason="", readiness=false. Elapsed: 69.472914ms
Feb  4 14:45:22.308: INFO: Pod "pod-subpath-test-dynamicpv-rdnh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.137446839s
[1mSTEP[0m: Saw pod success
Feb  4 14:45:22.309: INFO: Pod "pod-subpath-test-dynamicpv-rdnh" satisfied condition "Succeeded or Failed"
Feb  4 14:45:22.375: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-rdnh container test-container-subpath-dynamicpv-rdnh: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:45:22.516: INFO: Waiting for pod pod-subpath-test-dynamicpv-rdnh to disappear
Feb  4 14:45:22.586: INFO: Pod pod-subpath-test-dynamicpv-rdnh no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-rdnh
Feb  4 14:45:22.586: INFO: Deleting pod "pod-subpath-test-dynamicpv-rdnh" in namespace "provisioning-856"
... skipping 157 lines ...
Feb  4 14:45:36.755: INFO: PersistentVolumeClaim pvc-b56tf found but phase is Pending instead of Bound.
Feb  4 14:45:38.823: INFO: PersistentVolumeClaim pvc-b56tf found and phase=Bound (14.568981354s)
Feb  4 14:45:38.823: INFO: Waiting up to 3m0s for PersistentVolume efs.csi.aws.com-nx6tk to have phase Bound
Feb  4 14:45:38.890: INFO: PersistentVolume efs.csi.aws.com-nx6tk found and phase=Bound (67.127962ms)
[1mSTEP[0m: Creating pod exec-volume-test-preprovisionedpv-5ls7
[1mSTEP[0m: Creating a pod to test exec-volume-test
Feb  4 14:45:39.099: INFO: Waiting up to 5m0s for pod "exec-volume-test-preprovisionedpv-5ls7" in namespace "volume-5931" to be "Succeeded or Failed"
Feb  4 14:45:39.166: INFO: Pod "exec-volume-test-preprovisionedpv-5ls7": Phase="Pending", Reason="", readiness=false. Elapsed: 67.066303ms
Feb  4 14:45:41.233: INFO: Pod "exec-volume-test-preprovisionedpv-5ls7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134462139s
Feb  4 14:45:43.301: INFO: Pod "exec-volume-test-preprovisionedpv-5ls7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.202004685s
[1mSTEP[0m: Saw pod success
Feb  4 14:45:43.301: INFO: Pod "exec-volume-test-preprovisionedpv-5ls7" satisfied condition "Succeeded or Failed"
Feb  4 14:45:43.368: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod exec-volume-test-preprovisionedpv-5ls7 container exec-container-preprovisionedpv-5ls7: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:45:43.520: INFO: Waiting for pod exec-volume-test-preprovisionedpv-5ls7 to disappear
Feb  4 14:45:43.586: INFO: Pod exec-volume-test-preprovisionedpv-5ls7 no longer exists
[1mSTEP[0m: Deleting pod exec-volume-test-preprovisionedpv-5ls7
Feb  4 14:45:43.586: INFO: Deleting pod "exec-volume-test-preprovisionedpv-5ls7" in namespace "volume-5931"
... skipping 208 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (ntfs)][Feature:Windows] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240[0m

      [36mDriver efs.csi.aws.com doesn't support ntfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
... skipping 295 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256[0m

      [36mDriver supports dynamic provisioning, skipping PreprovisionedPV pattern[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
[90m------------------------------[0m
... skipping 99 lines ...
Feb  4 14:45:55.538: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:45:55.608: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com7htc8] to have phase Bound
Feb  4 14:45:55.676: INFO: PersistentVolumeClaim efs.csi.aws.com7htc8 found but phase is Pending instead of Bound.
Feb  4 14:45:57.748: INFO: PersistentVolumeClaim efs.csi.aws.com7htc8 found and phase=Bound (2.140154121s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-x2cm
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:45:57.958: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-x2cm" in namespace "provisioning-4897" to be "Succeeded or Failed"
Feb  4 14:45:58.027: INFO: Pod "pod-subpath-test-dynamicpv-x2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 68.480838ms
Feb  4 14:46:00.095: INFO: Pod "pod-subpath-test-dynamicpv-x2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.137131017s
Feb  4 14:46:02.164: INFO: Pod "pod-subpath-test-dynamicpv-x2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.20586432s
Feb  4 14:46:04.238: INFO: Pod "pod-subpath-test-dynamicpv-x2cm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.279539924s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:04.238: INFO: Pod "pod-subpath-test-dynamicpv-x2cm" satisfied condition "Succeeded or Failed"
Feb  4 14:46:04.309: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-x2cm container test-container-volume-dynamicpv-x2cm: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:46:04.475: INFO: Waiting for pod pod-subpath-test-dynamicpv-x2cm to disappear
Feb  4 14:46:04.543: INFO: Pod pod-subpath-test-dynamicpv-x2cm no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-x2cm
Feb  4 14:46:04.543: INFO: Deleting pod "pod-subpath-test-dynamicpv-x2cm" in namespace "provisioning-4897"
... skipping 121 lines ...
[1mSTEP[0m: Building a namespace api object, basename efs
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit set true
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:367
[1mSTEP[0m: Creating efs pvc & pv
[1mSTEP[0m: Creating pod to mount pvc "efs-3891" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Feb  4 14:46:05.904: INFO: Waiting up to 5m0s for pod "pvc-tester-w9626" in namespace "efs-3891" to be "Succeeded or Failed"
Feb  4 14:46:05.972: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 67.786563ms
Feb  4 14:46:08.044: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 2.139499287s
Feb  4 14:46:10.127: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 4.223309681s
Feb  4 14:46:12.197: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 6.292481597s
Feb  4 14:46:14.266: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 8.361550816s
Feb  4 14:46:16.335: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 10.4305691s
... skipping 3 lines ...
Feb  4 14:46:24.605: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 18.701268995s
Feb  4 14:46:26.675: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 20.770513218s
Feb  4 14:46:28.743: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 22.838812062s
Feb  4 14:46:30.810: INFO: Pod "pvc-tester-w9626": Phase="Pending", Reason="", readiness=false. Elapsed: 24.905986211s
Feb  4 14:46:32.878: INFO: Pod "pvc-tester-w9626": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.974165441s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:32.878: INFO: Pod "pvc-tester-w9626" satisfied condition "Succeeded or Failed"
Feb  4 14:46:32.947: INFO: pod "pvc-tester-w9626" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/107/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/107/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 141 lines ...
Feb  4 14:46:21.534: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:46:21.604: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comt28z2] to have phase Bound
Feb  4 14:46:21.672: INFO: PersistentVolumeClaim efs.csi.aws.comt28z2 found but phase is Pending instead of Bound.
Feb  4 14:46:23.740: INFO: PersistentVolumeClaim efs.csi.aws.comt28z2 found and phase=Bound (2.135758884s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-v8rl
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:46:23.950: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-v8rl" in namespace "provisioning-3915" to be "Succeeded or Failed"
Feb  4 14:46:24.021: INFO: Pod "pod-subpath-test-dynamicpv-v8rl": Phase="Pending", Reason="", readiness=false. Elapsed: 70.688154ms
Feb  4 14:46:26.112: INFO: Pod "pod-subpath-test-dynamicpv-v8rl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.161818183s
Feb  4 14:46:28.181: INFO: Pod "pod-subpath-test-dynamicpv-v8rl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.2308739s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:28.181: INFO: Pod "pod-subpath-test-dynamicpv-v8rl" satisfied condition "Succeeded or Failed"
Feb  4 14:46:28.249: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-v8rl container test-container-subpath-dynamicpv-v8rl: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:46:28.424: INFO: Waiting for pod pod-subpath-test-dynamicpv-v8rl to disappear
Feb  4 14:46:28.498: INFO: Pod pod-subpath-test-dynamicpv-v8rl no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-v8rl
Feb  4 14:46:28.498: INFO: Deleting pod "pod-subpath-test-dynamicpv-v8rl" in namespace "provisioning-3915"
... skipping 256 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Inline-volume (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath file is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256[0m

      [36mDriver efs.csi.aws.com doesn't support InlineVolume -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
[90m------------------------------[0m
... skipping 10 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:46:36.968: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 14:46:37.307: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:46:37.307: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
[1mSTEP[0m: Destroying namespace "volumemode-167" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail to use a volume in a pod with mismatched mode [Slow] [It][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297[0m

      [36mDriver "efs.csi.aws.com" does not provide raw block - skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
[90m------------------------------[0m
... skipping 333 lines ...
Feb  4 14:46:11.255: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:46:11.324: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com96m77] to have phase Bound
Feb  4 14:46:11.392: INFO: PersistentVolumeClaim efs.csi.aws.com96m77 found but phase is Pending instead of Bound.
Feb  4 14:46:13.461: INFO: PersistentVolumeClaim efs.csi.aws.com96m77 found and phase=Bound (2.136440816s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-2ctk
[1mSTEP[0m: Creating a pod to test atomic-volume-subpath
Feb  4 14:46:13.669: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-2ctk" in namespace "provisioning-3323" to be "Succeeded or Failed"
Feb  4 14:46:13.743: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Pending", Reason="", readiness=false. Elapsed: 74.602675ms
Feb  4 14:46:15.815: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.145818623s
Feb  4 14:46:17.883: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 4.214004661s
Feb  4 14:46:19.951: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 6.282707583s
Feb  4 14:46:22.020: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 8.351511488s
Feb  4 14:46:24.097: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 10.428187462s
... skipping 2 lines ...
Feb  4 14:46:30.313: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 16.643974215s
Feb  4 14:46:32.382: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 18.713023766s
Feb  4 14:46:34.450: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 20.780948708s
Feb  4 14:46:36.526: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Running", Reason="", readiness=true. Elapsed: 22.85711259s
Feb  4 14:46:38.596: INFO: Pod "pod-subpath-test-dynamicpv-2ctk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.927747029s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:38.597: INFO: Pod "pod-subpath-test-dynamicpv-2ctk" satisfied condition "Succeeded or Failed"
Feb  4 14:46:38.667: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-2ctk container test-container-subpath-dynamicpv-2ctk: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:46:38.817: INFO: Waiting for pod pod-subpath-test-dynamicpv-2ctk to disappear
Feb  4 14:46:38.884: INFO: Pod pod-subpath-test-dynamicpv-2ctk no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-2ctk
Feb  4 14:46:38.884: INFO: Deleting pod "pod-subpath-test-dynamicpv-2ctk" in namespace "provisioning-3323"
... skipping 126 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278[0m

      [36mDriver supports dynamic provisioning, skipping PreprovisionedPV pattern[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
[90m------------------------------[0m
... skipping 158 lines ...
Feb  4 14:46:43.342: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:46:43.411: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com647fk] to have phase Bound
Feb  4 14:46:43.478: INFO: PersistentVolumeClaim efs.csi.aws.com647fk found but phase is Pending instead of Bound.
Feb  4 14:46:45.545: INFO: PersistentVolumeClaim efs.csi.aws.com647fk found and phase=Bound (2.133919943s)
[1mSTEP[0m: Creating pod exec-volume-test-dynamicpv-lvcg
[1mSTEP[0m: Creating a pod to test exec-volume-test
Feb  4 14:46:45.760: INFO: Waiting up to 5m0s for pod "exec-volume-test-dynamicpv-lvcg" in namespace "volume-4522" to be "Succeeded or Failed"
Feb  4 14:46:45.835: INFO: Pod "exec-volume-test-dynamicpv-lvcg": Phase="Pending", Reason="", readiness=false. Elapsed: 74.548121ms
Feb  4 14:46:47.903: INFO: Pod "exec-volume-test-dynamicpv-lvcg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.142529176s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:47.903: INFO: Pod "exec-volume-test-dynamicpv-lvcg" satisfied condition "Succeeded or Failed"
Feb  4 14:46:47.979: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod exec-volume-test-dynamicpv-lvcg container exec-container-dynamicpv-lvcg: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:46:48.121: INFO: Waiting for pod exec-volume-test-dynamicpv-lvcg to disappear
Feb  4 14:46:48.190: INFO: Pod exec-volume-test-dynamicpv-lvcg no longer exists
[1mSTEP[0m: Deleting pod exec-volume-test-dynamicpv-lvcg
Feb  4 14:46:48.190: INFO: Deleting pod "exec-volume-test-dynamicpv-lvcg" in namespace "volume-4522"
... skipping 84 lines ...
Feb  4 14:46:36.472: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:46:36.555: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comw6gs9] to have phase Bound
Feb  4 14:46:36.625: INFO: PersistentVolumeClaim efs.csi.aws.comw6gs9 found but phase is Pending instead of Bound.
Feb  4 14:46:38.691: INFO: PersistentVolumeClaim efs.csi.aws.comw6gs9 found and phase=Bound (2.136420497s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-fdgp
[1mSTEP[0m: Creating a pod to test multi_subpath
Feb  4 14:46:38.893: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-fdgp" in namespace "provisioning-2079" to be "Succeeded or Failed"
Feb  4 14:46:38.966: INFO: Pod "pod-subpath-test-dynamicpv-fdgp": Phase="Pending", Reason="", readiness=false. Elapsed: 73.4253ms
Feb  4 14:46:41.036: INFO: Pod "pod-subpath-test-dynamicpv-fdgp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.142754245s
Feb  4 14:46:43.104: INFO: Pod "pod-subpath-test-dynamicpv-fdgp": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.210618563s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:43.104: INFO: Pod "pod-subpath-test-dynamicpv-fdgp" satisfied condition "Succeeded or Failed"
Feb  4 14:46:43.170: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-fdgp container test-container-subpath-dynamicpv-fdgp: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:46:43.316: INFO: Waiting for pod pod-subpath-test-dynamicpv-fdgp to disappear
Feb  4 14:46:43.382: INFO: Pod pod-subpath-test-dynamicpv-fdgp no longer exists
[1mSTEP[0m: Deleting pod
Feb  4 14:46:43.383: INFO: Deleting pod "pod-subpath-test-dynamicpv-fdgp" in namespace "provisioning-2079"
... skipping 279 lines ...
[1mSTEP[0m: Building a namespace api object, basename efs
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should mount without option tls when encryptInTransit set false
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:372
[1mSTEP[0m: Creating efs pvc & pv
[1mSTEP[0m: Creating pod to mount pvc "efs-4384" and run "mount && mount | grep /mnt/volume1 | grep fs-0fd9f1db5804865e5"
Feb  4 14:46:50.534: INFO: Waiting up to 5m0s for pod "pvc-tester-tf2fs" in namespace "efs-4384" to be "Succeeded or Failed"
Feb  4 14:46:50.602: INFO: Pod "pvc-tester-tf2fs": Phase="Pending", Reason="", readiness=false. Elapsed: 68.192203ms
Feb  4 14:46:52.669: INFO: Pod "pvc-tester-tf2fs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134876222s
Feb  4 14:46:54.741: INFO: Pod "pvc-tester-tf2fs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.207073209s
[1mSTEP[0m: Saw pod success
Feb  4 14:46:54.741: INFO: Pod "pvc-tester-tf2fs" satisfied condition "Succeeded or Failed"
Feb  4 14:46:54.810: INFO: pod "pvc-tester-tf2fs" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/114/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/114/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 432 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267[0m

      [36mDriver supports dynamic provisioning, skipping PreprovisionedPV pattern[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
[90m------------------------------[0m
... skipping 287 lines ...
[BeforeEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:49:00.766: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail to use a volume in a pod with mismatched mode [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297
Feb  4 14:49:01.105: INFO: Driver "efs.csi.aws.com" does not provide raw block - skipping
[AfterEach] [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:49:01.105: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
[1mSTEP[0m: Destroying namespace "volumemode-7064" for this suite.
... skipping 7 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (filesystem volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail to use a volume in a pod with mismatched mode [Slow] [It][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:297[0m

      [36mDriver "efs.csi.aws.com" does not provide raw block - skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:113
[90m------------------------------[0m
... skipping 26 lines ...
Feb  4 14:48:57.167: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:48:57.239: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comjgkfp] to have phase Bound
Feb  4 14:48:57.308: INFO: PersistentVolumeClaim efs.csi.aws.comjgkfp found but phase is Pending instead of Bound.
Feb  4 14:48:59.381: INFO: PersistentVolumeClaim efs.csi.aws.comjgkfp found and phase=Bound (2.142085095s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-4svr
[1mSTEP[0m: Creating a pod to test subpath
Feb  4 14:48:59.592: INFO: Waiting up to 5m0s for pod "pod-subpath-test-dynamicpv-4svr" in namespace "provisioning-4898" to be "Succeeded or Failed"
Feb  4 14:48:59.666: INFO: Pod "pod-subpath-test-dynamicpv-4svr": Phase="Pending", Reason="", readiness=false. Elapsed: 74.29423ms
Feb  4 14:49:01.735: INFO: Pod "pod-subpath-test-dynamicpv-4svr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.142774911s
Feb  4 14:49:03.802: INFO: Pod "pod-subpath-test-dynamicpv-4svr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.210122049s
[1mSTEP[0m: Saw pod success
Feb  4 14:49:03.802: INFO: Pod "pod-subpath-test-dynamicpv-4svr" satisfied condition "Succeeded or Failed"
Feb  4 14:49:03.868: INFO: Trying to get logs from node ip-172-20-109-214.us-west-2.compute.internal pod pod-subpath-test-dynamicpv-4svr container test-container-volume-dynamicpv-4svr: <nil>
[1mSTEP[0m: delete the pod
Feb  4 14:49:04.019: INFO: Waiting for pod pod-subpath-test-dynamicpv-4svr to disappear
Feb  4 14:49:04.084: INFO: Pod pod-subpath-test-dynamicpv-4svr no longer exists
[1mSTEP[0m: Deleting pod pod-subpath-test-dynamicpv-4svr
Feb  4 14:49:04.084: INFO: Deleting pod "pod-subpath-test-dynamicpv-4svr" in namespace "provisioning-4898"
... skipping 392 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Inline-volume (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if subpath directory is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:240[0m

      [36mDriver efs.csi.aws.com doesn't support InlineVolume -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
[90m------------------------------[0m
... skipping 535 lines ...

      [36mDriver supports dynamic provisioning, skipping PreprovisionedPV pattern[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/base.go:244
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Dynamic PV (block volmode)] volumeMode[0m 
  [1mshould fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:44:27.906: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258
[1mSTEP[0m: Creating sc
[1mSTEP[0m: Creating pv and pvc
Feb  4 14:49:28.776: INFO: Warning: did not get event about provisioing failed
[1mSTEP[0m: Deleting pvc
Feb  4 14:49:28.918: INFO: Deleting PersistentVolumeClaim "pvc-blk8x"
[1mSTEP[0m: Deleting sc
[AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:49:29.061: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 8 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (block volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail in binding dynamic provisioned PV to PVC [Slow][LinuxOnly]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:258[0m
[90m------------------------------[0m
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 24 lines ...

      [36mDriver efs.csi.aws.com doesn't support InlineVolume -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Pre-provisioned PV (block volmode)] volumeMode[0m 
  [1mshould fail to create pod by failing to mount volume [Slow][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:47:15.520: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename volumemode
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail to create pod by failing to mount volume [Slow]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197
[1mSTEP[0m: Creating sc
[1mSTEP[0m: Creating pv and pvc
Feb  4 14:47:16.271: INFO: Waiting for PV pvc5rkf to bind to PVC pvc-5sbxv
Feb  4 14:47:16.271: INFO: Waiting up to timeout=3m0s for PersistentVolumeClaims [pvc-5sbxv] to have phase Bound
Feb  4 14:47:16.338: INFO: PersistentVolumeClaim pvc-5sbxv found but phase is Pending instead of Bound.
... skipping 23 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail to create pod by failing to mount volume [Slow]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:197[0m
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Dynamic PV (default fs)] subPath[0m 
  [1mshould fail if non-existent subpath is outside the volume [Slow][LinuxOnly][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:49:23.893: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename provisioning
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267
Feb  4 14:49:24.422: INFO: Creating resource for dynamic PV
Feb  4 14:49:24.422: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
[1mSTEP[0m: creating a StorageClass 
[1mSTEP[0m: creating a claim
Feb  4 14:49:24.488: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:49:24.555: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comjd2m7] to have phase Bound
Feb  4 14:49:24.621: INFO: PersistentVolumeClaim efs.csi.aws.comjd2m7 found but phase is Pending instead of Bound.
Feb  4 14:49:26.701: INFO: PersistentVolumeClaim efs.csi.aws.comjd2m7 found and phase=Bound (2.145707119s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-tvhr
[1mSTEP[0m: Checking for subpath error in container status
Feb  4 14:49:29.070: INFO: Deleting pod "pod-subpath-test-dynamicpv-tvhr" in namespace "provisioning-1553"
Feb  4 14:49:29.138: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-tvhr" to be fully deleted
[1mSTEP[0m: Deleting pod
Feb  4 14:49:39.271: INFO: Deleting pod "pod-subpath-test-dynamicpv-tvhr" in namespace "provisioning-1553"
[1mSTEP[0m: Deleting pvc
Feb  4 14:49:39.343: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comjd2m7"
... skipping 15 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail if non-existent subpath is outside the volume [Slow][LinuxOnly]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267[0m
[90m------------------------------[0m
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 24 lines ...

      [36mDriver efs.csi.aws.com doesn't support ntfs -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Dynamic PV (default fs)] subPath[0m 
  [1mshould fail if subpath with backstepping is outside the volume [Slow][LinuxOnly][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:49:30.152: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename provisioning
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278
Feb  4 14:49:30.690: INFO: Creating resource for dynamic PV
Feb  4 14:49:30.690: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
[1mSTEP[0m: creating a StorageClass 
[1mSTEP[0m: creating a claim
Feb  4 14:49:30.758: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:49:30.828: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com5dzqj] to have phase Bound
Feb  4 14:49:30.896: INFO: PersistentVolumeClaim efs.csi.aws.com5dzqj found but phase is Pending instead of Bound.
Feb  4 14:49:32.964: INFO: PersistentVolumeClaim efs.csi.aws.com5dzqj found and phase=Bound (2.135449347s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-5s98
[1mSTEP[0m: Checking for subpath error in container status
Feb  4 14:49:37.307: INFO: Deleting pod "pod-subpath-test-dynamicpv-5s98" in namespace "provisioning-9002"
Feb  4 14:49:37.377: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-5s98" to be fully deleted
[1mSTEP[0m: Deleting pod
Feb  4 14:49:49.513: INFO: Deleting pod "pod-subpath-test-dynamicpv-5s98" in namespace "provisioning-9002"
[1mSTEP[0m: Deleting pvc
Feb  4 14:49:49.579: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com5dzqj"
... skipping 15 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail if subpath with backstepping is outside the volume [Slow][LinuxOnly]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:278[0m
[90m------------------------------[0m
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 49 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Inline-volume (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      [36m[1mshould fail if non-existent subpath is outside the volume [Slow][LinuxOnly] [BeforeEach][0m
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:267[0m

      [36mDriver efs.csi.aws.com doesn't support InlineVolume -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:116
[90m------------------------------[0m
... skipping 58 lines ...
[1mSTEP[0m: creating a claim
Feb  4 14:49:46.290: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:49:46.358: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.com49wvd] to have phase Bound
Feb  4 14:49:46.423: INFO: PersistentVolumeClaim efs.csi.aws.com49wvd found but phase is Pending instead of Bound.
Feb  4 14:49:48.490: INFO: PersistentVolumeClaim efs.csi.aws.com49wvd found and phase=Bound (2.132317216s)
[1mSTEP[0m: Creating pod to format volume volume-prep-provisioning-4509
Feb  4 14:49:48.704: INFO: Waiting up to 5m0s for pod "volume-prep-provisioning-4509" in namespace "provisioning-4509" to be "Succeeded or Failed"
Feb  4 14:49:48.777: INFO: Pod "volume-prep-provisioning-4509": Phase="Pending", Reason="", readiness=false. Elapsed: 72.594492ms
Feb  4 14:49:50.843: INFO: Pod "volume-prep-provisioning-4509": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.138547884s
[1mSTEP[0m: Saw pod success
Feb  4 14:49:50.843: INFO: Pod "volume-prep-provisioning-4509" satisfied condition "Succeeded or Failed"
Feb  4 14:49:50.843: INFO: Deleting pod "volume-prep-provisioning-4509" in namespace "provisioning-4509"
Feb  4 14:49:50.917: INFO: Wait up to 5m0s for pod "volume-prep-provisioning-4509" to be fully deleted
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-428f
[1mSTEP[0m: Checking for subpath error in container status
Feb  4 14:49:53.181: INFO: Deleting pod "pod-subpath-test-dynamicpv-428f" in namespace "provisioning-4509"
Feb  4 14:49:53.250: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-428f" to be fully deleted
[1mSTEP[0m: Deleting pod
Feb  4 14:49:57.385: INFO: Deleting pod "pod-subpath-test-dynamicpv-428f" in namespace "provisioning-4509"
[1mSTEP[0m: Deleting pvc
Feb  4 14:49:57.451: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.com49wvd"
... skipping 150 lines ...

      [36mDriver efs.csi.aws.com doesn't support ext3 -- skipping[0m

      /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:121
[90m------------------------------[0m
[0m[efs-csi] EFS CSI[0m [90m[Driver: efs.csi.aws.com][0m [0m[Testpattern: Dynamic PV (default fs)] subPath[0m 
  [1mshould fail if subpath file is outside the volume [Slow][LinuxOnly][0m
  [37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256[0m

[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 6 lines ...
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
[1mSTEP[0m: Creating a kubernetes client
Feb  4 14:49:40.075: INFO: >>> kubeConfig: /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/hack/e2e/csi-test-artifacts/test-cluster-32766.k8s.local.kops.kubeconfig
[1mSTEP[0m: Building a namespace api object, basename provisioning
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should fail if subpath file is outside the volume [Slow][LinuxOnly]
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256
Feb  4 14:49:40.606: INFO: Creating resource for dynamic PV
Feb  4 14:49:40.606: INFO: Using claimSize:1Mi, test suite supported size:{ 1Mi}, driver(efs.csi.aws.com) supported size:{ 1Mi} 
[1mSTEP[0m: creating a StorageClass 
[1mSTEP[0m: creating a claim
Feb  4 14:49:40.673: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil
Feb  4 14:49:40.743: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [efs.csi.aws.comhp2fd] to have phase Bound
Feb  4 14:49:40.809: INFO: PersistentVolumeClaim efs.csi.aws.comhp2fd found but phase is Pending instead of Bound.
Feb  4 14:49:42.877: INFO: PersistentVolumeClaim efs.csi.aws.comhp2fd found and phase=Bound (2.134154134s)
[1mSTEP[0m: Creating pod pod-subpath-test-dynamicpv-l8xf
[1mSTEP[0m: Checking for subpath error in container status
Feb  4 14:49:47.214: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8xf" in namespace "provisioning-8247"
Feb  4 14:49:47.284: INFO: Wait up to 5m0s for pod "pod-subpath-test-dynamicpv-l8xf" to be fully deleted
[1mSTEP[0m: Deleting pod
Feb  4 14:49:59.420: INFO: Deleting pod "pod-subpath-test-dynamicpv-l8xf" in namespace "provisioning-8247"
[1mSTEP[0m: Deleting pvc
Feb  4 14:49:59.486: INFO: Deleting PersistentVolumeClaim "efs.csi.aws.comhp2fd"
... skipping 14 lines ...
[efs-csi] EFS CSI
[90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:219[0m
  [Driver: efs.csi.aws.com]
  [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:227[0m
    [Testpattern: Dynamic PV (default fs)] subPath
    [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:50[0m
      should fail if subpath file is outside the volume [Slow][LinuxOnly]
      [90m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:256[0m
[90m------------------------------[0m
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:220
[BeforeEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:185
... skipping 72 lines ...
[1mSTEP[0m: Building a namespace api object, basename efs
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should mount different paths on same volume on same node
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:234
[1mSTEP[0m: Creating efs pvc & pv with no subpath
[1mSTEP[0m: Creating pod to make subpaths /a and /b
Feb  4 14:49:01.954: INFO: Waiting up to 5m0s for pod "pvc-tester-cgjfg" in namespace "efs-2764" to be "Succeeded or Failed"
Feb  4 14:49:02.022: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 67.876557ms
Feb  4 14:49:04.089: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.135259839s
Feb  4 14:49:06.165: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.210485049s
Feb  4 14:49:08.235: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.280731073s
Feb  4 14:49:10.305: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.350650446s
Feb  4 14:49:12.373: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.418840131s
Feb  4 14:49:14.443: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.488369279s
Feb  4 14:49:16.512: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.557392358s
Feb  4 14:49:18.581: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.627357598s
Feb  4 14:49:20.649: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.6952664s
Feb  4 14:49:22.718: INFO: Pod "pvc-tester-cgjfg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.764056577s
Feb  4 14:49:24.787: INFO: Pod "pvc-tester-cgjfg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.832444985s
[1mSTEP[0m: Saw pod success
Feb  4 14:49:24.787: INFO: Pod "pvc-tester-cgjfg" satisfied condition "Succeeded or Failed"
[1mSTEP[0m: Creating efs pvc & pv with subpath /a
[1mSTEP[0m: Creating efs pvc & pv with subpath /b
[1mSTEP[0m: Creating pod to mount subpaths /a and /b
[AfterEach] [efs-csi] EFS CSI
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:186
Feb  4 14:50:05.483: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 114 lines ...
[1mSTEP[0m: Building a namespace api object, basename efs
[1mSTEP[0m: Waiting for a default service account to be provisioned in namespace
[It] should mount with option tls when encryptInTransit unset
  /home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:363
[1mSTEP[0m: Creating efs pvc & pv
[1mSTEP[0m: Creating pod to mount pvc "efs-9770" and run "mount && mount | grep /mnt/volume1 | grep 127.0.0.1"
Feb  4 14:50:01.391: INFO: Waiting up to 5m0s for pod "pvc-tester-99r2p" in namespace "efs-9770" to be "Succeeded or Failed"
Feb  4 14:50:01.457: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 65.543079ms
Feb  4 14:50:03.526: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.134584965s
Feb  4 14:50:05.593: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.201463491s
Feb  4 14:50:07.659: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.267373792s
Feb  4 14:50:09.726: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.33447483s
Feb  4 14:50:11.797: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.405605613s
... skipping 4 lines ...
Feb  4 14:50:22.134: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 20.742335159s
Feb  4 14:50:24.200: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 22.808220849s
Feb  4 14:50:26.266: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 24.874652121s
Feb  4 14:50:28.334: INFO: Pod "pvc-tester-99r2p": Phase="Pending", Reason="", readiness=false. Elapsed: 26.943073847s
Feb  4 14:50:30.400: INFO: Pod "pvc-tester-99r2p": Phase="Succeeded", Reason="", readiness=false. Elapsed: 29.009062499s
[1mSTEP[0m: Saw pod success
Feb  4 14:50:30.400: INFO: Pod "pvc-tester-99r2p" satisfied condition "Succeeded or Failed"
Feb  4 14:50:30.468: INFO: pod "pvc-tester-99r2p" logs:
 overlay on / type overlay (rw,relatime,lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/34/fs,upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/162/fs,workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/162/work)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
... skipping 167 lines ...
[1mSTEP[0m: Deleted EFS filesystem "fs-0fd9f1db5804865e5"



[91m[1mSummarizing 1 Failure:[0m

[91m[1m[Fail] [0m[90m[efs-csi] EFS CSI [0m[0m[Driver: efs.csi.aws.com] [0m[91m[1m[It] should create a directory with the correct permissions when in directory provisioning mode [0m
[37m/home/prow/go/src/github.com/kubernetes-sigs/aws-efs-csi-driver/test/e2e/e2e.go:426[0m

[1m[91mRan 37 of 190 Specs in 541.729 seconds[0m
[1m[91mFAIL![0m -- [32m[1m36 Passed[0m | [91m[1m1 Failed[0m | [33m[1m0 Pending[0m | [36m[1m153 Skipped[0m


Ginkgo ran 1 suite in 10m12.317441705s
Test Suite Failed
+ TEST_PASSED=1
+ set -e
+ set +x
###
## TEST_PASSED: 1
#
... skipping 814 lines ...
I0204 14:40:45.115661       1 node.go:306] NodeGetInfo: called with args 
I0204 14:43:40.542003       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:40.545547       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:40.546911       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-0bac4c0ad858783f5" target_path:"/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:40.546978       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
I0204 14:43:40.547038       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount with options [accesspoint=fsap-0bac4c0ad858783f5 tls]
E0204 14:43:40.991460       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:40.991576       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:41.542174       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:41.543267       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-0bac4c0ad858783f5" target_path:"/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:41.543337       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
I0204 14:43:41.543422       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount with options [accesspoint=fsap-0bac4c0ad858783f5 tls]
E0204 14:43:41.981493       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:41.981672       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:43.046295       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:43.047219       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-0bac4c0ad858783f5" target_path:"/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:43.047287       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
I0204 14:43:43.047361       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount with options [accesspoint=fsap-0bac4c0ad858783f5 tls]
E0204 14:43:43.674443       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:43.674554       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:45.760691       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:45.761680       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-0bac4c0ad858783f5" target_path:"/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:45.761750       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
I0204 14:43:45.761808       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount with options [accesspoint=fsap-0bac4c0ad858783f5 tls]
E0204 14:43:46.239625       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:46.239717       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:50.267731       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:50.268977       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-0bac4c0ad858783f5" target_path:"/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:50.269064       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
I0204 14:43:50.269134       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount with options [accesspoint=fsap-0bac4c0ad858783f5 tls]
E0204 14:43:50.673979       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:50.674179       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-0bac4c0ad858783f5,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/f905a4d1-90d2-4981-884b-bc306a262194/volumes/kubernetes.io~csi/pvc-563df0de-d34f-4fac-9677-24171eeac369/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-08abf96f38d73d75f is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:53.376679       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:53.382676       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:53.383670       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" target_path:"/var/lib/kubelet/pods/30c86d61-7b72-417a-95dc-ebd5f04e927e/volumes/kubernetes.io~csi/efs.csi.aws.com-c9gd7/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
I0204 14:43:53.383733       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/30c86d61-7b72-417a-95dc-ebd5f04e927e/volumes/kubernetes.io~csi/efs.csi.aws.com-c9gd7/mount
... skipping 494 lines ...
I0204 14:47:19.687852       1 node.go:203] NodeUnpublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" target_path:"/var/lib/kubelet/pods/36193e4a-a441-4094-87ac-919dd41cda95/volumes/kubernetes.io~csi/efs-364/mount" 
I0204 14:47:19.690551       1 node.go:227] NodeUnpublishVolume: unmounting /var/lib/kubelet/pods/36193e4a-a441-4094-87ac-919dd41cda95/volumes/kubernetes.io~csi/efs-364/mount
I0204 14:47:19.708206       1 node.go:232] NodeUnpublishVolume: /var/lib/kubelet/pods/36193e4a-a441-4094-87ac-919dd41cda95/volumes/kubernetes.io~csi/efs-364/mount unmounted
I0204 14:47:19.789143       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:22.992810       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:22.997472       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:22.997549       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:23.593977       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:23.595340       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:23.595393       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:24.597123       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:24.598478       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:24.598545       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:26.603220       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:26.604771       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:26.604857       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:30.616873       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:30.618150       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:30.618204       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:38.641748       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:38.642916       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:38.642968       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:47:54.697900       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:47:54.699086       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:47:54.699152       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:48:26.704211       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:48:26.705369       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:48:26.705421       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
I0204 14:49:30.796113       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:49:30.797151       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5" staging_target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc5rkf" target_path:"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc5rkf/267341ba-f001-4435-a464-d77263803950" volume_capability:<block:<> access_mode:<mode:SINGLE_NODE_WRITER > > 
E0204 14:49:30.797208       1 driver.go:97] GRPC error: rpc error: code = InvalidArgument desc = Volume capability not supported: only filesystem volumes are supported
###
## Printing pod efs-csi-node-6dk7s efs-plugin container logs
#
I0204 14:40:43.900386       1 config_dir.go:88] Creating symlink from '/etc/amazon/efs' to '/var/amazon/efs'
I0204 14:40:43.901220       1 metadata.go:63] getting MetadataService...
I0204 14:40:43.902489       1 metadata.go:68] retrieving metadata from EC2 metadata service
... skipping 10 lines ...
I0204 14:40:45.633395       1 node.go:306] NodeGetInfo: called with args 
I0204 14:43:41.853386       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:41.858540       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:41.860656       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-07f7034f408229e3f" target_path:"/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:41.860746       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
I0204 14:43:41.860815       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount with options [accesspoint=fsap-07f7034f408229e3f tls]
E0204 14:43:42.336552       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:42.336729       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:42.857306       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:42.858527       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-07f7034f408229e3f" target_path:"/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:42.858599       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
I0204 14:43:42.858675       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount with options [accesspoint=fsap-07f7034f408229e3f tls]
E0204 14:43:43.285210       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:43.285330       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:44.357962       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:44.359167       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-07f7034f408229e3f" target_path:"/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:44.359239       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
I0204 14:43:44.359320       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount with options [accesspoint=fsap-07f7034f408229e3f tls]
E0204 14:43:44.787780       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:44.788159       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:46.862198       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:46.863193       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-07f7034f408229e3f" target_path:"/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:46.863249       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
I0204 14:43:46.863324       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount with options [accesspoint=fsap-07f7034f408229e3f tls]
E0204 14:43:47.280518       1 mount_linux.go:184] Mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
E0204 14:43:47.280830       1 driver.go:97] GRPC error: rpc error: code = Internal desc = Could not mount "fs-0fd9f1db5804865e5:/" at "/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount": mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t efs -o accesspoint=fsap-07f7034f408229e3f,tls fs-0fd9f1db5804865e5:/ /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
Output: Failed to resolve "fs-0fd9f1db5804865e5.efs.us-west-2.amazonaws.com". The file system mount target ip address cannot be found, please pass mount target ip address via mount options. 
User: arn:aws:sts::607362164682:assumed-role/nodes.test-cluster-32766.k8s.local/i-0830a5883d972f25d is not authorized to perform: elasticfilesystem:DescribeMountTargets on the specified resource
Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].Warning: config file does not have fips_mode_enabled item in section mount.. You should be able to find a new config file in the same folder as current config file /etc/amazon/efs/efs-utils.conf. Consider update the new config file to latest config file. Use the default value [fips_mode_enabled = False].
I0204 14:43:51.381426       1 node.go:290] NodeGetCapabilities: called with args 
I0204 14:43:51.382257       1 node.go:52] NodePublishVolume: called with args volume_id:"fs-0fd9f1db5804865e5::fsap-07f7034f408229e3f" target_path:"/var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount" volume_capability:<mount:<> access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:"storage.kubernetes.io/csiProvisionerIdentity" value:"1675521646408-8081-efs.csi.aws.com" > 
I0204 14:43:51.382327       1 node.go:178] NodePublishVolume: creating dir /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount
I0204 14:43:51.382400       1 node.go:183] NodePublishVolume: mounting fs-0fd9f1db5804865e5:/ at /var/lib/kubelet/pods/3a805f41-0505-4b71-943b-161fdaac16a4/volumes/kubernetes.io~csi/pvc-4e0d1bea-ed96-428b-b6dd-902f7565ba96/mount with options [accesspoint=fsap-07f7034f408229e3f tls]
... skipping 486 lines ...
	route-table:rtb-09969e2c014f61145
	internet-gateway:igw-0249ed801ebaa3055
	volume:vol-027d87a2f8141f744
	dhcp-options:dopt-0e409642cf53ef53b
	subnet:subnet-085688942c855aa1c
	vpc:vpc-0f09bc799016710a8
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2023-02-04T14:53:48Z"}
++ early_exit_handler
++ '[' -n 170 ']'
++ kill -TERM 170
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 6 lines ...

PR	jonathanrainer: Adds capability to provision directories on the EFS dynamically
Result	ABORTED
Tests	1 failed / 36 succeeded
Started	2023-02-04 14:32
Elapsed	21m46s
Revision	4a2d3428f97687ab248e1252ea44bb382778b03a
Refs	732

kubernetes-sigs/aws-efs-csi-driver PR #732 pull-aws-efs-csi-driver-e2e #1621879403761897472

Test Failures

EFS CSI Suite [efs-csi] EFS CSI [Driver: efs.csi.aws.com] should create a directory with the correct permissions when in directory provisioning mode 19s

Passed

Skipped

Error lines from build-log.txt