On Tue, Aug 25, 2020 at 02:20:50PM -0000, Balint Reczey wrote:
> @vorlon What is your plan regarding this fix? The revert may have helped
> MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
> fstab then MAAS should be fixed and not LXD images should be broken, so
> I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
> file which is not particularly beautiful, but not invalid at least.
MAAS images were broken because cloud-init could not handle the new
behavior. This is not the MAAS team's responsibility to fix, the Server
Team has been working on it with Dimitri; and having our MAAS images broken
was an unacceptable regression that was blocking kernel testing.
See the other linked bug, LP: #1890803, for details. If the
cloud-initramfs-tools change has landed, then the livecd-rootfs revert can
be reverted again.
On Tue, Aug 25, 2020 at 02:20:50PM -0000, Balint Reczey wrote:
> @vorlon What is your plan regarding this fix? The revert may have helped
> MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
> fstab then MAAS should be fixed and not LXD images should be broken, so
> I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
> file which is not particularly beautiful, but not invalid at least.
MAAS images were broken because cloud-init could not handle the new
behavior. This is not the MAAS team's responsibility to fix, the Server
Team has been working on it with Dimitri; and having our MAAS images broken
was an unacceptable regression that was blocking kernel testing.
See the other linked bug, LP: #1890803, for details. If the -tools change has landed, then the livecd-rootfs revert can
cloud-initramfs
be reverted again.