Skip to content

WIP: annotate HCO CR with platform.kubevirt.io/autopilot=true on deploy#4287

Open
tiraboschi wants to merge 1 commit into
kubevirt:mainfrom
tiraboschi:trigger_vpa
Open

WIP: annotate HCO CR with platform.kubevirt.io/autopilot=true on deploy#4287
tiraboschi wants to merge 1 commit into
kubevirt:mainfrom
tiraboschi:trigger_vpa

Conversation

@tiraboschi

@tiraboschi tiraboschi commented May 25, 2026

Copy link
Copy Markdown
Member

What this PR does / why we need it:
This is a temporary experiment to measure the impact of enabling virt-platform-autopilot across all openshift-ci lanes on test stability and execution time, before deciding how to stably enable it.

PLEASE DON'T MERGE

Reviewer Checklist

Reviewers are supposed to review the PR for every aspect below one by one. To check an item means the PR is either "OK" or "Not Applicable" in terms of that item. All items are supposed to be checked before merging a PR.

  • PR Message
  • Commit Messages
  • How to test
  • Unit Tests
  • Functional Tests
  • User Documentation
  • Developer Documentation
  • Upgrade Scenario
  • Uninstallation Scenario
  • Backward Compatibility
  • Troubleshooting Friendly

Jira Ticket:

Release note:

@tiraboschi
WIP: annotate HCO CR with platform.kubevirt.io/autopilot=true on deploy
db22a38 
This is a temporary experiment to measure the impact of enabling
virt-platform-autopilot across all openshift-ci lanes on test stability
and execution time, before deciding how to stably enable it.

Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
@kubevirt-bot

kubevirt-bot commented May 25, 2026

Copy link
Copy Markdown
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@kubevirt-bot kubevirt-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 25, 2026
@kubevirt-bot

kubevirt-bot commented May 25, 2026

Copy link
Copy Markdown
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 orenc1 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@tiraboschi

tiraboschi commented May 25, 2026

Copy link
Copy Markdown
Member Author

/hold

@kubevirt-bot kubevirt-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XS labels May 25, 2026
@sonarqubecloud

sonarqubecloud Bot commented May 25, 2026

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@coveralls

coveralls commented May 25, 2026

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 26406366768

Coverage remained the same at 80.345%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

Coverage Stats

Coverage Status
Relevant Lines: 12989
Covered Lines: 10436
Line Coverage: 80.34%
Coverage Strength: 2.05 hits per line
💛 - Coveralls

@openshift-ci

openshift-ci Bot commented May 25, 2026

Copy link
Copy Markdown

@tiraboschi: 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-prev-operator-sdk-azure db22a38 link true /test hco-e2e-upgrade-prev-operator-sdk-azure
ci/prow/hco-e2e-kv-smoke-azure db22a38 link true /test hco-e2e-kv-smoke-azure
ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-azure db22a38 link false /test hco-e2e-upgrade-prev-operator-sdk-sno-azure
ci/prow/hco-e2e-upgrade-operator-sdk-azure db22a38 link true /test hco-e2e-upgrade-operator-sdk-azure
ci/prow/hco-e2e-operator-sdk-azure db22a38 link true /test hco-e2e-operator-sdk-azure
ci/prow/hco-e2e-operator-sdk-gcp db22a38 link true /test hco-e2e-operator-sdk-gcp
ci/prow/hco-e2e-operator-sdk-sno-azure db22a38 link false /test hco-e2e-operator-sdk-sno-azure
ci/prow/hco-e2e-upgrade-operator-sdk-sno-azure db22a38 link false /test hco-e2e-upgrade-operator-sdk-sno-azure
ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-azure db22a38 link true /test hco-e2e-consecutive-operator-sdk-upgrades-azure
ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-aws db22a38 link false /test hco-e2e-upgrade-prev-operator-sdk-sno-aws
ci/prow/hco-e2e-upgrade-operator-sdk-aws db22a38 link true /test hco-e2e-upgrade-operator-sdk-aws
ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-aws db22a38 link true /test hco-e2e-consecutive-operator-sdk-upgrades-aws
ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws db22a38 link true /test hco-e2e-upgrade-prev-operator-sdk-aws
ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws db22a38 link false /test hco-e2e-upgrade-operator-sdk-sno-aws
ci/prow/hco-e2e-operator-sdk-aws db22a38 link true /test hco-e2e-operator-sdk-aws
ci/prow/hco-e2e-operator-sdk-sno-aws db22a38 link false /test hco-e2e-operator-sdk-sno-aws

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.

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

Reviewers

@machadovilaca machadovilaca Awaiting requested review from machadovilaca
@orenc1 orenc1 Awaiting requested review from orenc1

Assignees

No one assigned

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@tiraboschi @kubevirt-bot @coveralls