NO-JIRA: DNM test afterburn main (coreos/afterburn#1251) via coreos/continuous

[qinqon]

DO NOT MERGE — PoC for testing only (x86_64).

Replaces afterburn in the OCP 4.22 node image with a prebuilt el9 RPM of afterburn main (afterburn-5.11.0-0.dev.pr1251.el9.x86_64.rpm, vendored in this PR), which includes coreos/afterburn#1251 — "kubevirt: Support static gateway and DNS with DHCP".

Why a vendored RPM (not the COPR)

The @CoreOS/continuous COPR builds afterburn main only for Fedora chroots; its centos-stream-9 / rhel-9 / centos-stream-10 builds fail, so there is no EL9-compatible afterburn RPM there to override from. The vendored RPM is built from afterburn main against EL9 (UBI9), so it links the RHEL 9.8 glibc/openssl the node image uses.

afterburn runs in the initramfs (afterburn-network-kargs, before ignition-fetch), so the override happens during build-node-image.sh (rpm-ostree override replace /run/src/afterburn-*.rpm) and the compose regenerates the initrd with the patched binary.

How to use (cluster-bot)

build 4.22,openshift/os#1944

Then set the returned release image on a HyperShift/KubeVirt NodePool:

oc patch nodepool <np> -n <hc-ns> --type=merge \
  -p '{"spec":{"release":{"image":"<pullspec>"}}}'

Verify on a node

rpm -q afterburn            # afterburn-5.11.0-0.dev.pr1251.el9
lsinitrd /usr/lib/modules/*/initramfs.img | grep afterburn

[openshift-ci-robot]

@qinqon: This pull request explicitly references no jira issue.

Details

In response to this:

DO NOT MERGE — PoC for testing only.

Replaces afterburn in the OCP 4.22 node image with the @CoreOS/continuous COPR build of afterburn main HEAD (currently afterburn-5.9.0.70.g9cc2a7b-6), which includes coreos/afterburn#1251 — "kubevirt: Support static gateway and DNS with DHCP".

afterburn runs in the initramfs (afterburn-network-kargs, before ignition-fetch), so the override is composed into the node image (rpm-ostree override replace during build-node-image.sh) and the compose regenerates the initrd with the patched binary. override replace is used because the main build (5.9.0.70) sorts below the shipped 5.10.0.

How to use (cluster-bot)

build 4.22,openshift/os#<this-PR>

Then set the returned release image on a HyperShift/KubeVirt NodePool to exercise the first-boot kubevirt network path:

oc patch nodepool <np> -n <hc-ns> --type=merge \
 -p '{"spec":{"release":{"image":"<pullspec>"}}}'

Verify on a node

rpm -q afterburn            # afterburn-5.9.0.70.g9cc2a7b-6
lsinitrd /usr/lib/modules/*/initramfs.img | grep afterburn

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: qinqon
Once this PR has been reviewed and has the lgtm label, please assign peacerebel 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:

• OWNERS

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

[openshift-ci]

@qinqon: The following test 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/images	5fd73bd	link	true	/test images

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.