Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test".
(Note: "add to whitelist" is no longer supported. Please update configurations in hack/jenkins/job-configs/kubernetes-jenkins-pull/ instead.)

This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

Otherwise, if this message is too spammy, please complain to ixdy.

https://github.com/kubernetes/kubernetes/blob/master/pkg/util/mount/mount.go#L112 should the mountPath here be evaluated as symlinks as well?

@zhouhaibing089 Thanks. Yes, this mountPath need do EvalSymlinks as well.

Could anyone guide me how to find the detail errors for below FAILURE?

TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests Build 22537 outcome was FAILURE
Summary: Exit code 1 Build time: 00:14:04

I can only see below error message in build log, but no much clue

[19:06:36]E:     [Step 6/6] Step Clean, Build, Kube-Up, Smoke Test, Kube-Down (Command Line) failed

@chengyli you could rebase your code to get a clean test again. I thought the test has failed for a long time, though not the way failed like you met.

@saad-ali any actions reuiqred from my side? And who could help to review the code?

I'll take a look. CC @kubernetes/sig-storage

LGTM

@k8s-bot ok to test

@saad-ali , is the test failure caused by this issue #25037?

Yes, that does appear to be the case.

@saad-ali
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

@k8s-bot test this issue: #25037

GCE e2e build/test passed for commit 1fb33aa.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@saad-ali , could you please help to merge the pr, thanks!

It will automatically be merged by the merge-bot. The submit queue is pretty backed up, so it might take a few days.

@saad-ali Got it, thanks!

@chengyli I'm merging a bunch of small PRs to clear out the queue. In it goes.