Repository navigation
Bump rpm deps to pick up qemu-img 10.1.0-24.el9 - #4269
Conversation
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]>
|
Hi @lexfrei. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions 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. |
|
/approve |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/override pull-containerized-data-importer-e2e-ceph-wffc |
|
@akalenyu: Overrode contexts on behalf of akalenyu: pull-containerized-data-importer-e2e-ceph-wffc DetailsIn response to this:
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. |
What this PR does / why we need it:
make rpm-depson 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-nextis replaced byopenssl-fips-providerfrom openssl 3.5.8,yajlbyjson-cbehind crun 1.29, andcurl-minimalon aarch64 bycurl. Alsomake rpm-depsis not fully deterministic here. A second run flippedopenssl-fips-providerback tofips-provider-nextin the aarch64 and s390x importer trees andcurlback tocurl-minimalintestimage_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 onopenssl-fips-providerandcurl.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: