Add a presubmit job to test upgrades on the CVO repo #2997
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci-robot
added
the
size/M
Contributor
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
Requires openshift/ci-operator#284 before it will function. Will be used as the template for other jobs. The job launches the cluster using a release image build from the current state of the integration stream (release:initial). It then launches the upgrade tests with openshift-tests run-upgrade all --to-image=.../ci-op-.../release:latest The test job will start the prereq tests, then once they are stable, launch the upgrade, monitoring invariants while the test continues. Once the upgrade is complete or fails, the postcondition tests will run and then the cluster is torn down. Due to limitations in the upstream infrastructure for upgrade tests we don't get the nice separation between tests that e2e runs do which is a future improvement. After this test is working we'll add it to other repos as a standard job, including the release verification jobs. We'll also invoke it from the release controller dynamically to calculate upgrade edges prior to promoting a job.
Contributor
Author
Contributor
Author
|
Probably going to be replaced by |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires openshift/ci-operator#284 before it will function. Will be used as
the template for other jobs.
The job launches the cluster using a release image build from the current
state of the integration stream (release:initial). It then launches the
upgrade tests with
The test job will start the prereq tests, then once they are stable, launch
the upgrade, monitoring invariants while the test continues. Once the
upgrade is complete or fails, the postcondition tests will run and then the
cluster is torn down.
Due to limitations in the upstream infrastructure for upgrade tests we
don't get the nice separation between tests that e2e runs do which is a
future improvement.
After this test is working we'll add it to other repos as a standard job,
including the release verification jobs. We'll also invoke it from the
release controller dynamically to calculate upgrade edges prior to
promoting a job.