PRs:
https://github.com/vyos/vyos1x-config/pull/33
https://github.com/vyos/vyconf/pull/13

PR:
https://github.com/vyos/vyos-1x/pull/4300

Discussed and POC to be tested.

Add backport to Sagitta 1.4.1, needed by T6452.

PR:
https://github.com/VyOS-Networks/vyos-1x/pull/142

PR:
https://github.com/vyos/vyos-http-api-tools/pull/21
will replace the auto-generated
https://github.com/vyos/vyos-http-api-tools/pull/20

PR:
https://github.com/vyos/vyos-1x/pull/4213

There is current work that will be replacing the legacy show command, removing this bottleneck; related tasks will link here to keep track of progress.

@gadams it may well have been the case that the fragile synchronization before the fix was in fact a cause of the problem, at least in some (all ?) cases. I expected however, that any other config error on boot could also trigger the complaint in vyos-configd, which would consequently drop any useful output. With the original change in T6326 and the fix in T6899, any output (error or otherwise) should now be robust and generally available (notably, through the http-api, which was the motivation to finally fix the output workaround for T6326).

@gadams I agree with 2, as becomes apparent in the current situation: it is misleading and should be changed so as to avoid confusion. If you want to take it up, that would be great; thanks. Regarding 1, if you are seeing boot hangs on a system with the above fix, we will need to investigate: I have not encountered it, so I can try to reproduce with the following information: rolling version; sanitized config; platform (vm or hardware). I suggest opening as a separate task, as the forum reports so far (unless I'm mistaken) have pointed to this one. Thanks again for the info.

@opswill I suggest closing this task and opening a separate task focused on the specific continuing issue.

This is resolved for rolling, and not applicable to Circinus until backport of T6326.

@opswill Yes, those debug messages report that vyos-configd is operating correctly: error_code 1 is 'success' in the enum list. Consequently, the obscuring error in vyos-configd has been resolved, and the root cause of your issue can now be investigated ...

So yes, that's the idea, and the tools are there for a simple implementation (done in May, rebased now for comparison):
https://github.com/vyos/vyos-1x/compare/current...jestabro:example-property-secret

PR:
https://github.com/vyos/vyos-1x/pull/4202

The first three PRs above have been merged, and the next in sequence (https://github.com/vyos/libvyosconfig/pull/21) opened for review.

T6899 merged; when rolling available, kindly retest. Thanks !

This will be squashed with https://vyos.dev/T6326 for backport to Circinus, after confirmation.

This will need the fix in https://vyos.dev/T6899 for backport to Circinus.

Thanks @gadams , and yes that was also mentioned in the forum discussion here:
https://forum.vyos.io/t/vyos-sometimes-does-not-start-properly/15486
I believe the correction made in the PR for the parent task T6899 should help reveal/resolve the issue.

The PR for the parent task:
https://vyos.dev/T6899
will avoid obscuring underlying errors. Revisit after merge of above.

PR:
https://github.com/vyos/vyos-1x/pull/4197

As covered in last comment, all matters have been addressed, but for (then) open question re firewall migration. If that recurs, or still present, we will open a specific task.

As discussed a workaround is available, and preferable to the danger over usefulness of backporting to 1.3.x.

Adding that the long standing issue in T6543 is being addressed in the work of T6718, which provides a replacement to legacy loadConfig; the legacy code will not be corrected.

The only piece remaining here is a backport for Equuleus.

The specific high priority issue here was addressed in T6131; the general question of support for ZeroTier is in T6455. Closing this task as stated.

This will have a simple solution as a corollary of the work T6718: put on hold for now, pending restatement in terms of that work.