Skip to content

USHIFT-6380: Fix OLM test random failures#5942

Merged
openshift-merge-bot[bot] merged 8 commits intoopenshift:mainfrom
ggiguash:pr-5933-branch
Dec 22, 2025
Merged

USHIFT-6380: Fix OLM test random failures#5942
openshift-merge-bot[bot] merged 8 commits intoopenshift:mainfrom
ggiguash:pr-5933-branch

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Dec 18, 2025

Derived from #5933
Co-authored with @pacevedom

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@ggiguash: This pull request references USHIFT-6380 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Derived from
Co-authored with @pacevedom

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2025

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@ggiguash: This pull request references USHIFT-6380 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21" instead.

Details

In response to this:

Derived from #5933
Co-authored with @pacevedom

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 openshift-eng/jira-lifecycle-plugin repository.

@ggiguash ggiguash marked this pull request as ready for review December 18, 2025 10:37
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 18, 2025
@openshift-ci openshift-ci bot requested review from agullon and vanhalenar December 18, 2025 10:37
@ggiguash
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@ggiguash: This pull request references USHIFT-6380 which is a valid jira issue.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@pacevedom
Copy link
Contributor

/test all

2 similar comments
@pacevedom
Copy link
Contributor

/test all

@pacevedom
Copy link
Contributor

/test all

@pacevedom
Copy link
Contributor

/test e2e-aws-tests-bootc-arm

@copejon
Copy link
Contributor

copejon commented Dec 18, 2025

/assign @copejon

@copejon
Copy link
Contributor

copejon commented Dec 18, 2025

/retest

@pacevedom
Copy link
Contributor

/test all

2 similar comments
@pacevedom
Copy link
Contributor

/test all

@pacevedom
Copy link
Contributor

/test all

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 19, 2025
@pacevedom
Copy link
Contributor

Looks like we need bigger timeouts, after 2min it was still unpacking the catalog (most likely due to its size)

@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 20, 2025

Looking at this report, we are still getting disk space problems, this time in /tmp partition.

err: copying system image from manifest list: writing blob: adding layer with blob "sha256:e63b11a59e6566584406149f0b8e969a63d410842200b95291111db8aedd36f3"/""/"sha256:470bee5c0b41ddef39f5b51bb3daedcbdc72df92955f17603fa408faf08a2fed": unpacking failed (error: exit status 1; output: open /tmp/cache/cache/bamoe-kogito-operator_8.x_bamoe-kogito-operator.8.0.2-3.json: no space left on device); artifact err: provided artifact is a container image

@ggiguash
Copy link
Contributor Author

Another failure here

Keyword 'CSV Should Be Succeeded' failed after retrying for 5 minutes. The last error was: Succeeded != Pending

@ggiguash
Copy link
Contributor Author

No more OLM failures. Retesting
/test all

1 similar comment
@ggiguash
Copy link
Contributor Author

No more OLM failures. Retesting
/test all

@agullon
Copy link
Contributor

agullon commented Dec 22, 2025

/lgtm

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

openshift-ci bot commented Dec 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@ggiguash
Copy link
Contributor Author

ggiguash commented Dec 22, 2025

Giving it the last try. If there are no OLM failures, we'll merge this PR.

/unhold
/test all

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 22, 2025
@ggiguash
Copy link
Contributor Author

OLM tests have not failed
/override ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-upstream ci/prow/e2e-aws-tests-bootc-upstream-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm prow/e2e-aws-tests-bootc-release

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • prow/e2e-aws-tests-bootc-release

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-aws-tests
  • ci/prow/e2e-aws-tests-arm
  • ci/prow/e2e-aws-tests-bootc
  • ci/prow/e2e-aws-tests-bootc-arm
  • ci/prow/e2e-aws-tests-bootc-periodic
  • ci/prow/e2e-aws-tests-bootc-periodic-arm
  • ci/prow/e2e-aws-tests-bootc-release
  • ci/prow/e2e-aws-tests-bootc-release-arm
  • ci/prow/e2e-aws-tests-bootc-upstream
  • ci/prow/e2e-aws-tests-bootc-upstream-arm
  • ci/prow/e2e-aws-tests-periodic
  • ci/prow/e2e-aws-tests-periodic-arm
  • ci/prow/e2e-aws-tests-release
  • ci/prow/e2e-aws-tests-release-arm
  • ci/prow/images
  • ci/prow/security
  • ci/prow/test-unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-microshift-main-e2e-aws-tests
  • pull-ci-openshift-microshift-main-e2e-aws-tests-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-upstream
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-upstream-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-periodic
  • pull-ci-openshift-microshift-main-e2e-aws-tests-periodic-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-release
  • pull-ci-openshift-microshift-main-e2e-aws-tests-release-arm
  • pull-ci-openshift-microshift-main-images
  • pull-ci-openshift-microshift-main-security
  • pull-ci-openshift-microshift-main-test-unit
  • pull-ci-openshift-microshift-main-verify
  • pull-ci-openshift-microshift-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

OLM tests have not failed
/override ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-upstream ci/prow/e2e-aws-tests-bootc-upstream-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm prow/e2e-aws-tests-bootc-release

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.

@ggiguash
Copy link
Contributor Author

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 22, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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 openshift-eng/jira-lifecycle-plugin repository.

@ggiguash
Copy link
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-upstream ci/prow/e2e-aws-tests-bootc-upstream-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm ci/prow/e2e-aws-tests-bootc-release

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-release, ci/prow/e2e-aws-tests-bootc-release-arm, ci/prow/e2e-aws-tests-bootc-upstream, ci/prow/e2e-aws-tests-bootc-upstream-arm, ci/prow/e2e-aws-tests-release, ci/prow/e2e-aws-tests-release-arm

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-upstream ci/prow/e2e-aws-tests-bootc-upstream-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm ci/prow/e2e-aws-tests-bootc-release

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.

@ggiguash
Copy link
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-release

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6786b8f and 2 for PR HEAD ab26cce in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-release

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: 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.

@ggiguash
Copy link
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-release

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-release

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 5f3d81e into openshift:main Dec 22, 2025
20 checks passed
@ggiguash ggiguash deleted the pr-5933-branch branch December 22, 2025 17:36
@ggiguash
Copy link
Contributor Author

/cherry-pick release-4.21

@openshift-cherrypick-robot

@ggiguash: #5942 failed to apply on top of branch "release-4.21":

Applying: USHIFT-6380: Expand lvm size for optional ostree scenarios
Applying: USHIFT-6380: Expand lvm size for optional bootc scenarios
Using index info to reconstruct a base tree...
A	test/scenarios-bootc/upstream/cos10-src@optional.sh
A	test/scenarios-bootc/upstream/cos9-src@optional.sh
Falling back to patching base and 3-way merge...
Auto-merging test/scenarios/releases/el96-lrel@optional.sh
CONFLICT (content): Merge conflict in test/scenarios/releases/el96-lrel@optional.sh
Auto-merging test/scenarios/periodics/el96-src@optional.sh
CONFLICT (content): Merge conflict in test/scenarios/periodics/el96-src@optional.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 USHIFT-6380: Expand lvm size for optional bootc scenarios

Details

In response to this:

/cherry-pick release-4.21

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants