OCPBUGS-44674: Handle openshift-host-network namespace as special when it modifies

[k37y]

• Add condition in NetworkPolicy updateMatchCache to handle HostNetworkNamespace changes

[openshift-ci-robot]

@k37y: This pull request references Jira Issue OCPBUGS-44674, which is invalid:

• expected the bug to target the "4.19.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.

In response to this:

• Add condition in NetworkPolicy updateMatchCache to handle HostNetworkNamespace changes

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.

[k37y]

/jira refresh

[openshift-ci-robot]

@k37y: This pull request references Jira Issue OCPBUGS-44674, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhaozhanqi

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.

[k37y]

/assign @danwinship

[danwinship]

openshift-sdn master is dead now (and in particular, there is no CI for openshift-sdn master any more). SDN bugs should be filed against 4.16 first, and then backported from there as needed. You can click the "Edit" button by the bug summary, and then that will let you change the base branch from openshift:master to openshift:release-4.16. (And you'll need to update the jira issue as well. You'll also need to create a dummy 4.17 version of the jira issue to make the 4.16 one "depends on", in order to get the openshift bots to be happy.)

[openshift-ci-robot]

@k37y: This pull request references Jira Issue OCPBUGS-44674, which is invalid:

• expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.19.0" instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-44674 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

• Add condition in NetworkPolicy updateMatchCache to handle HostNetworkNamespace changes

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]

@k37y: This pull request references Jira Issue OCPBUGS-44674, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhaozhanqi

In response to this:

• Add condition in NetworkPolicy updateMatchCache to handle HostNetworkNamespace changes

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]

@k37y: This pull request references Jira Issue OCPBUGS-44674, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.z) matches configured target version for branch (4.16.z)
• bug is in the state POST, 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-51269 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-51269 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0, 4.17.z
• bug has dependents

Requesting review from QA contact:
/cc @zhaozhanqi

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.

[k37y]

@danwinship, I have made the below changes to the Jira:

Target release: 4.16.0
Release note: Handle the openshift-host-network namespace as special and set the VNID as zero when it modifies.
Release note type: Bug Fix

And cloned 4.17.0 targeted Jira and closed it as Done.

[danwinship]

just a few minor things

[k37y]

/test e2e-gcp-sdn

[openshift-ci]

@k37y: 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/security	ab6af87	link	false	/test security

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.

[danwinship]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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

[danwinship]

/label backport-risk-assessed

[asood-rh]

/label cherry-pick-approved

[openshift-ci-robot]

@k37y: Jira Issue OCPBUGS-44674: All pull requests linked via external trackers have merged:

• openshift/sdn#648

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

In response to this:

• Add condition in NetworkPolicy updateMatchCache to handle HostNetworkNamespace changes

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: kube-proxy
This PR has been included in build kube-proxy-container-v4.16.0-202503051735.p0.gcbddb0b.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-sdn
This PR has been included in build ose-node-container-v4.16.0-202503051735.p0.gcbddb0b.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2025-03-05-204846