The initramfs-tools change is reasonable, but I disagree that the
dropbear behavior is "correct". The use of 'critical' for network
interfaces should be limited to those that actually need to be up for
the root filesystem to be available. Using dropbear for a one-time
unlock of the rootfs at boot is not that. Especially given that the
dropbear bottom hook /specifically deconfigures/ the network interface,
it should not be inducing netplan to output yaml that sets 'critical'.
Either the configure_networking function should be extended to take an
option to skip the 'critical' setting, or dropbear should do some
cleanup in its bottom script.
** Changed in: dropbear (Ubuntu Focal)
Status: Invalid => Triaged
** Changed in: dropbear (Ubuntu Groovy)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876884
Title:
netplan using incorrect renderer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1876884/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
