Skip to content

Conversation

@wainersm
Copy link
Contributor

@wainersm wainersm commented Dec 9, 2025

The current osc-test-fbc-integration pipeline in Konflux which runs to test the test-fbc catalog have a broken test because it expects the old operator version of 1.11.0. I could have it fixed in Prow side, but I preferred to add a new EXPECTED_OPERATOR_VERSION parameter to the pipeline so we can bump the version at same time test-fbc version is raised.

In order to have EXPECTED_OPERATOR_VERSION taking effect I had to fix a issue (that's the commit 3c66305).

While in here, because testing these changes is time-consuming, I added two more changes:

  • passing the FORCE_SUCCESS_EXIT=no parameter to force the job report fail to any kind of error (CI infra or tests failures)
  • bumped the konflux-tasks to latest and greatest to pick up some nice features like job submission retry

The expected operator version parameter is used by QE tests check the
operator catalog is released with the right version. As we are in the
1.11.1 release cycle, bumped it.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
The extra newline in CATALOG_IMAGE is preventing the ENVS variable from
being parsed correctly.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
By default the prow job succeed even when tests failed. The only
situation it fails is when there is an CI infra problem. We don't that
behavior on jobs triggered by konflux, otherwise we will be needed to
inspect all results.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Use latest and greatest version of konflux-tasks that provides
improvements such as retrying job creation in case of fail.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
@openshift-ci openshift-ci bot requested review from bpradipt and snir911 December 9, 2025 18:54
@wainersm
Copy link
Contributor Author

wainersm commented Dec 9, 2025

@vvoronko
Copy link

vvoronko commented Dec 9, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2025
@vvoronko
Copy link

vvoronko commented Dec 9, 2025

/approve

Copy link
Contributor

@littlejawa littlejawa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
Thanks @wainersm !

@littlejawa
Copy link
Contributor

/retest

@wainersm
Copy link
Contributor Author

/retest

The latest failure on CI seems to be in Prow infra.

@wainersm
Copy link
Contributor Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Dec 11, 2025

@wainersm: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

@tbuskey
Copy link
Contributor

tbuskey commented Dec 11, 2025

/approve

value: downstream-candidate
- name: ENVS
value: "CATALOG_SOURCE_IMAGE=$(tasks.get-catalog-image.results.CATALOG_IMAGE)"
value: "CATALOG_SOURCE_IMAGE=$(tasks.get-catalog-image.results.CATALOG_IMAGE),EXPECTED_OPERATOR_VERSION=1.11.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this bump occur at the same time we bump versions with the ## OSC_VERSION tag as documented at https://github.com/openshift/sandboxed-containers-operator/blob/devel/docs/DEVELOPMENT.md#updating-versions ? Or should this be only bumped after the bundle was pushed and the test-catalog udpated accordingly as in f70661f ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @gkurz !

This pipeline aims to test OSC on updates of the test-catalog, so it should be only bumped alongside the commit f70661f

I want to document it somewhere or have the bump done automatically, that's why I asked you and @littlejawa on slack. IIUC test-catalog version is bumped manually so I want to have a small section in fbc/README.md that explains how test-catalog version (and this pipeline) is updated. Makes sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants