[k8s-R5.0]: Firewall policy corresponding to Ingress-Service do not get deleted if kube-manager is restarted

Bug #1766174 reported by Pulkit Tandon on 2018-04-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Fix Released
Medium
Dinesh Bakiaraj
Trunk
Fix Released
Medium
Dinesh Bakiaraj

Bug Description

BUG Template:

Configuration:
K8s 1.9.2
coat-5.0-30
Centos-7.4

Setup:
5 node setup.
1 Kube master. 3 Controller.
2 Agent+ K8s slaves

Issue description:
Created a K8s-Ingress object with backend as a service.
Corresponding to that, a firewall policy get created for allowing traffic from Ingress to Service.
Now, restart the kube-manager.
Post restart, all basic checks were fine.

Now delete the k8s-Ingress.
The firewall policies created by contrail corresponding to that Ingress will not get deleted.

Test script to verify the same issue:
test_ingress_isolation_post_kube_manager_restart

Pulkit Tandon (pulkitt) wrote :

Issue has been fixed about a month back. Hence clsoing.
Recently run on R5.0-86 and master-124.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers