Firstly, note that this is a failure in boot configuration, and is not related to migration: the log output of vyos-router is misleading, reporting the steps following initialization. On success:
Starting VyOS router: migrate configure
on failure:
Starting VyOS router: migrate configure failed !Adding vyos-config-debug to the boot options on first boot after installation will provide more information on the config error, if it is possible to try that; cf.:
https://docs.vyos.io/en/sagitta/contributing/debugging.html#kernel
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Jan 30 2024
Jan 30 2024
jestabro changed the status of T5980: Add image-tools support for configurable kernel boot options, a subtask of T5979: Add configurable kernel boot parameters, from Unknown Status to Resolved.
GitHub <[email protected]> committed rVYOSONEX8bd6c24b50a3: Merge pull request #2888 from vyos/mergify/bp/sagitta/pr-2886 (authored by jestabro).
a.apostoliuk changed the status of T5930: vrf - route-leak not work using route-target both command. from Open to In progress.
GitHub <[email protected]> committed rVYOSONEX02f7f91e3937: Merge pull request #2905 from vyos/mergify/bp/sagitta/pr-2877 (authored by c-po).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEX9eb129400dd5: vrf: T5973: fix has_rule() to check for l3mdev rule (authored by c-po).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEXf5590b63f2a8: vrf: T5973: move initial conntrack firewall table to startup (authored by c-po).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEX4d3df4402857: vrf: T5973: ensure Kernel module is loaded (authored by c-po).
GitHub <[email protected]> committed rVYOSONEXe13d901fd903: Merge pull request #2877 from c-po/vrf-5973 (authored by c-po).
GitHub <[email protected]> committed rVYOSONEX29045dff3845: Merge pull request #2904 from vyos/mergify/bp/sagitta/pr-2902 (authored by Viacheslav).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEX1e97bee82294: https: T6000: fix error in migration of path https certbot (authored by jestabro).
GitHub <[email protected]> committed rVYOSONEXe79fd8fff6de: Merge pull request #2902 from jestabro/migration-certbot (authored by c-po).
Viacheslav changed the subtype of T6000: [1.3.x -> 1.5.x] migrating threw exception in /opt/vyatta/etc/config-migrate/migrate/https/5-to-6, performed workaround from "Task" to "Bug".
Viacheslav triaged T6002: When using git as config-management commit-archive, comment is not used as commit message as Wishlist priority.
Jan 29 2024
Jan 29 2024
L0crian added a comment to T5991: 1.4.0-RC3 deleting portions of config in error (migration script).
Duplicate of https://vyos.dev/T3500
In T6001#174979, @fernando wrote:this command was added by default in FRR , but it's supported on lasted version (9.1):
https://docs.frrouting.org/en/latest/zebra.html#clicmd-ip-nht-resolve-via-default
https://docs.frrouting.org/en/latest/zebra.html#clicmd-ipv6-nht-resolve-via-default
as I mentioned , it was added in 9.1 as default behavior :
I was looking into the issue here on the forums for the user, i see the documentation says it should be enabled by default for the traditional profile which it appears to be set to use, but it does not work until i manually set that option through vtysh.
this command was added by default in FRR , but it's supported on lasted version (9.1):
jestabro added a comment to T5991: 1.4.0-RC3 deleting portions of config in error (migration script).
Firstly, note that this is a failure in boot configuration, and is not related to migration: the log output of vyos-router is misleading, reporting the steps following initialization. On success:
Starting VyOS router: migrate configure
on failure:
Starting VyOS router: migrate configure failed !
Sub-task merged and backported; I will close this as 'Resolved N/A', as described above.
jestabro moved T5994: Fix typo in 'remote' module preventing 'add system image' via ftp from Open to Finished on the VyOS 1.4 Sagitta board.
jestabro closed T5994: Fix typo in 'remote' module preventing 'add system image' via ftp as Resolved.
jestabro moved T5988: image-tools: a check of valid image name is missing from 'add image' from Open to Finished on the VyOS 1.4 Sagitta board.
jestabro closed T5988: image-tools: a check of valid image name is missing from 'add image', a subtask of T5987: 'add system image' with URL fails, as Resolved.
jestabro closed T5988: image-tools: a check of valid image name is missing from 'add image' as Resolved.
GitHub <[email protected]> committed rVYOSONEXb9005b289ef0: Merge pull request #2900 from vyos/mergify/bp/sagitta/pr-2899 (authored by jestabro).
GitHub <[email protected]> committed rVYOSONEX310c3f3b5c81: Merge pull request #2901 from vyos/mergify/bp/sagitta/pr-2898 (authored by jestabro).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEXacd01da06534: remote: T5994: fix typo in check_storage for Ftp class (authored by jestabro).
Mergify <37929162+mergify[bot]@users.noreply.github.com> committed rVYOSONEX923741ec9819: image-tools: T5988: validate image name in add_image (authored by jestabro).
The root issue could be in https://vyos.dev/T5611 T5611
Will take care about it after my vacation
In T5998#174912, @Viacheslav wrote:@stoicopa Do you have any ideas for CLI?
Viacheslav added a comment to T5999: load-balancing reverse-proxy can't configure root as a redirect.
Viacheslav renamed T5999: load-balancing reverse-proxy can't configure root as a redirect from load-balancing can't configure root as a redirect to load-balancing reverse-proxy can't configure root as a redirect.
Viacheslav triaged T5999: load-balancing reverse-proxy can't configure root as a redirect as Normal priority.
@stoicopa Do you have any ideas for CLI?
@cleopold73 Do you have any ideas for CLI?
Viacheslav edited projects for T5997: Support ssl backends on reverse-proxy, added: VyOS 1.5 Circinus; removed VyOS 1.2 Crux.
It is more of an upstream issue.
In addition, the PR already exists https://github.com/vyos/vyos-build/pull/438
Jan 28 2024
Jan 28 2024
Unknown Object (User) updated subscribers of T5619: Update the Intel ixgbe driver due to issues with Intel X533.
Why did you @Viacheslav lower the priority? It's basically broken currently.
GitHub <[email protected]> committed rVYOSONEX801359c2ebc7: Merge pull request #2898 from jestabro/validate-name (authored by dmbaturin).
GitHub <[email protected]> committed rVYOSONEX225b199ebe8c: Merge pull request #2899 from jestabro/typo-add-image-ftp (authored by dmbaturin).
jestabro added a comment to T5939: [1.3.5 -> 1.4.0-RC1 Migration] as-path-list Entries Get Messed Up.
Sub-task T5996.
jestabro triaged T5996: Incorrect behavior for backslash escapes in config save and compare commands as High priority.
Related to FRR logic
Won’t fix
Add a bug report on their repo
Jan 27 2024
Jan 27 2024
well i was checking this issue and i guess we had to concider
sarthurdev changed the status of T5993: DHCP6: no leases are created unless specifying a "interface" on the zone from Open to Confirmed.
sarthurdev changed the status of T5992: DHCP: show dhcp server leases not showing all leases from Open to Confirmed.
jestabro added a comment to T5994: Fix typo in 'remote' module preventing 'add system image' via ftp.
jestabro triaged T5994: Fix typo in 'remote' module preventing 'add system image' via ftp as Normal priority.
jestabro added a comment to T5988: image-tools: a check of valid image name is missing from 'add image'.
Viacheslav changed the status of T5991: 1.4.0-RC3 deleting portions of config in error (migration script), a subtask of T5938: Migration fail root task for 1.4-rc, from Open to Needs testing.
Viacheslav changed the status of T5991: 1.4.0-RC3 deleting portions of config in error (migration script) from Open to Needs testing.
Viacheslav triaged T5991: 1.4.0-RC3 deleting portions of config in error (migration script) as High priority.
Same as with https://vyos.dev/T5619.
Viacheslav triaged T5990: Intel 25G E810 kernel ice driver does not work with LLDP as Normal priority.
Jan 26 2024
Jan 26 2024
PR to fix here: https://github.com/vyos/vyos-1x/pull/2897
I have conducted additional testing. I can replicate the issue on a fresh VM. It seems the issue arises if the DHCP server is slow to respond upon bootup.