kubernetes: Should recreate evicted statefulset conformance test may encounter host port conflict

What happened:

The Should recreate evicted statefulset conformance test in https://github.com/kubernetes/kubernetes/blob/master/test/e2e/apps/statefulset.go fails because Pod ss-0 expected to be re-created at least once. This was caused by the Predicate PodFitsHostPorts failed scheduling error. The root cause was a host port conflict for port 21017. This port was in-use as an ephemeral port by another application running on the node.

What you expected to happen:

Should recreate evicted statefulset conformance test handles potential host port conflicts.

How to reproduce it (as minimally and precisely as possible):

Since this is timing related, reproducing the problem is not easy. Running conformance tests in parallel like is described in https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md#running-conformance-tests makes it a little easier to reproduce the problem provided there is an application on the host that could yield the host port conflict.

Anything else we need to know?:

No.

Environment:

• Kubernetes version (use kubectl version): Any
• Cloud provider or hardware configuration: IBM cloud provider
• OS (e.g: cat /etc/os-release): Ubuntu 18.04.3 LTS
• Kernel (e.g. uname -a): 4.15.0-58-generic
• Install tools: IBM Cloud Kubernetes Service
• Network plugin and version (if this is a network-related bug): N/A
• Others: None