Skip to content

OCPBUGS-77942: Fix OLMv1 test operator to listen on IPv6#657

Open
stbenjam wants to merge 1 commit intoopenshift:mainfrom
stbenjam:fix-ipv6-test-operator-binding
Open

OCPBUGS-77942: Fix OLMv1 test operator to listen on IPv6#657
stbenjam wants to merge 1 commit intoopenshift:mainfrom
stbenjam:fix-ipv6-test-operator-binding

Conversation

@stbenjam
Copy link
Member

@stbenjam stbenjam commented Mar 6, 2026

Summary

  • The test operator's httpd script (python3 -m http.server) binds to 0.0.0.0 (IPv4 only) by default
  • On IPv6-only networks, startup/liveness/readiness probes fail because nothing listens on the IPv6 address
  • Adding --bind :: makes the server listen on all interfaces including IPv6

Impact

This is the root cause of the 0% all-time pass rate (58 runs, 0 passes since 2026-02-09) on:

  • periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-techpreview

The same OLMv1 tests pass at 98.83% on IPv4 clusters, confirming the failure is isolated to IPv6-only networks.

🤖 Generated with Claude Code

@openshift-ci openshift-ci bot requested review from oceanc80 and trgeiger March 6, 2026 19:00
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@stbenjam
Copy link
Member Author

stbenjam commented Mar 6, 2026

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

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

  • periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d9a49b50-198e-11f1-9b13-7f03b4eb9475-0

@stbenjam stbenjam changed the title Fix OLMv1 test operator to listen on IPv6 OCPBUGS-77942: Fix OLMv1 test operator to listen on IPv6 Mar 6, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 6, 2026
@openshift-ci-robot
Copy link

@stbenjam: This pull request references Jira Issue OCPBUGS-77942, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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:

Summary

  • The test operator's httpd script (python3 -m http.server) binds to 0.0.0.0 (IPv4 only) by default
  • On IPv6-only networks, startup/liveness/readiness probes fail because nothing listens on the IPv6 address
  • Adding --bind :: makes the server listen on all interfaces including IPv6

Impact

This is the root cause of the 0% all-time pass rate (58 runs, 0 passes since 2026-02-09) on:

  • periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-techpreview

The same OLMv1 tests pass at 98.83% on IPv4 clusters, confirming the failure is isolated to IPv6-only networks.

🤖 Generated with Claude Code

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.

@stbenjam
Copy link
Member Author

stbenjam commented Mar 6, 2026

/jira refresh

@openshift-ci-robot
Copy link

@stbenjam: This pull request references Jira Issue OCPBUGS-77942, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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.

Details

In response to this:

/jira refresh

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.

@stbenjam
Copy link
Member Author

stbenjam commented Mar 6, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 6, 2026
@openshift-ci-robot
Copy link

@stbenjam: This pull request references Jira Issue OCPBUGS-77942, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 6, 2026
@stbenjam
Copy link
Member Author

stbenjam commented Mar 7, 2026

The test operator's httpd script uses python3's http.server which
binds to 0.0.0.0 (IPv4 only) by default. On IPv6-only networks
(e.g. metal-ipi-ovn-ipv6-techpreview), the startup/liveness/readiness
probes connect to the pod's IPv6 address but nothing is listening,
causing the operator pod to never become Ready and the OLMv1
ClusterExtension install test to time out.

Adding --bind :: makes python3 http.server listen on all interfaces
including IPv6, fixing the test on dual-stack and IPv6-only clusters.

This resolves the 0% pass rate on:
- periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ipi-ovn-ipv6-techpreview

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@stbenjam stbenjam force-pushed the fix-ipv6-test-operator-binding branch from f7a613c to 3eb48e8 Compare March 7, 2026 02:08
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 7, 2026

@stbenjam: 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/e2e-aws-upgrade-ovn-single-node 3eb48e8 link false /test e2e-aws-upgrade-ovn-single-node

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants