+++ This bug was initially created as a clone of Bug #1756981 +++
Description of problem:
When a Network Policy is enforced, an update of the SG of a LBaaS affected by the Network Policy is triggered. However, when checking if the k8s service should be affected by the Network Policy, services without selector are also taken into account and they shouldn't as Kuryr does not wires them.
Also it's assumed that the ports field will be always defined in the service specification and this might not always happen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run the Kubernetes Upstream Network Policy e2e test: "should enforce updated policy"
--- Additional comment from Ben Bennett on 2019-09-30 08:31:39 EDT ---
If this needs to be fixed in 4.2, then please clone this bug and set it to 4.2.z. I don't think this is a release blocker.
--- Additional comment from Ben Bennett on 2019-10-01 15:40:39 EDT ---
Feels too late for 4.2.0. Let's fix this in 4.2.1.
Verified on OCP 4.2.0-0.nightly-2019-10-25-021846 build on top of OSP 13 2019-10-01.1 puddle.
release image: registry.svc.ci.openshift.org/ocp/release@sha256:8f97aa21e1c0b2815ec7c86e4138362940a5dcbc292840ab4d6d5b67fedb173f
K8s NP (test/e2e/network/network_policy.go) tests passed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.