[k8s-R5.0]: Firewall policy corresponding to Ingress-Service do not get deleted if kube-manager is restarted
Bug #1766174 reported by
Pulkit Tandon
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_
To post a comment you must log in.
Code review in progress: /review. opencontrail. org/#/c/ 42533/ /review. opencontrail. org/#/c/ 42553/
https:/
https:/