Myself I'm in favor of maintaining a fork and asking people to install it. We can add a version check to the ./configure script to make sure it stops and tells the user what to do if the version is not patched.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 5 2019
Oct 27 2019
Oct 24 2019
Oct 22 2019
Oct 21 2019
Oct 19 2019
Oct 15 2019
Oct 1 2019
Sep 30 2019
Sep 24 2019
Sep 17 2019
Sep 13 2019
Sep 11 2019
Sep 9 2019
Sep 6 2019
Works in the latest image for me.
It should have been fixed by https://github.com/vyos/vyos-1x/commit/ff05e2a90edf8af5d7b8ad5c69cae2dd40af2c8d It works for me in post-Sep 01 images and I don't see the error in the latest one, but I'm not sure why it would appear in the Sep 01 image if the commit is from Aug 30.
@nirmal The full fix is a bit more complicated. There are two cases: when it's called from conf mode at commit time, it needs to use the value from the proposed config (that's returnValue). However, in op mode, it also re-generates the config, so your fix would make the send dhcp6.client-id option disappear from the config when a user runs renew dhcpv6 interface .... A full fix needs to handle both cases and use returnEffectiveValue in op mode.
>>> s=""" ... foo { ... bar { ... baz quux foo ... } ... } ... """ >>> import vyos.configtree >>> c = vyos.configtree.ConfigTree(s) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/vyos/configtree.py", line 167, in __init__ raise ValueError("Failed to parse config: {0}".format(msg)) ValueError: Failed to parse config: Syntax error on line 4, character 14: Invalid syntax.
It was indeed a bug, caused by the same issue as all other subtasks of T1598: lack of proper synchronization.
If it re-appears, please reopen of course.
Disappearing entries should no longer be a problem, but if it re-appears due to a missing case, please reopen.
Sep 5 2019
Sep 1 2019
As a stopgap measure that allows old config to load, I've made the script cap it at 100:
Aug 31 2019
Cherry-picked into crux.
@rgrant I've cherry-picked it into Crux, will be in the 1.2.3 release soon.
Cherry-picked into crux.
Cherry-picked into crux.
Cherry-picked into crux.
CHerry-picked into crux.
Cherry-picked into crux.
Cherry-picked into crux.
Imported 2.0.17 into crux.
Aug 30 2019
Actually, there are already run monitor traffic interface $intf commands and they work fine in 1.2.3.
Aug 29 2019
Aug 27 2019
If it reappears, feel free to reopen.