[openshift-4.22] OCPBUGS-92656: revert: backport dual-stack IPFamilyPolicy and upstream test skips to 4.22 OTE

[redhat-chai-bot]

This reverts merge commit f622188 (PR #480) which broke 4.22 nightlies on metal platforms.

Root cause

The GetCloudConfig() call added in main.go invokes framework.LoadConfig() which initializes klog. On 4.22, klog writes INFO-level lines to stdout. When openshift-tests runs the OTE binary's list subcommand, it expects pure JSON on stdout but gets klog noise instead, causing invalid character 'I' looking for beginning of value errors.

This worked on 5.0 because OTE PR #74 makes openshift-tests-extension scan for the first { or [ line before unmarshalling, tolerating stdout contamination. The 4.22 branch uses an older openshift-tests-extension without this fix.

Failing jobs

• metal-ipi-ovn-ipv4 (blocking)
• metal-ipi-ovn-ipv6 (blocking)

See payload analysis for details.

A fix-forward PR will follow that re-lands the dualstack changes with an updated openshift-tests-extension dependency to resolve the klog/JSON parsing issue.

/cc @mtulio

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-92656, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

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:

This reverts merge commit f622188 (PR #480) which broke 4.22 nightlies on metal platforms.

Root cause

The GetCloudConfig() call added in main.go invokes framework.LoadConfig() which initializes klog. On 4.22, klog writes INFO-level lines to stdout. When openshift-tests runs the OTE binary's list subcommand, it expects pure JSON on stdout but gets klog noise instead, causing invalid character 'I' looking for beginning of value errors.

This worked on 5.0 because OTE PR #74 makes openshift-tests-extension scan for the first { or [ line before unmarshalling, tolerating stdout contamination. The 4.22 branch uses an older openshift-tests-extension without this fix.

Failing jobs

• metal-ipi-ovn-ipv4 (blocking)
• metal-ipi-ovn-ipv6 (blocking)

See payload analysis for details.

A fix-forward PR will follow that re-lands the dualstack changes with an updated openshift-tests-extension dependency to resolve the klog/JSON parsing issue.

/cc @mtulio

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: 95380f5c-6339-4137-a858-7f2251180f25

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[mtulio]

/retitle "[openshift-4.22] OCPBUGS-92656: revert: backport dual-stack IPFamilyPolicy and upstream test skips to 4.22 OTE"

[mtulio]

/retitle [openshift-4.22] OCPBUGS-92656: revert: backport dual-stack IPFamilyPolicy and upstream test skips to 4.22 OTE

[mtulio]

Fix proposal is in progress at #482 , if there is green we prefer there than reverting changes.
/hold

[openshift-ci]

@redhat-chai-bot: 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.

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-92656. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

This reverts merge commit f622188 (PR #480) which broke 4.22 nightlies on metal platforms.

Root cause

The GetCloudConfig() call added in main.go invokes framework.LoadConfig() which initializes klog. On 4.22, klog writes INFO-level lines to stdout. When openshift-tests runs the OTE binary's list subcommand, it expects pure JSON on stdout but gets klog noise instead, causing invalid character 'I' looking for beginning of value errors.

This worked on 5.0 because OTE PR #74 makes openshift-tests-extension scan for the first { or [ line before unmarshalling, tolerating stdout contamination. The 4.22 branch uses an older openshift-tests-extension without this fix.

Failing jobs

• metal-ipi-ovn-ipv4 (blocking)
• metal-ipi-ovn-ipv6 (blocking)

See payload analysis for details.

A fix-forward PR will follow that re-lands the dualstack changes with an updated openshift-tests-extension dependency to resolve the klog/JSON parsing issue.

/cc @mtulio

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.