Skip to content

Conversation

@vrutkovs
Copy link
Contributor

@vrutkovs vrutkovs commented Aug 25, 2021

TODO:

  • Verify that step/job crosses 4hr period
  • Add a step to delete Insights operator pod
    This would make it send a new report, so that we could see the result in the Superset.
    UPD: CI runs are preconfigured to run snapshots every 10 mins, which is enough for post section to trigger this

Requires openshift/ci-tools#2294 to pass generated job checker

@vrutkovs vrutkovs changed the title jobs: extend 4.6 -> 4.7 -> 4.8 upgrade timeout to 8hrs WIP jobs: extend 4.6 -> 4.7 -> 4.8 upgrade timeout to 8hrs Aug 25, 2021
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 25, 2021
@openshift-ci openshift-ci bot requested review from dmage and joelddiaz August 25, 2021 15:33
@vrutkovs
Copy link
Contributor Author

/retest

Failed on 4.3 -> 4.4 leg

@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs vrutkovs closed this Aug 27, 2021
@vrutkovs vrutkovs reopened this Aug 27, 2021
@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs vrutkovs force-pushed the long-timeout-jobs branch 3 times, most recently from e5356e2 to 8083065 Compare August 27, 2021 12:31
@vrutkovs
Copy link
Contributor Author

Not sure why stable-initial install doesn't complete

/retest

@vrutkovs
Copy link
Contributor Author

/retest

1 similar comment
@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs vrutkovs force-pushed the long-timeout-jobs branch 3 times, most recently from c62bbd8 to 7818fd1 Compare August 30, 2021 16:38
@vrutkovs
Copy link
Contributor Author

/retest

1 similar comment
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Sep 2, 2021

/retest

@vrutkovs vrutkovs force-pushed the long-timeout-jobs branch 2 times, most recently from d122e2e to 02d3b6d Compare September 2, 2021 13:43
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Sep 3, 2021

/retest

@vrutkovs vrutkovs force-pushed the long-timeout-jobs branch 2 times, most recently from 10488cc to 8e54958 Compare September 3, 2021 13:10
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Sep 6, 2021

/retest

@vrutkovs
Copy link
Contributor Author

vrutkovs commented Nov 8, 2021

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2021
@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Dec 26, 2021
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 3, 2022
@vrutkovs vrutkovs force-pushed the long-timeout-jobs branch 2 times, most recently from ce41d63 to 4977520 Compare January 3, 2022 12:55
Vadim Rutkovsky added 2 commits January 3, 2022 15:03
These tests are sequential upgrades to ensure born-in-4.x clusters can be upgraded to 4.8.
Disruption tests are skipped, prowjob timeout is extended to 8 hours
@vrutkovs
Copy link
Contributor Author

vrutkovs commented Jan 3, 2022

/cc @wking

@openshift-ci openshift-ci bot requested a review from wking January 3, 2022 14:04
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 18, 2022
@wking
Copy link
Member

wking commented Jan 27, 2022

/retest

@wking
Copy link
Member

wking commented Jan 27, 2022

/lgtm
/hold

Looks good to me. Would be nice to have a rehearsal confirming it works before pulling the hold, but if it's to hard to get the ancient versions to install, I'm fine landing this first and adjusting later if necessary.

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

openshift-ci bot commented Jan 27, 2022

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@vrutkovs
Copy link
Contributor Author

/hold cancel

Lets run them live for a few weeks, we might want to move them to never-stable if these never pass

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 27, 2022
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2022

@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/pj-rehearse-blocking 7818fd124fc5498e9889d8e0529e6b4d6a267889 link /test pj-rehearse-blocking
ci/rehearse/openshift/cluster-logging-operator/release-5.2/e2e-gcp 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-gcp 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/release-5.4/e2e-gcp 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-ovirt-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-ovirt-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/tech-preview/e2e-operator 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-aws-upgrade-single-node 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.9-e2e-vsphere-ovn 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-gcp-ovn 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-stable-4.8-upgrade-from-stable-4.6-e2e-aws-upgrade-paused 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-vsphere-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-azure-ovn-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-gcp-ovn-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-aws-ovn-upgrade 80d46cf7e3086275e0a346f7791cd68e8b490980 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.11-e2e-ibmcloud-ipi-ovn-periodic ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.7/e2e-aws-disruptive-ovn ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/okd-e2e-gcp ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-aws-disruptive ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-aws ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/openshift/origin/release-4.9/e2e-gcp-disruptive ce41d6342460ea03a0f1df1d3f371ed46ed41bd4 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-stable-4.8-upgrade-from-stable-4.5-e2e-aws-upgrade 0498c82 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-stable-4.8-upgrade-from-stable-4.2-e2e-aws-upgrade 0498c82 link unknown /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-stable-4.8-upgrade-from-stable-4.3-e2e-aws-upgrade 0498c82 link unknown /test pj-rehearse
ci/prow/pj-rehearse 0498c82 link false /test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-stable-4.8-upgrade-from-stable-4.4-e2e-aws-upgrade 0498c82 link unknown /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-merge-robot openshift-merge-robot merged commit 1ab3d95 into openshift:master Jan 27, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2022

@vrutkovs: Updated the following 3 configmaps:

  • ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master__stable-4.8-upgrade-from-stable-4.2.yaml using file ci-operator/config/openshift/release/openshift-release-master__stable-4.8-upgrade-from-stable-4.2.yaml
    • key openshift-release-master__stable-4.8-upgrade-from-stable-4.3.yaml using file ci-operator/config/openshift/release/openshift-release-master__stable-4.8-upgrade-from-stable-4.3.yaml
    • key openshift-release-master__stable-4.8-upgrade-from-stable-4.4.yaml using file ci-operator/config/openshift/release/openshift-release-master__stable-4.8-upgrade-from-stable-4.4.yaml
    • key openshift-release-master__stable-4.8-upgrade-from-stable-4.5.yaml using file ci-operator/config/openshift/release/openshift-release-master__stable-4.8-upgrade-from-stable-4.5.yaml
  • job-config-master-periodics configmap in namespace ci at cluster app.ci using the following files:
    • key openshift-release-master-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml
  • step-registry configmap in namespace ci at cluster app.ci using the following files:
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/test/8h/OWNERS
    • key openshift-e2e-test-8h-commands.sh using file ci-operator/step-registry/openshift/e2e/test/8h/openshift-e2e-test-8h-commands.sh
    • key openshift-e2e-test-8h-ref.metadata.json using file ci-operator/step-registry/openshift/e2e/test/8h/openshift-e2e-test-8h-ref.metadata.json
    • key openshift-e2e-test-8h-ref.yaml using file ci-operator/step-registry/openshift/e2e/test/8h/openshift-e2e-test-8h-ref.yaml
Details

In response to this:

TODO:

  • Verify that step/job crosses 4hr period
  • Add a step to delete Insights operator pod
    This would make it send a new report, so that we could see the result in the Superset.
    UPD: CI runs are preconfigured to run snapshots every 10 mins, which is enough for post section to trigger this

Requires openshift/ci-tools#2294 to pass generated job checker

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants