certs: use arch-specific image arghost
Similar to what monitortest.go is doing, use arch-specific image for "agnhost" as its not being used directly
/payload-job periodic-ci-openshift-multiarch-master-nightly-4.16-ocp-e2e-aws-ovn-arm64 periodic-ci-openshift-multiarch-master-nightly-4.16-ocp-e2e-ovn-remote-libvirt-ppc64le
@vrutkovs: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-multiarch-master-nightly-4.16-ocp-e2e-aws-ovn-arm64
- periodic-ci-openshift-multiarch-master-nightly-4.16-ocp-e2e-ovn-remote-libvirt-ppc64le
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/de55d320-c04f-11ee-831b-eede4afd1278-0
/hold
This doesn't seem necessary - test is passing in some arm64 payloads where tests image is fresh, fails on week old tests image used in some jobs
@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-single-node-serial | a2403c36e840d5f3450e658598ea3d101e7917fb | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-metal-ipi-sdn | a2403c36e840d5f3450e658598ea3d101e7917fb | link | false | /test e2e-metal-ipi-sdn |
| ci/prow/e2e-aws-ovn-single-node-upgrade | a2403c36e840d5f3450e658598ea3d101e7917fb | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-agnostic-ovn-cmd | a2403c36e840d5f3450e658598ea3d101e7917fb | link | false | /test e2e-agnostic-ovn-cmd |
| ci/prow/e2e-metal-ipi-ovn-ipv6 | a2403c36e840d5f3450e658598ea3d101e7917fb | link | true | /test e2e-metal-ipi-ovn-ipv6 |
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/test-infra repository. I understand the commands that are listed here.