I use autoinstall to get my system installed in a specific state, then i need to boot that state. I want my tools to use that state (lightdm for exemple), so if cloud-config needs to run some tasks it should do it before i can interact with my system.
Is that normal that cloud-config starts after tty1 login, overriding prompt, messing up with term ? lightdm is not a script, is that normal that it starts before cloud-config ? lightdm starting with wrong timezone and locale is a bug, and not a lightdm one. Should I modify manually all units to wait for cloud-init.target ? I don't think so. Then cloud-config should run ealier in the boot process, and at first boot, lightdm should start with right timezone and locale set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907107 Title: cloud-init runs too late at first startup after ubuntu autoinstall To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1907107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
