You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pod container image points to ligato/vpp-agent:latest
As the pod starts there is a error in the logs:
level=error msg="getting resync data failed: resync returned error: given key \"config/vpp/v2/route/vrf/0/dst/0.0.0.0/0/gw/10.1.1.1\" does not match with key generated from value: \"config/vpp/v2/route/if/memif1/vrf/0/dst/0.0.0.0/0/gw/10.1.1.1\" (value: &vpp_l3.Route{Type:0, VrfId:0x0, DstNetwork:\"0.0.0.0/0\", NextHopAddr:\"10.1.1.1\", OutgoingInterface:\"memif1\", Weight:0x0, Preference:0x0, ViaVrfId:0x0, XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0})" loc="kvdbsync/watch_impl.go(101)" logger=defaultLogger
tagging the image as ligato/vpp-agent:v2.1.1 (as per the examples in sfc) solves this issue.
I can submit a PR to pin the images to 2.1.1, but there might be a deeper issue here which I could solve with some direction.
The text was updated successfully, but these errors were encountered:
pringlewood
changed the title
Ligato vpp-agent does not start when pulling latest
When running examples Ligato vpp-agent does not start when pulling latest
Aug 21, 2019
Thanks for pointing out to this. There is an API change in the newest vpp-agent version. Pinning to v2.1.1 is correct for now, we will move to the new API (and new vpp-agent tag in the examples) with the next Contiv release.
I am following the k8s examples for the memif
k8s/examples/memif/
The pod container image points to ligato/vpp-agent:latest
As the pod starts there is a error in the logs:
level=error msg="getting resync data failed: resync returned error: given key \"config/vpp/v2/route/vrf/0/dst/0.0.0.0/0/gw/10.1.1.1\" does not match with key generated from value: \"config/vpp/v2/route/if/memif1/vrf/0/dst/0.0.0.0/0/gw/10.1.1.1\" (value: &vpp_l3.Route{Type:0, VrfId:0x0, DstNetwork:\"0.0.0.0/0\", NextHopAddr:\"10.1.1.1\", OutgoingInterface:\"memif1\", Weight:0x0, Preference:0x0, ViaVrfId:0x0, XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0})" loc="kvdbsync/watch_impl.go(101)" logger=defaultLogger
tagging the image as ligato/vpp-agent:v2.1.1 (as per the examples in sfc) solves this issue.
I can submit a PR to pin the images to 2.1.1, but there might be a deeper issue here which I could solve with some direction.
The text was updated successfully, but these errors were encountered: