NO-JIRA: tls registry: extend time for cert collection pod to start

[vrutkovs]

Some SNO/multiarch tests are unable to start cert collection pod in one minute. This extends the period to 5 minutes.
Fixes issues from https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview-serial/1840789311960649728

Retry fetching info about tests image from buildcluster registry, as it may throw transient errors

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
Once this PR has been reviewed and has the lgtm label, please assign xueqzhan for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@vrutkovs: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-ipsec-serial	2c51029	link	false	/test e2e-aws-ovn-ipsec-serial
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	2c51029	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade	2c51029	link	false	/test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[vrutkovs]

/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-azure-ovn-kube-apiserver-rollout
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-serial
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview-serial

[openshift-ci]

@vrutkovs: trigger 4 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-e2e-azure-ovn-kube-apiserver-rollout
• periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-serial
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e30187a0-8662-11ef-8495-c0a9fd21c103-0

[vrutkovs]

/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-metal-ipi-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-vsphere-ovn-techpreview

[openshift-ci]

@vrutkovs: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ad699680-86dc-11ef-8d36-822a39823da0-0

[openshift-ci-robot]

@vrutkovs: This pull request explicitly references no jira issue.

In response to this:

Some SNO/multiarch tests are unable to start cert collection pod in one minute. This extends the period to 5 minutes.
Fixes issues from https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview-serial/1840789311960649728

Retry fetching info about tests image from buildcluster registry, as it may throw transient errors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.