Closed razo7 closed 4 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
Considering that it supposed to perform both upgrade and downgrade, would be bundle-run-replace
be a clearer option?
Considering that it supposed to perform both upgrade and downgrade, would be
bundle-run-replace
be a clearer option?
I don't have a strong preference here. bundle-run-update
also seems fine as we update the CSV.
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: clobrano, razo7
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm cancel
/lgtm
ping tide
@razo7: The following test 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/4.12-openshift-e2e | 31ace8461d4ef5429010b421018e57a65c662295 | link | unknown | /test 4.12-openshift-e2e |
Full PR test history. Your PR dashboard.
/retest
Why we need this PR
Introduce a new target,
bundle-run-update
, for testing an operator upgrade. It could be used as well for downgrading or reinstalling the operator (instead of running the bundle-cleanup and then bundle-run).Run 'VERSION=SOME_VERSION' prior to running the bundle-run or bundle-run-update targets to modify the installed or replaced bundle CSV.
The new target will be used for testing operator upgrades in OCP CI - https://github.com/openshift/release/pull/50559
Changes made
bundle-run-update
targetBUNDLE_RUN_NAMESPACE
toOPERATOR_NAMESPACE
in MakefileWhich issue(s) this PR fixes
ECOPROJECT-1082
Test plan
Similar to PR of NMO #120