The issue with the missing domain name in /etc/hosts with hostfile-update, as mentioned above, seems to trigger another problem. The hostname requested by the client seems to be added to /etc/hosts verbatim and some clients (eg. some Windows machines and printers) request a fully qualified name with a trailing dot. Since pdns-recursor unconditionally appends a dot, there are now two trailing dots, causing pdns-recursor to crash if it restarts.

I said it in the PR, but I'll say it here too -- I really don't have an idea, nor do I have enough knowledge of the codebase to get debugging data. I suspect that partprobe is either getting an error back from the kernel or is throwing its own error, and partx isn't. if I could step through the process and look at a couple things (like, is some partition actually mounted when partprobe runs, which could trigger this?) I would, assuming I've got the spare cycles. I don't at the immediate moment, and especially not to run through the code to try and figure out debugging on my own. Even being told "set debug here, here, and here, then retry the install" would help.

Is this still an issue on newer rolling images? This PR addresses ownership issues in /config on system update: https://github.com/vyos/vyos-1x/pull/2731

How come partprobe fails but not partx?

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

PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/2763

The fix from 1.5 was actually not backported. Thanks for testing and feedback

This affected my install. PR submitted with fix above (with very basic testing done successfully) in the link below.

Having support for vhost is handy when you dont want just to blindly share a single documentroot but have the ability to use multiple at a single host.

There is no redirect anymore

https://github.com/vyos/vyos-1x/pull/2758

Closed for implementation via T5886

same issue. but as a work around, instead of reinstalling, have you tried clearing /config/dhcp folder and create empty dhcp4-leases.csv dhcp4-leases.csv.2 with _kea:_kea permission.

It seems issues with migrations

[  OK  ] Reached target cloud-init.target - Cloud-init target.
[   28.675603] vyos-router[1767]: Waiting for NICs to settle down: settled in 0sec..
[   31.572854] vyos-router[1767]: Mounting VyOS Config...done.
[   42.670126] vyos-router[1767]: Starting VyOS router: migrate configure failed!
[   43.268753] vyos-config[1773]: Configuration error

PR https://github.com/vyos/vyos-vm-images/pull/42

Hopefully this can be resolved for VyOS 2.0 in the future...

Hopefully this can be resolved for VyOS 2.0 in the future...

New PR for dynamic address groups: https://github.com/vyos/vyos-1x/pull/2756

Mounting a ram disk on top should be pretty easy.
The question is, how much ram should be allocated for this, and how to make sure it doesn't run out of space.
I am no expert in logrotate, but it sounds like it should be able to do it.

Complete config
Admin@vyos:~$ show dhcp server leases

I've further determined that it also occurs if no container is attached to the network because the interface is only created when a container is attached.

Happy new year!

Can you provide your DHCP server config?

T4516 adds this functionality.

Workaround for clouds introduced in:
https://github.com/vyos/vyos-cloud-init/pull/68
https://github.com/vyos/vyos-cloud-init/pull/69

This might fix this problem
https://github.com/vyos/vyos-1x/pull/2752

Add please the simple examples with set of commands to reproduce

set xxxx x.x.xx