Skip to content

Bump rpm deps to pick up qemu-img 10.1.0-24.el9 - #4269

Merged
kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
lexfrei:bump-rpm-deps-qemu-img-24
Sep 3, 2026
Merged

kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
lexfrei:bump-rpm-deps-qemu-img-24

Conversation

@lexfrei

@lexfrei lexfrei commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

make rpm-deps on top of main. The part that matters: qemu-img goes from 10.1.0-21.el9 to 10.1.0-24.el9 on all three arches. The rest is what CentOS Stream 9 moved since the last regeneration.

The 4k sector fix from #4179 did not make it into -21. v1.66.0 ships -21, and an HTTP import into a block device with 4096-byte logical sectors still fails with Failed to clear the new image's first sector: Invalid argument (#4175). qemu-kvm 10.1.0-24.el9 has the fix and landed on the mirror on 2026-08-25, three weeks after #4222 was closed.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):

Fixes #4175

Special notes for your reviewer:

I did not build the importer image from this tree, the qemu-img version is what the WORKSPACE diff says. What I have seen myself is the v1.66.0 importer failing the same HTTP-to-DRBD-block import that v1.64.0 completes.

The closure moved a bit with the versions: fips-provider-next is replaced by openssl-fips-provider from openssl 3.5.8, yajl by json-c behind crun 1.29, and curl-minimal on aarch64 by curl. Also make rpm-deps is not fully deterministic here. A second run flipped openssl-fips-provider back to fips-provider-next in the aarch64 and s390x importer trees and curl back to curl-minimal in testimage_aarch64, everything else came out identical, qemu-img included. Both are valid solutions and main already mixes the two. I committed the run where every tree agrees on openssl-fips-provider and curl.

I'd like to follow with a [release-v1.66] cherry-pick and, if that's fine with you, a v1.66.1: this is the one thing keeping the 1.66 line out of cozystack.

Release note:

BugFix: importing into a block device with 4k sectors failed with "Failed to clear the new image's first sector"; the importer now ships qemu-img 10.1.0-24.el9 which carries the fix

The 4k sector block device fix did not make it into the -21 build
that v1.66.0 ships: an HTTP import into a block device with 4096-byte
logical sectors still fails with "Failed to clear the new image's
first sector: Invalid argument". qemu-kvm 10.1.0-24.el9 carries the
fix and is available in CentOS Stream 9 now.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>
@kubevirt-prow kubevirt-prow 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 Sep 2, 2026
@kubevirt-prow
kubevirt-prow Bot requested review from Acedus and akalenyu September 2, 2026 19:14
@kubevirt-prow

kubevirt-prow Bot commented Sep 2, 2026

Copy link
Copy Markdown

Hi @lexfrei. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

@akalenyu

akalenyu commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm
thanks!

@kubevirt-prow kubevirt-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2026
@kubevirt-prow

kubevirt-prow Bot commented Sep 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akalenyu

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

@kubevirt-prow kubevirt-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 3, 2026
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 49.774% (+0.08%) from 49.697% — lexfrei:bump-rpm-deps-qemu-img-24 into kubevirt:main

@akalenyu

akalenyu commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

/override pull-containerized-data-importer-e2e-ceph-wffc
log substring flake

@kubevirt-prow

kubevirt-prow Bot commented Sep 3, 2026

Copy link
Copy Markdown

@akalenyu: Overrode contexts on behalf of akalenyu: pull-containerized-data-importer-e2e-ceph-wffc

Details

In response to this:

/override pull-containerized-data-importer-e2e-ceph-wffc
log substring flake

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-prow
kubevirt-prow Bot merged commit e03fbd0 into kubevirt:main Sep 3, 2026
21 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot import DV into a block device

3 participants