Skip to content

Conversation

@nunnatsa
Copy link
Collaborator

@nunnatsa nunnatsa commented Dec 7, 2025

Manual revert of #3735

We can't compile with AAQ 1.3.1 in openshift CI, as go1.22 there is 1.22.9, while AAQ 1.3.1 requires 1.22.11

Release note:

downgrade AAQ to v1.3.0

We can't compile with AAQ 1.3.1 in openshift CI, as go1.22 there is
1.22.9, while AAQ requires 1.22.11

Signed-off-by: Nahshon Unna Tsameret <[email protected]>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Dec 7, 2025
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign avlitman for approval. For more information see the Code Review Process.

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

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

@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 7, 2025

@nunnatsa nunnatsa changed the title revert bumping AAQ to v1.3.0 [release 1.14] Revert bumping AAQ to v1.3.0 Dec 7, 2025
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes - here's some feedback:

  • In go.mod you downgraded the go directive to 1.22.9 but added toolchain go1.22.11, which seems to reintroduce the same version constraint you are trying to avoid; consider removing or aligning the toolchain directive with what is actually available in OpenShift CI.
  • The metadata.annotations.createdAt field in the CSV was updated to a later date even though this is essentially a revert; consider keeping this timestamp consistent with the original release or updating it only as part of an actual new build process.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In go.mod you downgraded the `go` directive to 1.22.9 but added `toolchain go1.22.11`, which seems to reintroduce the same version constraint you are trying to avoid; consider removing or aligning the toolchain directive with what is actually available in OpenShift CI.
- The `metadata.annotations.createdAt` field in the CSV was updated to a later date even though this is essentially a revert; consider keeping this timestamp consistent with the original release or updating it only as part of an actual new build process.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@nunnatsa nunnatsa changed the title [release 1.14] Revert bumping AAQ to v1.3.0 [release 1.14] downgrade AAQ to v1.3.0 Dec 7, 2025
@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 20005768770

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 72.501%

Totals Coverage Status
Change from base Build 19859446007: 0.0%
Covered Lines: 6549
Relevant Lines: 9033

💛 - Coveralls

@openshift-ci
Copy link

openshift-ci bot commented Dec 7, 2025

@nunnatsa: The following tests 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/hco-e2e-upgrade-operator-sdk-sno-aws 9dc3b0a link false /test hco-e2e-upgrade-operator-sdk-sno-aws
ci/prow/hco-e2e-operator-sdk-sno-azure 9dc3b0a link false /test hco-e2e-operator-sdk-sno-azure
ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-aws 9dc3b0a link false /test hco-e2e-upgrade-prev-operator-sdk-sno-aws
ci/prow/hco-e2e-operator-sdk-gcp 9dc3b0a link true /test hco-e2e-operator-sdk-gcp
ci/prow/hco-e2e-operator-sdk-aws 9dc3b0a link true /test hco-e2e-operator-sdk-aws
ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws 9dc3b0a link true /test hco-e2e-upgrade-prev-operator-sdk-aws
ci/prow/hco-e2e-operator-sdk-sno-aws 9dc3b0a link false /test hco-e2e-operator-sdk-sno-aws
ci/prow/hco-e2e-upgrade-operator-sdk-sno-azure 9dc3b0a link false /test hco-e2e-upgrade-operator-sdk-sno-azure
ci/prow/hco-e2e-operator-sdk-azure 9dc3b0a link true /test hco-e2e-operator-sdk-azure
ci/prow/hco-e2e-upgrade-prev-operator-sdk-azure 9dc3b0a link true /test hco-e2e-upgrade-prev-operator-sdk-azure
ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-azure 9dc3b0a link false /test hco-e2e-upgrade-prev-operator-sdk-sno-azure
ci/prow/hco-e2e-upgrade-operator-sdk-azure 9dc3b0a link true /test hco-e2e-upgrade-operator-sdk-azure
ci/prow/hco-e2e-upgrade-operator-sdk-aws 9dc3b0a link true /test hco-e2e-upgrade-operator-sdk-aws

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

@hco-bot
Copy link
Collaborator

hco-bot commented Dec 7, 2025

hco-e2e-kv-smoke-gcp lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-azure

@kubevirt-bot
Copy link
Contributor

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-kv-smoke-azure

In response to this:

hco-e2e-kv-smoke-gcp lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-azure

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

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants