Closed liudf0716 closed 4 years ago
it seems vpp must checkout to 5b786fb89483a77614dd40e8959463816d79fcbb to solve above problem
@liudf0716 the VPP 20.01 you've used before contained changes in the API not compatible with the VPP agent (i.e. newer than supported), so as you already mentioned you have to use the exact commit.
@VladoLavor thanks for your kindly answer. anyway, I have a question : why not use v20.01-rc0 tag but that commit?
@liudf0716 It's because we usually update current development version (master branch) of VPP several times between XX.YY-rc0
and XX.YY-release
to minimize the amount of work needed (small batches of API changes) and catch possible issues more early.
@ondrej-fabry thanks maybe it will lead to confusion for newcomer
@liudf0716 The requirements to support a particular commit from the VPP master branch comes from other project that collaborate with Ligato. We always inform about changes of VPP compatibility in our CHANGELOG.
@ondrej-fabry Ok, get it thanks!
I used vpp-agent v2.3.0 and vpp 20.01rc0, after the following operations, encount error
my vpp.env is
make agent it's ok, then execute vpp-agent, show the following error
I add log in file vendor/git.fd.io/govpp.git/core/channel.go
after make agent and execute vpp-agent, show the following error