DO NOT MERGE: OCPBUGS-103516: MADV_RANDOM removal on 4.22 (pre-6.4 kernel)

[hasbro17]

DO NOT MERGE — throwaway PR for perfscale data gathering only.

Adds a go.mod replace pointing bbolt at the openshift/bbolt release-5.0
fork (v1.4.3 with madvise(MADV_RANDOM) removed) on openshift-4.22,
which runs on RHCOS9 / kernel 5.14 (el9_8).

Purpose: a control-plane-fips-24nodes perfscale run to confirm removing
MADV_RANDOM does not regress on a pre-6.4 kernel — closing the second
prong of the upstream argument (etcd-io/bbolt#939) that removal is safe on
older kernels.

Context: the current 4.22 baseline (stock bbolt, MADV_RANDOM present) already
performs well on el9_8 — compaction ~1.6s, major faults ~11.5/s — because the
RHEL 9.6 page-cache revert carried forward. This run should show removal stays
at parity (~1.6s), i.e. no regression.

Do not merge or review — this branch will be deleted once the data is
collected.

Ref: etcd-io/bbolt#939
Ref: https://redhat.atlassian.net/browse/OCPBUGS-103516

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@hasbro17: This pull request references Jira Issue OCPBUGS-103516, which is invalid:

• expected the bug to target either version "4.22.0." or "openshift-4.22.0.", but it targets "5.0.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-103516 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

DO NOT MERGE — throwaway PR for perfscale data gathering only.

Adds a go.mod replace pointing bbolt at the openshift/bbolt release-5.0
fork (v1.4.3 with madvise(MADV_RANDOM) removed) on openshift-4.22,
which runs on RHCOS9 / kernel 5.14 (el9_8).

Purpose: a control-plane-fips-24nodes perfscale run to confirm removing
MADV_RANDOM does not regress on a pre-6.4 kernel — closing the second
prong of the upstream argument (etcd-io/bbolt#939) that removal is safe on
older kernels.

Context: the current 4.22 baseline (stock bbolt, MADV_RANDOM present) already
performs well on el9_8 — compaction ~1.6s, major faults ~11.5/s — because the
RHEL 9.6 page-cache revert carried forward. This run should show removal stays
at parity (~1.6s), i.e. no regression.

Do not merge or review — this branch will be deleted once the data is
collected.

Ref: etcd-io/bbolt#939
Ref: https://redhat.atlassian.net/browse/OCPBUGS-103516

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 4826570f-17da-4277-bbbd-f8a89e381118

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasbro17

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:

• OWNERS [hasbro17]

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

[hasbro17]

/payload-job periodic-ci-openshift-eng-ocp-perfscale-main-aws-4.22-nightly-x86-control-plane-fips-24nodes

[openshift-ci]

@hasbro17: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[hasbro17]

/payload-job periodic-ci-openshift-eng-ocp-perfscale-main-aws-4.22-nightly-x86-control-plane-fips-24nodes

[openshift-ci]

@hasbro17: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[hasbro17]

/payload-job periodic-ci-openshift-eng-ocp-perfscale-main-aws-4.22-nightly-x86-control-plane-fips-24nodes

[openshift-ci]

@hasbro17: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[afcollins]

/payload-job pull-ci-openshift-eng-ocp-perfscale-main-aws-4.22-nightly-x86-control-plane-fips-24nodes

[openshift-ci]

@afcollins: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[afcollins]

/test pull-ci-openshift-eng-ocp-perfscale-main-aws-4.22-nightly-x86-control-plane-fips-24nodes

[hasbro17]

/test perfscale-payload-control-plane-6nodes

[openshift-ci]

@hasbro17: all tests passed!

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.

[jtaleric]

/test ?

[openshift-ci]

@jtaleric: The following commands are available to trigger required jobs:

/test configmap-scale

/test e2e-aws-ovn

/test e2e-aws-ovn-serial

/test e2e-aws-ovn-upgrade

/test images

/test upstream-unit

The following commands are available to trigger optional jobs:

/test e2e-aws-etcd-recovery

/test e2e-hypershift

/test e2e-hypershift-conformance

/test perfscale-payload-control-plane-6nodes

/test upstream-e2e

/test upstream-integration

/test upstream-release

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-etcd-openshift-4.22-configmap-scale

pull-ci-openshift-etcd-openshift-4.22-e2e-aws-ovn

pull-ci-openshift-etcd-openshift-4.22-e2e-aws-ovn-serial

pull-ci-openshift-etcd-openshift-4.22-e2e-aws-ovn-upgrade

pull-ci-openshift-etcd-openshift-4.22-images

pull-ci-openshift-etcd-openshift-4.22-upstream-e2e

pull-ci-openshift-etcd-openshift-4.22-upstream-integration

pull-ci-openshift-etcd-openshift-4.22-upstream-release

pull-ci-openshift-etcd-openshift-4.22-upstream-unit

Details

In response to this:

/test ?

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.