What happened?this commit changed the rust and cargo installation during the docker build from yum to a dynamic method using rustup. This is causing some tests to fail as the rpm make for efs-utils expects rust and cargo to be visible from a yum install. Example of failures from pull requests can be found here and here.
What you expected to happen?
The testing to pass.
How to reproduce it (as minimally and precisely as possible)?
Simplest way is to retest either of those PRs above and see Prow output.
/kind bug
What happened? this commit changed the rust and cargo installation during the docker build from yum to a dynamic method using rustup. This is causing some tests to fail as the rpm make for efs-utils expects rust and cargo to be visible from a yum install. Example of failures from pull requests can be found here and here.
What you expected to happen? The testing to pass.
How to reproduce it (as minimally and precisely as possible)? Simplest way is to retest either of those PRs above and see Prow output.
Anything else we need to know?:
Environment
kubectl version
): N/APlease also attach debug logs to help us better diagnose https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_aws-efs-csi-driver/1455/pull-aws-efs-csi-driver-e2e/1836084250353340416