Skip to content

Conversation

@r4f4
Copy link
Contributor

@r4f4 r4f4 commented Dec 15, 2020

After openshift/origin#24887 we are seeing image
pull errors in CI for ppc64le and s390x. So for now we've created our
own multi-arch mirror.

Signed-off-by: Rafael Fonseca [email protected]

@alvaroaleman
Copy link
Contributor

/assign @smarterclayton
/uncc

@jaypoulz
Copy link
Contributor

Long term plan is to keep working with the upstream to ensure that multi-arch images are available for each supported platform. However, given the lack of generally available hardware (especially for s390x), this is our interim solution to ensure that we're able to continue to cover 90%+ of the e2e parallel suite. Otherwise, we drop back into the high 60s for Z and 80s for power.

@r4f4 r4f4 force-pushed the use-multiarch-mirror branch 3 times, most recently from 31ce576 to 66f732b Compare December 15, 2020 22:15
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 16, 2020

/retest

@r4f4 r4f4 force-pushed the use-multiarch-mirror branch 2 times, most recently from dde983f to 56110fc Compare December 16, 2020 11:09
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 16, 2020

/retest

@r4f4
Copy link
Contributor Author

r4f4 commented Dec 16, 2020

/retest

@r4f4
Copy link
Contributor Author

r4f4 commented Dec 16, 2020

The "managed cluster ..." test will be fixed by #14394

@r4f4 r4f4 force-pushed the use-multiarch-mirror branch from 56110fc to 2cb3de5 Compare December 17, 2020 09:41
@petr-muller
Copy link
Member

/approve

Providing the label necessary for merge, but someone who can interpret the chnages in tests lists should provide /lgtm

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2020
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 17, 2020

We added one more image to our multi-arch repo, so I'll do another review round of the excluded tests before this is merged.

@r4f4 r4f4 force-pushed the use-multiarch-mirror branch 2 times, most recently from 0131db6 to f640f68 Compare December 17, 2020 14:49
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 17, 2020

List reviewed, it's good to go now.

@openshift-merge-robot
Copy link
Contributor

@r4f4: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/release-openshift-origin-installer-e2e-remote-libvirt-ppc64le-4.7 f640f685ddcb5166dd44bfc73b51296efee8d534 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-remote-libvirt-s390x-4.7 f640f685ddcb5166dd44bfc73b51296efee8d534 link /test pj-rehearse
ci/prow/pj-rehearse f640f685ddcb5166dd44bfc73b51296efee8d534 link /test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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.

After openshift/origin#24887 we are seeing image
pull errors in CI for ppc64le and s390x. So for now we've created our
own multi-arch mirror.

Signed-off-by: Rafael Fonseca <[email protected]>
@r4f4 r4f4 force-pushed the use-multiarch-mirror branch from f640f68 to a48cc91 Compare December 17, 2020 17:45
@r4f4
Copy link
Contributor Author

r4f4 commented Dec 17, 2020

I added a few more false-positive test failures (DNS failures and connection timeouts).

@jaypoulz
Copy link
Contributor

/lgtm

I think it's worth checking this in before the holidays since this will increase our coverage, test pass rates, and most importantly, gather us the kind of quality data we need to make decisions when we come back from shutdown.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaypoulz, petr-muller, r4f4

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci-robot
Copy link
Contributor

@r4f4: Updated the following 7 configmaps:

  • job-config-4.7 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-release-release-4.7-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.7-periodics.yaml
  • job-config-4.7 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.7-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.7-periodics.yaml
  • prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster api.ci using the following files:
    • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster app.ci using the following files:
    • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster build01 using the following files:
    • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster build02 using the following files:
    • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-remote-libvirt-e2e configmap in namespace ci at cluster vsphere using the following files:
    • key cluster-launch-installer-remote-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-remote-libvirt-e2e.yaml
Details

In response to this:

After openshift/origin#24887 we are seeing image
pull errors in CI for ppc64le and s390x. So for now we've created our
own multi-arch mirror.

Signed-off-by: Rafael Fonseca [email protected]

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants