OCPSTRAT-3036: Temporarily skip API LBs follow /readyz of kube-apiserver and don't send request early test

[jubittajohn]

The "API LBs follow /readyz of kube-apiserver and don't send request early" test is temporarily skipped while investigating intermittent failures during the 1.36 rebase.

Summary by CodeRabbit

• Tests
  • Added a test case entry to track and handle a known issue (OCPBUGS-86789) in the APIServer component testing suite.

[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: automatic mode

[openshift-ci-robot]

@jubittajohn: This pull request references OCPSTRAT-3036 which is a valid jira issue.

Details

In response to this:

The "API LBs follow /readyz of kube-apiserver and don't send request early" test is temporarily skipped while investigating intermittent failures during the 1.36 rebase.

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 8d8eb871-cb85-4d4a-8332-a7e141e31096

📥 Commits

Reviewing files that changed from the base of the PR and between c0f50ac and 107ea67.

📒 Files selected for processing (1)

• pkg/test/extensions/disabled_tests.go

---

Walkthrough

A single disabled test entry is added to the "Broken" disablement map in the test extensions configuration, referencing issue OCPBUGS-86789 and disabling a sig-api-machinery APIServer test.

Changes

Test Disablement

Layer / File(s)	Summary
Add Broken test disablement pkg/test/extensions/disabled_tests.go	A new entry with an OCPBUGS-86789 issue reference is added to the "Broken" disabled-tests map, disabling a sig-api-machinery/APIServer/Late feature test.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly references the specific test being skipped (API LBs follow /readyz of kube-apiserver and don't send request early) and mentions the associated JIRA issue (OCPSTRAT-3036), which directly aligns with the change of adding a disabled test entry.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	Test name added contains only static descriptive strings with no dynamic values, timestamps, generated IDs, or other changing information.
Test Structure And Quality	✅ Passed	PR adds test name to disabled_tests.go disablement list, not modifying actual Ginkgo test code. Custom check applies to test implementation quality, not test disablement infrastructure.
Microshift Test Compatibility	✅ Passed	PR only adds a test name to a disabled tests configuration file; it does not add new Ginkgo e2e tests, so MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR does not add new Ginkgo e2e test definitions. It only adds a test name to a disabled tests filter for an existing upstream test, which is unrelated to SNO compatibility checks.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only a test configuration file listing disabled tests, not deployment manifests, operator code, or controllers with scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	PR adds a disabled test entry to a data structure within a regular function. No process-level code or stdout writes are present in the modified file.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only adds a disabled test entry in configuration; no new Ginkgo e2e test definition is added, so IPv6/disconnected network check does not apply.
No-Weak-Crypto	✅ Passed	PR adds only test metadata entries with no cryptographic implementations, weak crypto algorithms, or unsafe secret comparisons.
Container-Privileges	✅ Passed	Privileged settings (privileged: true, hostNetwork, runAsUser: 0) in test monitoring manifests are justified for API server disruption testing infrastructure.
No-Sensitive-Data-In-Logs	✅ Passed	PR adds no logging statements; only adds a test name and issue reference to a disabled tests configuration file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[jubittajohn]

/test images

[jubittajohn]

/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[jubittajohn]

/verified by ci

Run where test is not disabled

curl -sL "https://storage.googleapis.com/test-platform-results/pr-logs/pull/31153/pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2/2064028578751713280/artifacts/e2e-aws-ovn-serial/openshift-e2e-test/artifacts/junit/junit_e2e__20260608-180132.xml" | grep -i "API LBs follow"
<testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and stop sending requests [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T19:17:12Z" end-time="2026-06-08T19:17:12Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">
 <testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and don&#39;t send request early [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T19:20:04Z" end-time="2026-06-08T19:20:04Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">

CI job run from this PR:

curl -sL "https://storage.googleapis.com/test-platform-results/pr-logs/pull/31268/pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2/2064063069394309120/artifacts/e2e-aws-ovn-serial/openshift-e2e-test/artifacts/junit/junit_e2e__20260608-202444.xml" | grep -i "API LBs follow" 
<testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and stop sending requests [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T21:45:21Z" end-time="2026-06-08T21:45:21Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">

[openshift-ci-robot]

@jubittajohn: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

Run where test is not disabled

curl -sL "https://storage.googleapis.com/test-platform-results/pr-logs/pull/31153/pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2/2064028578751713280/artifacts/e2e-aws-ovn-serial/openshift-e2e-test/artifacts/junit/junit_e2e__20260608-180132.xml" | grep -i "API LBs follow"
<testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and stop sending requests [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T19:17:12Z" end-time="2026-06-08T19:17:12Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">
<testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and don&#39;t send request early [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T19:20:04Z" end-time="2026-06-08T19:20:04Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">

CI job run from this PR:

curl -sL "https://storage.googleapis.com/test-platform-results/pr-logs/pull/31268/pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2/2064063069394309120/artifacts/e2e-aws-ovn-serial/openshift-e2e-test/artifacts/junit/junit_e2e__20260608-202444.xml" | grep -i "API LBs follow" 
<testcase name="[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and stop sending requests [Suite:openshift/conformance/parallel]" time="0" start-time="2026-06-08T21:45:21Z" end-time="2026-06-08T21:45:21Z" lifecycle="blocking" source-image="tests" source-binary="openshift-tests">

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]

@jubittajohn: 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.