Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCO: add OKD tests for release-4.6 and release-4.7 branches #12683

Merged

Conversation

vrutkovs
Copy link
Member

Make sure OKD images are tested and promoted on 4.6/4.7 branch PRs.

Replaces #12615

@vrutkovs
Copy link
Member Author

/cc @sinnykumari

Make sure OKD images are tested and promoted on 4.6/4.7 branch PRs
@vrutkovs vrutkovs force-pushed the okd-4.6-mco-branching branch from 3e8873a to 24793ca Compare October 12, 2020 09:54
@sinnykumari
Copy link
Contributor

ah, I started working on fixing the okd related changes sometime back. Since you have already created a new pr, i will drop okd related commit 9016a5d from openshift/machine-config-operator#2145

@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-aws 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-upgrade 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-gcp-op 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-gcp-op 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-aws 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-upgrade 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.6/okd-e2e-gcp-op 24793ca link /test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.6/okd-e2e-upgrade 24793ca link /test pj-rehearse
ci/prow/pj-rehearse 24793ca link /test pj-rehearse

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.

@sinnykumari
Copy link
Contributor

As vadim mentioned, okd tests in ci are failing due to OVN changes. Vadim will look at failing upgrade tests later on. This shouldn't impact regular MCO tests.

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sinnykumari, vrutkovs

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

The pull request process is described here

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 openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 15, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e3b2f14 into openshift:master Oct 15, 2020
@openshift-ci-robot
Copy link
Contributor

@vrutkovs: Updated the following 7 configmaps:

  • job-config-4.6 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-machine-config-operator-release-4.6-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-postsubmits.yaml
    • key openshift-machine-config-operator-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-presubmits.yaml
  • job-config-4.6 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-release-4.6-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-postsubmits.yaml
    • key openshift-machine-config-operator-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-presubmits.yaml
  • job-config-4.7 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-machine-config-operator-release-4.7-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-postsubmits.yaml
    • key openshift-machine-config-operator-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-presubmits.yaml
  • job-config-4.7 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-release-4.7-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-postsubmits.yaml
    • key openshift-machine-config-operator-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-presubmits.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-master__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-master__okd.yaml
  • ci-operator-4.6-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-release-4.6__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6__okd.yaml
  • ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-machine-config-operator-release-4.7__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7__okd.yaml

In response to this:

Make sure OKD images are tested and promoted on 4.6/4.7 branch PRs.

Replaces #12615

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.

5 participants