Skip to content

release: Release minor upgrade jobs should run conformance after #14666

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.

Sign up for GitHub

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

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Jan 19, 2021
Merged

release: Release minor upgrade jobs should run conformance after #14666

openshift-merge-robot merged 1 commit into from
Jan 19, 2021

Conversation

@smarterclayton
Copy link
Contributor

@smarterclayton smarterclayton commented Jan 6, 2021

After a successful release upgrade, we should be running a
conformance suite to verify that upgraded clusters are conformant.

/hold

still testing

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 6, 2021
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 6, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

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 openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2021
@smarterclayton smarterclayton force-pushed the upgrade_then_test branch 3 times, most recently from 44b3202 to 0d908e2 Compare January 6, 2021 20:13
@smarterclayton
Copy link
Contributor Author

smarterclayton commented Jan 7, 2021

/retest

@smarterclayton smarterclayton mentioned this pull request Jan 7, 2021
Merged
@smarterclayton
Copy link
Contributor Author

smarterclayton commented Jan 7, 2021

/retest

@smarterclayton smarterclayton force-pushed the upgrade_then_test branch 3 times, most recently from 4a1ece1 to f1f7779 Compare January 11, 2021 18:09
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jan 11, 2021

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

Test name Commit Details Rerun command
ci/prow/pj-rehearse f1f7779b40bce6f0a878bf5aa631707b3566fe8d 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.

@smarterclayton
Copy link
Contributor Author

smarterclayton commented Jan 18, 2021

/retest

@smarterclayton smarterclayton force-pushed the upgrade_then_test branch 5 times, most recently from cb39c5e to 66def8d Compare January 19, 2021 00:55
@smarterclayton
release: Release minor upgrade jobs should run conformance after
8081c8c 
After a successful release upgrade, we should be running a
conformance suite to verify that upgraded clusters are conformant.
@smarterclayton
Copy link
Contributor Author

smarterclayton commented Jan 19, 2021

/hold cancel

Tests pass in 4.7 most of the time, turning on the gates.

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 19, 2021
@smarterclayton smarterclayton added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 2021

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

Test name Commit Details Rerun command
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.6-stable-to-4.7-ci 14918a8f9f88579de5a0a31b2a88883567e3f215 link /test pj-rehearse
ci/prow/pj-rehearse 14918a8f9f88579de5a0a31b2a88883567e3f215 link /test pj-rehearse
ci/rehearse/release-openshift-ocp-installer-e2e-ovirt-upgrade-4.7-stable-to-4.8-ci 66def8da7f89a8fa9b0931b6990e9ae4257fea42 link /test pj-rehearse
ci/rehearse/release-openshift-ocp-installer-e2e-ovirt-upgrade-4.6-stable-to-4.7-ci 66def8da7f89a8fa9b0931b6990e9ae4257fea42 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.6-stable-to-4.7-ci 66def8da7f89a8fa9b0931b6990e9ae4257fea42 link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-gcp-upgrade-4.7-stable-to-4.8-ci 8081c8c link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-aws-upgrade-4.7-stable-to-4.8-ci 8081c8c link /test pj-rehearse
ci/rehearse/release-openshift-origin-installer-e2e-azure-upgrade-4.7-stable-to-4.8-ci 8081c8c 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.

@openshift-bot
Copy link
Contributor

openshift-bot commented Jan 19, 2021

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 2076334 into openshift:master Jan 19, 2021
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 19, 2021

@smarterclayton: Updated the following 4 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
  • job-config-4.8 configmap in namespace ci at cluster api.ci using the following files:
    • key openshift-release-release-4.8-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.8-periodics.yaml
  • job-config-4.8 configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-release-4.8-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-release-4.8-periodics.yaml
Details

In response to this:

After a successful release upgrade, we should be running a
conformance suite to verify that upgraded clusters are conformant.

/hold

still testing

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

Reviewers

@bbguimaraes bbguimaraes Awaiting requested review from bbguimaraes

@petr-muller petr-muller Awaiting requested review from petr-muller

Assignees

No one assigned

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@smarterclayton @openshift-ci-robot @openshift-merge-robot @openshift-bot