Bug 1828388

Summary: NPs on svc not enforced when exposed port and target are different
Product: OpenShift Container Platform Reporter: Luis Tomas Bolivar <ltomasbo>
Component: NetworkingAssignee: Luis Tomas Bolivar <ltomasbo>
Networking sub component: kuryr QA Contact: Jon Uriarte <juriarte>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: gcheresh, juriarte, vlaad, zyu
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1828387
: 1828699 (view as bug list) Environment:
Last Closed: 2020-05-18 13:35:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1828387    
Bug Blocks: 1828699    

Description Luis Tomas Bolivar 2020-04-27 16:06:14 UTC 
+++ This bug was initially created as a clone of Bug #1828387 +++

NP rules are not properly updated on LoadBalancer security groups when the exposed port and the target port does not match
Comment 3 Jon Uriarte 2020-05-11 11:10:15 UTC 
Verified in 4.4.0-0.nightly-2020-05-08-224132 on top of OSP 16 compose RHOS_TRUNK-16.0-RHEL-8-20200506.n.2 (with OVS and amphora-driver).

After creating a service that exposes a different port than the one in the pod behind, if a network policy is created for blocking the ingress
traffic to the pod, the security rules are now applied in the load balancer and the service is not reachable.
Comment 5 errata-xmlrpc 2020-05-18 13:35:03 UTC 
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.

https://access.redhat.com/errata/RHBA-2020:2133