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.
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.