Bug 1828699: Ensure NP are enforced on SVC with different port and target port

[openshift-cherrypick-robot]

This is an automated cherry-pick of #223

/assign luis5tb

[openshift-ci-robot]

@openshift-cherrypick-robot: Not creating new clone for Bugzilla bug 1828388 as Bugzilla bug 1828699 has been detected as a clone for the correct target release of this cherrypick. Running refresh:
/bugzilla refresh

In response to this:

[release-4.3] [release-4.4] Bug 1828388: Ensure NP are enforced on SVC with different port and target port

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/test-infra repository.

[openshift-ci-robot]

@openshift-ci-robot: This pull request references Bugzilla bug 1828388, which is invalid:

• expected the bug to target the "4.3.z" release, but it targets "4.4.z" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

@openshift-cherrypick-robot: Not creating new clone for Bugzilla bug 1828388 as Bugzilla bug 1828699 has been detected as a clone for the correct target release of this cherrypick. Running refresh:
/bugzilla refresh

In response to this:

[release-4.3] [release-4.4] Bug 1828388: Ensure NP are enforced on SVC with different port and target port

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/test-infra 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/test-infra repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1828699, which is invalid:

• expected dependent Bugzilla bug 1828388 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is MODIFIED instead
• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.3] Bug 1828699: Ensure NP are enforced on SVC with different port and target port

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/test-infra repository.

[luis5tb]

/lgtm

[luis5tb]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: luis5tb, 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 [luis5tb]

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

[openshift-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci-robot]

@openshift-bot: This pull request references Bugzilla bug 1828699, which is invalid:

• expected dependent Bugzilla bug 1828388 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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/test-infra repository.

[openshift-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci-robot]

@openshift-bot: This pull request references Bugzilla bug 1828699, which is invalid:

• expected dependent Bugzilla bug 1828388 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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/test-infra repository.

[openshift-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci-robot]

@openshift-bot: This pull request references Bugzilla bug 1828699, which is invalid:

• expected dependent Bugzilla bug 1828388 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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/test-infra repository.

[luis5tb]

/bugzilla refresh

[openshift-ci-robot]

@luis5tb: This pull request references Bugzilla bug 1828699, which is invalid:

• expected dependent Bugzilla bug 1828387 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

[luis5tb]

/bugzilla refresh

[openshift-ci-robot]

@luis5tb: This pull request references Bugzilla bug 1828699, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.3.z) matches configured target release for branch (4.3.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1828388 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
• dependent Bugzilla bug 1828388 targets the "4.4.z" release, which is one of the valid target releases: 4.4.0, 4.4.z
• bug has dependents

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

[sdodson]

/retitle Bug 1828699: Ensure NP are enforced on SVC with different port and target port

[openshift-ci-robot]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: openshift/kuryr-kubernetes#227. Bugzilla bug 1828699 has been moved to the MODIFIED state.

In response to this:

Bug 1828699: Ensure NP are enforced on SVC with different port and target port

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/test-infra repository.