NP rules are not properly updated on LoadBalancer security groups when the exposed port and the target port does not match
Verified in 4.5.0-0.nightly-2020-05-06-003431 on top of OSP 16 compose RHOS_TRUNK-16.0-RHEL-8-20200427.n.0 (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.
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.