[K8s] Build 4.0.0.0-3041: Removal of member from loadbalacer pool leaving junk entry in nh --get output
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
Medium
|
RAVI KIRAN | |||
R3.2 |
Fix Committed
|
Medium
|
RAVI KIRAN | |||
Trunk |
Fix Committed
|
Medium
|
RAVI KIRAN |
Bug Description
Steps to reproduce
-------
1. Create Service in kubernets pointing to replication controller(rc) of 3 members.
So Service has 3 backends. ECMP composite nexthop for Service IP pointing to 3 entry.
2. Change the replica count in rc to higher value . Say 100
Service has 100 backends. ECMP composite nexthop for Service IP pointing to 100 entry.
3. Bring back replica value to 3.
Here all the 97 composite nexthop is removed and replaced with -1 entry. and "vRouter(Response): No such device " log is coming
root@kube-
10.100.51.120/32 32 P - 420 -
root@kube-
Id:420 Type:Composite Fmly: AF_INET Rid:0 Ref_cnt:3 Vrf:1
Valid Hash Key Parameters: Proto,SrcIP,
Sub NH(label): 19(20) 27(21) 23(19) -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
Id:19 Type:Encap Fmly: AF_INET Rid:0 Ref_cnt:3 Vrf:1
Encap Data: 02 92 7b 93 ea fa 00 00 5e 00 01 00 08 00
Id:27 Type:Encap Fmly: AF_INET Rid:0 Ref_cnt:3 Vrf:1
Encap Data: 02 92 fd 13 70 fa 00 00 5e 00 01 00 08 00
Id:23 Type:Encap Fmly: AF_INET Rid:0 Ref_cnt:3 Vrf:1
Encap Data: 02 92 b2 0e 20 fa 00 00 5e 00 01 00 08 00
vRouter(Response): No such device (19)
vRouter(Response): No such device (19)
vRouter(Response): No such device (19)
vRouter(Response): No such device (19)
vRouter(Response): No such device (19)
vRouter(Response): No such device (19)
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Hari Prasad Killi (haripk) |
milestone: | none → r4.0 |
information type: | Proprietary → Public |
While nh utility is expanding all sub-NHs, it has to ignore cases where the index is -1.