User Details
- User Since
- Apr 12 2019, 4:27 PM (276 w, 17 h)
Yesterday
Thu, Jul 25
Time of task extended for testing.
Wed, Jul 24
Note that this is only a difference in formatting, not a change in error reporting; the formatting will be restored to the original behavior for consistency of parsing.
This was a result of changes to make error reporting more explicit in case of errors in config dependencies; I will realign with error reporting without vyos-configd.
Mon, Jul 22
Links for PR in preparation:
https://github.com/vyos/vyos1x-config/compare/current...jestabro:vy-adapter
https://github.com/vyos/vyatta-cfg/compare/current...jestabro:vy-adapter
https://github.com/vyos/vyos-1x/compare/current...jestabro:vy-adapter
https://github.com/vyos/libvyosconfig/compare/current...jestabro:vy-adapter
Wed, Jul 17
Mon, Jul 15
Fri, Jul 12
This was completed at the time of T5248.
Thu, Jul 11
The solution sketched above will be handled in subtask T6569; in this task we will revert to using only the local redundancy removal in order to provide per-script error reporting.
Mon, Jul 8
Recovering gracefully and logging an error is a simple fix, and will be committed in the interim while the larger issue is addressed: namely, when running under vyos-configd, a ConfigError in a called dependency script should elicit a commit error in the originating config session. Here, however, we confront again the constraints of operating under the legacy commit algorithm. To address the matter, we will implement a partial solution to T5731 so as to catch verification errors in the (first instance of) sequential processing of the priority queue and cache the data for final processing of the activation stages (generate/apply); errors in the latter stages, as less common, will be logged. The sketch provided summarizes a design that balances the needs of early and correct (verify stage) error reporting with removing redundancy overhead when running under configd.
Fri, Jul 5
Bug fix in case of empty config file component version string:
https://github.com/vyos/vyos-1x/pull/3788
Wed, Jul 3
@a.apostoliuk if you accept the explanation above and the workaround suffices (as recently discussed), we will close this task.
Adding parent T6543 as contributing factor of issue in comment:
https://vyos.dev/T5991#178786
The biosdevname question is a matter for T5603; this task will be closed.
A version of this change will be part of T5528, only for Circinus initially.
Spring cleaning PR:
https://github.com/vyos/vyos-1x/pull/3760
The critical issue was addressed in T5520, and the matter avoided with the move to revised image tools. No more to do on this at this point, and will close.
Tue, Jul 2
Added child/related task T6300; the issue is explained in the above comment and in that task. As has been discussed, the easiest workaround is to save the config on the source image before migrating --- backporting the rewrite of vyatta_net_name/vyatta_interface_rescan to 1.3.x will not resolve the issue for earlier images, so a workaround is needed in those cases.
Added parent task T5611; the issue is explained in the above comment and in that task. As has been discussed, the easiest workaround is to save the config on the source image before migrating --- backporting the rewrite of vyatta_net_name/vyatta_interface_rescan to 1.3.x, as mentioned in T5611, will not resolve the issue for earlier images, so a workaround is needed in those cases.
As mentioned above, the main regression was fixed; as to the other issue of "‘show system image’ list may not reflect the actual default boot image" I was unable to reproduce originally, but likely fixed as well, as the regression in question corrupted the image list and annotations. Close as fixed; reopen as needed.
This will be readied for PR without adding the external package vyos1x-adapter; that version has already been completed and will be linked below.
Fri, Jun 28
PR merged:
https://github.com/vyos/vyos-1x/pull/3692
Jun 24 2024
Jun 21 2024
My current understanding, and memory of its introduction, is that the settings os.environ[SUDO_*] were more than needed at the time, with a possible later use in mind: the only critical setting for vyos-configd as a dispatcher of config mode scripts is the preceding line: setgid(cfg_group.gid), allowing the config group access to generated files. Note that the environment variables are not currently used by conf-mode scripts, other than system_login.py, leading to the above bug.
Jun 20 2024
Draft PR passes configtests; dramatically faster:
https://github.com/vyos/vyos-1x/pull/3692
Minor integration and other testing remain before ready for review.
Jun 11 2024
Jun 6 2024
Resolved by T6006.
Resolved by PR merged in T6006.
Included in PR:
https://github.com/vyos/vyos-1x/pull/3587
PR:
https://github.com/vyos/vyos-1x/pull/3587
Companion PR's listed therein.