[release-4.17] OCPBUGS-39121: Live migration: report network overlap via live_migration_blocked metric

[openshift-cherrypick-robot]

This is an automated cherry-pick of #2482

/assign martinkennelly

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-39096 has been cloned as Jira Issue OCPBUGS-39121. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-39121: Live migration: report network overlap via live_migration_blocked metric

In response to this:

This is an automated cherry-pick of #2482

/assign martinkennelly

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-39121, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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.

In response to this:

This is an automated cherry-pick of #2482

/assign martinkennelly

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.

[martinkennelly]

/jira refresh

[openshift-ci-robot]

@martinkennelly: This pull request references Jira Issue OCPBUGS-39121, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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.

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.

[martinkennelly]

/jira refresh

[openshift-ci-robot]

@martinkennelly: This pull request references Jira Issue OCPBUGS-39121, 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.17.0) matches configured target version for branch (4.17.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-39096 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-39096 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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.

[kyrtapz]

/lgtm

[kyrtapz]

/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kyrtapz]

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

[asood-rh]

/label cherry-pick-approved

[martinkennelly]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 6da95cf and 2 for PR HEAD ab0eba9 in total

[openshift-ci]

@openshift-cherrypick-robot: 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/e2e-aws-hypershift-ovn-kubevirt	ab0eba9	link	false	/test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration	ab0eba9	link	false	/test e2e-aws-ovn-local-to-shared-gateway-mode-migration
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	ab0eba9	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/security	ab0eba9	link	false	/test security
ci/prow/4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade	ab0eba9	link	false	/test 4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

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]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-39121: All pull requests linked via external trackers have merged:

• openshift/cluster-network-operator#2483

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

In response to this:

This is an automated cherry-pick of #2482

/assign martinkennelly

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: cluster-network-operator
This PR has been included in build cluster-network-operator-container-v4.17.0-202410030534.p0.g3db5bd4.assembly.stream.el9.
All builds following this will include this PR.

[martinkennelly]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@martinkennelly: new pull request created: #2519

In response to this:

/cherry-pick release-4.16

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.