Test NMO operator upgrade from v0.17.0 to latest #50559
Conversation
|
/pj-rehearse max |
openshift-ci
bot
added
the
approved
There was a problem hiding this comment.
- why spinning up a new cluster for this test instead of using the one we have alrady?
- what about doing what the docs suggest, using 3 steps: install, upgrade, e2e test? (https://docs.ci.openshift.org/docs/how-tos/testing-operator-sdk-operators/#operator-upgrade-testing)
/hold
|
It seems like the test was never tested... |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
razo7
changed the title
|
FAR doesn't have the |
|
/pj-rehearse pull-ci-medik8s-node-maintenance-operator-main-4.16-openshift-e2e |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Good input, I have followed your suggestions, applied them for NMO, and I will now add the upgrade utility in FAR |
|
/pj-rehearse pull-ci-medik8s-node-maintenance-operator-main-4.16-openshift-e2e |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-medik8s-node-maintenance-operator-main-4.16-openshift-e2e |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-medik8s-node-maintenance-operator-main-4.16-openshift-e2e |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-medik8s-node-maintenance-operator-main-4.16-openshift-e2e |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
Make OCP-e2e cluster test a three steps test- installing old version, update to latest, test e2e test
|
/pj-rehearse auto-ack |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
removed
the
rehearsals-ack
Fetch old released version from Quay for the first installation
|
/pj-rehearse auto-ack |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@razo7: The following test failed, say
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. |
|
/pj-rehearse auto-ack |
|
@razo7: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/retest |
openshift-ci-robot
added
the
rehearsals-ack
...r/config/medik8s/node-maintenance-operator/medik8s-node-maintenance-operator-main__4.16.yaml
Show resolved
Hide resolved
|
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Include NMO upgrade installation test in OCP-e2e cluster test Make OCP-e2e cluster test a three steps test- installing old version, update to latest, test e2e test * Use quay released version Fetch old released version from Quay for the first installation
Perform an operator upgrade test from the last released version to the latest commit in
main.Upgrade an old operator to a new one on the same OCP cluster, see https://docs.ci.openshift.org/docs/how-tos/testing-operator-sdk-operators/#operator-upgrade-testing