Add scenarios for rolling back and re-installing SBO with OLM

[pmacik]

Signed-off-by: Pavel Macík pavel.macik@gmail.com

Follow-up to #1221

Changes

This PR adds additional acceptance testing scenarios for:

• Reinstall latest SBO with OLM
• Reinstall pre-latest SBO with OLM
• Rollback SBO with OLM to the previous version

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs
  included if any changes are user facing
• Tests
  included if any functionality added or changed. For bugfixes please include tests that can catch regressions
• All acceptance test scenarios included in the PR which verifies a bugfix or a requested feature reported by a non-member are tagged with @external-feedback tag.
• Follows the commit message standard

[openshift-ci]

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

[codecov]

Codecov Report

Merging #1313 (86b383b) into master (b397f86) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1313   +/-   ##
=======================================
  Coverage   58.16%   58.16%           
=======================================
  Files          35       35           
  Lines        3007     3007           
=======================================
  Hits         1749     1749           
  Misses       1090     1090           
  Partials      168      168           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b397f86...86b383b. Read the comment docs.

[pmacik]

/retest

[pmacik]

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

[openshift-ci]

@pmacik: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test 4.10-acceptance
• /test 4.10-performance-reduced
• /test 4.11-acceptance
• /test 4.11-performance-reduced
• /test 4.12-acceptance
• /test 4.9-acceptance
• /test performance

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-redhat-developer-service-binding-operator-master-4.10-acceptance
• pull-ci-redhat-developer-service-binding-operator-master-4.11-acceptance
• pull-ci-redhat-developer-service-binding-operator-master-4.12-acceptance
• pull-ci-redhat-developer-service-binding-operator-master-4.9-acceptance

In response to this:

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

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.

[pmacik]

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

[pmacik]

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

[pmacik]

/retest

[pmacik]

/retest

[pmacik]

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

[pmacik]

/retest

[pmacik]

/test 4.9-upgrade-with-olm
/test 4.10-upgrade-with-olm
/test 4.11-upgrade-with-olm
/test 4.12-upgrade-with-olm

[filariow]

/lgtm

[filariow]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: filariow

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:

• OWNERS [filariow]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment