Don't retry jobs that are expected to fail
Don't retry jobs that are expected to fail

At network service testing the timeout for jobs failing or not is 90
seconds and those jobs have three retries, in case the test is expected
to fail 4 differenct containers are going to be create/run/delete since
the job is going to retry it and this reaches the timeout limit (more
often at k8s >= 1.20).

Since on test that expect job to fail retries does not make sense this
change add a parameter to the job creatin function so we specify no
retries if job is expected to fail.

Signed-off-by: Quique Llorente <fad7636a3d20aa3e8008777ef56bb24366aa3b13@redhat.com>

stu-gott/kubevirt,davidvossel/kubevirt,davidvossel/kubevirt,kubevirt/kubevirt,kubevirt/kubevirt,stu-gott/kubevirt,stu-gott/kubevirt,davidvossel/kubevirt,kubevirt/kubevirt,davidvossel/kubevirt,kubevirt/kubevirt,stu-gott/kubevirt