Frequent test failures of `TestFunctional/parallel/MountCmd/any-port`

[minikube-bot]

This test has high flake rates for the following environments:

Environment	Flake Rate (%)
Docker_Cloud_Shell	100.00

[medyagh]

it seems that it started on Aug 23rd Aug 24th https://storage.googleapis.com/minikube-flake-rate/flake_chart.html?env=Docker_Linux_docker_arm64&test=TestFunctional/parallel/MountCmd/any-port

[medyagh]

on Github Action it fails too here is the Docker Linux arm64 logs 47.txt

2021-09-20T18:45:09.0270445Z === CONT  TestFunctional/parallel/MountCmd/any-port
2021-09-20T18:45:09.0272997Z     functional_test_mount_test.go:133: (dbg) Non-zero exit: ./minikube-linux-arm64 -p functional-20210920184147-2055 ssh -- ls -la /mount-9p: exit status 1 (518.910403ms)
2021-09-20T18:45:09.0276942Z         
2021-09-20T18:45:09.0277902Z         -- stdout --
2021-09-20T18:45:09.0279302Z            ls: cannot access '/mount-9p/test-1632163507254384816': Bad file descriptor
2021-09-20T18:45:09.0281696Z            ls: cannot access '/mount-9p/created-by-test-removed-by-pod': Bad file descriptor
2021-09-20T18:45:09.0283586Z            ls: cannot access '/mount-9p/created-by-test': Bad file descriptor
2021-09-20T18:45:09.0284587Z            total 0
2021-09-20T18:45:09.0285602Z            -????????? ? ? ? ?            ? created-by-test
2021-09-20T18:45:09.0286972Z            -????????? ? ? ? ?            ? created-by-test-removed-by-pod
2021-09-20T18:45:09.0288224Z            -????????? ? ? ? ?            ? test-1632163507254384816
2021-09-20T18:45:09.0288812Z         
2021-09-20T18:45:09.0289479Z         -- /stdout --
2021-09-20T18:45:09.0290013Z         ** stderr ** 
2021-09-20T18:45:09.0290642Z            ssh: Process exited with status 1
2021-09-20T18:45:09.0291234Z         
2021-09-20T18:45:09.0291988Z         ** /stderr **
2021-09-20T18:45:09.0293782Z     functional_test_mount_test.go:135: failed verifying accessing to the mount. args "./minikube-linux-arm64 -p functional-20210920184147-2055 ssh -- ls -la /mount-9p" : exit status 1
2021-09-20T18:45:09.0295918Z     functional_test_mount_test.go:84: "TestFunctional/parallel/MountCmd/any-port" failed, getting debug info...
2021-09-20T18:45:09.0298009Z     functional_test_mount_test.go:85: (dbg) Run:  ./minikube-linux-arm64 -p functional-20210920184147-2055 ssh "mount | grep 9p; ls -la /mount-9p; cat /mount-9p/pod-dates"
2021-09-20T18:45:09.4633611Z     functional_test_mount_test.go:85: (dbg) Non-zero exit: ./minikube-linux-arm64 -p functional-20210920184147-2055 ssh "mount | grep 9p; ls -la /mount-9p; cat /mount-9p/pod-dates": exit status 1 (436.233806ms)
2021-09-20T18:45:09.4635673Z         
2021-09-20T18:45:09.4636695Z         -- stdout --
2021-09-20T18:45:09.4638538Z            192.168.49.1 on /mount-9p type 9p (rw,relatime,sync,dirsync,dfltuid=1000,dfltgid=999,access=any,msize=65536,trans=tcp,noextend,port=33383)
2021-09-20T18:45:09.4640577Z            ls: cannot access '/mount-9p/test-1632163507254384816': Bad file descriptor
2021-09-20T18:45:09.4642420Z            ls: cannot access '/mount-9p/created-by-test-removed-by-pod': Bad file descriptor
2021-09-20T18:45:09.4644268Z            ls: cannot access '/mount-9p/created-by-test': Bad file descriptor
2021-09-20T18:45:09.4645336Z            total 0
2021-09-20T18:45:09.4646430Z            -????????? ? ? ? ?            ? created-by-test
2021-09-20T18:45:09.4647886Z            -????????? ? ? ? ?            ? created-by-test-removed-by-pod
2021-09-20T18:45:09.4649333Z            -????????? ? ? ? ?            ? test-1632163507254384816
2021-09-20T18:45:09.4650630Z            cat: /mount-9p/pod-dates: No such file or directory
2021-09-20T18:45:09.4652590Z         
2021-09-20T18:45:09.4653380Z         -- /stdout --
2021-09-20T18:45:09.4653923Z         ** stderr ** 
2021-09-20T18:45:09.4654552Z            ssh: Process exited with status 1
2021-09-20T18:45:09.4655146Z         
2021-09-20T18:45:09.4655632Z         ** /stderr **

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale