This errors out on VyOS 1.2.8
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 30 2021
@stepler on a fresh installation, all migration scripts will be run, as the default config contains no component version string, and has to be incrementally migrated.
I will push to have a solution included in 1.3, reviewing both zsdc's and rps's suggested patches; we will not hold up epa1 for this, but rather include as a bug fix following.
Not working on 1.4-rolling-202108300430 (results from livecd, same as new install; note the conntrack entries):
A careful analysis of the error here is provided in the last two comments; the general question of unicode support will be investigated in T3785.
Not quite there with the VNI configuration on 1.4-rolling-202108300430 (see middle vtysh output: VRF green has a VNI configured, but VRFs blue and red don't):
Looks good on 1.4-rolling-202108300430:
This is resolved for 1.3, and is not a backport candidate for 1.2, as indicated above.
cmd = {"op": "delete", "path": ["protocols","static","route", subnet, "next-hop", nexthop]}passed via the http-api properly returns the same error message as would be seen on the CLI. Non-issue.
Add key to successful commit.
set interfaces tunnel tun1 parameters ip key '1'
The revisions in T3768/T1950 provide a listing of components in /usr/share/vyos/component-versions.json for easy reference; this file is not used during migration, so any changes to the file will have no effect. The larger issue of dropping reliance on vyatta-cfg-system for component version information will be handled in T3474 for those components that have been moved to XML/Python.
T3785 is opened for the general issue; a workaround will be provided in the interim.