[release-4.20] OCPBUGS-77148: Add config override for openflow-probe

[arkadeepsen]

Manual cherry pick from #2917 (commit cd14da6). No conflicts.

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-77148, which is invalid:

• expected dependent Jira Issue OCPBUGS-77147 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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:

Manual cherry pick from #2917 (commit cd14da6)

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: Pro

Run ID: de627a95-0bd8-4b74-aba8-ae91e9a10d9f

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
• Post copyable unit tests in a comment

---

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 and usage tips.}

[arkadeepsen]

/tide refresh

[arkadeepsen]

/retest-required

[liqcui]

/verified by @liqcui

[openshift-ci-robot]

@liqcui: This PR has been marked as verified by @liqcui.

Details

In response to this:

/verified by @liqcui

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.

[pperiyasamy]

/retest-required

[arkadeepsen]

/retest-required

[arkadeepsen]

/retest-required

[arkadeepsen]

The reason why e2e-aws-ovn-serial-1of2 is failing is explained in https://issues.redhat.com/browse/OCPBUGS-74237.

[Suite:openshift/machine-config-operator/disruptive][sig-mco][OCPFeatureGate:MachineConfigNodes] [Suite:openshift/conformance/serial][Serial]Should properly transition through MCN conditions on rebootless node update [apigroup:machineconfiguration.openshift.io]
{  fail [github.com/openshift/origin/test/extended/machine_config/machine_config_node.go:331]: Error, could not detect AppliedFilesAndOS=True.
Expected
    <bool>: false
to be true}

However, the fix wasn't backported to 4.20. Left a comment here for backporting the fix to 4.20.

[pperiyasamy]

/test 4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-77148, which is invalid:

• expected dependent Jira Issue OCPBUGS-77147 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

Details

In response to this:

Manual cherry pick from #2917 (commit cd14da6). No conflicts.

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.

[danwinship]

/lgtm

[liqcui]

/verified by @liqcui

[openshift-ci-robot]

@liqcui: This PR has been marked as verified by @liqcui.

Details

In response to this:

/verified by @liqcui

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 APPROVED

This pull-request has been approved by: arkadeepsen, danwinship

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 [danwinship]

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

[arkadeepsen]

@danwinship Can you please also add the backport-risk-assessed label?

[danwinship]

/label backport-risk-assessed

[arkadeepsen]

/test e2e-azure-ovn-upgrade

[arkadeepsen]

/test e2e-aws-ovn-hypershift-conformance

[openshift-ci]

@arkadeepsen: The following tests 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/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade	86e3c68	link	false	/test 4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade
ci/prow/security	86e3c68	link	false	/test security
ci/prow/4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade	86e3c68	link	false	/test 4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade

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.

[arkadeepsen]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-77147 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-77147 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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]

@arkadeepsen: Jira Issue OCPBUGS-77148: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

• openshift/ovn-kubernetes#2981 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-77148 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Manual cherry pick from #2917 (commit cd14da6). No conflicts.

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.

[arkadeepsen]

/jira backport release-4.19,release-4.18

[openshift-ci-robot]

@arkadeepsen: The following backport issues have been created:

• OCPBUGS-77150 for branch release-4.19
• OCPBUGS-77151 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18

Details

In response to this:

/jira backport release-4.19,release-4.18

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-cherrypick-robot]

@openshift-ci-robot: #2918 failed to apply on top of branch "release-4.18":

Applying: Add config override for openflow-probe
Using index info to reconstruct a base tree...
M	bindata/network/ovn-kubernetes/common/008-script-lib.yaml
M	pkg/network/ovn_kubernetes.go
M	pkg/network/ovn_kubernetes_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/network/ovn_kubernetes_test.go
CONFLICT (content): Merge conflict in pkg/network/ovn_kubernetes_test.go
Auto-merging pkg/network/ovn_kubernetes.go
CONFLICT (content): Merge conflict in pkg/network/ovn_kubernetes.go
Auto-merging bindata/network/ovn-kubernetes/common/008-script-lib.yaml
CONFLICT (content): Merge conflict in bindata/network/ovn-kubernetes/common/008-script-lib.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Add config override for openflow-probe

Details

In response to this:

@arkadeepsen: The following backport issues have been created:

• OCPBUGS-77150 for branch release-4.19
• OCPBUGS-77151 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.19,release-4.18

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.

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.

[openshift-cherrypick-robot]

@openshift-ci-robot: #2918 failed to apply on top of branch "release-4.19":

Applying: Add config override for openflow-probe
Using index info to reconstruct a base tree...
M	bindata/network/ovn-kubernetes/common/008-script-lib.yaml
M	pkg/network/ovn_kubernetes.go
M	pkg/network/ovn_kubernetes_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/network/ovn_kubernetes_test.go
CONFLICT (content): Merge conflict in pkg/network/ovn_kubernetes_test.go
Auto-merging pkg/network/ovn_kubernetes.go
Auto-merging bindata/network/ovn-kubernetes/common/008-script-lib.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Add config override for openflow-probe

Details

In response to this:

@arkadeepsen: The following backport issues have been created:

• OCPBUGS-77150 for branch release-4.19
• OCPBUGS-77151 for branch release-4.18

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.19
/cherrypick release-4.18

In response to this:

/jira backport release-4.19,release-4.18

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.

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.