[02:19] hm === pieq_ is now known as pieq [06:41] Hi [06:41] i don't know you nickname (raharper ?) but i added required files : https://bugs.launchpad.net/subiquity/+bug/1906829 [06:41] Launchpad bug 1906829 in subiquity "autoinstall: set locale to fr_FR not working" [Undecided,Incomplete] [06:42] is there any "clean" workaround for this ? === cpaelzer_ is now known as cpaelzer === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie === sem2peie- is now known as sem2peie === ddstreet_away is now known as ddstreet === hggdh_ is now known as hggdh [13:47] seriously [13:48] i'm getting crazy with this new autoinstaller [13:48] each time i test something it is not working... [13:48] i spent 2 days on timezone setting [13:48] which is ignored [13:48] and still not working [13:49] https://x0.at/_cG.txt [13:49] this is config i'm using and its ignored ! [13:50] locales not working, timezone not working [14:00] i'm spent so many time on this [14:00] i'm exausted [14:00] i want to finish, each step is a mess [14:00] i opened 10 issues [14:00] please help === sem2peie- is now known as sem2peie [14:09] https://bugs.launchpad.net/subiquity/+bug/1907107 [14:09] Launchpad bug 1907107 in subiquity "autoinstall: timezone is ignored" [Undecided,New] === kleinkravis is now known as hydromalis === sem2peie- is now known as sem2peie === Guest44200 is now known as _hc === ijohnson is now known as ijohnson|lunch [19:10] mwhudson does post install script which runs at first startup uses the first sudo user ? [19:19] eoli3n: which script is that? cloud-init does it's stuff as root [19:31] here's my problem [19:32] http://sprunge.us/QooXyU [19:33] when i comment chroot line with ansible-pull run, then locales and timezone works [19:33] but when i run my ansible-playbook it fails. So i need to identify which tasks is breaking post script which setup timezone and locale generation at startup [19:33] the playbook has 400 tasks :/ [19:34] one is that i remove the first sudo user created by the installer [19:34] i'm testing piece by piece [19:34] but its really long [19:34] each iteration needs a new install to run [19:35] (i use qemu/kvm with ovmf then i can't use snapshots) [19:37] as this is running in chroot late_command could it break something ? (tasks which remove first user) === ijohnson|lunch is now known as ijohnson [20:38] eoli3n: the late-commands run as root but before first startup [20:38] yes i'm not talking about that [20:39] lets restart fresh [20:39] in late-commands, i run ansible [20:39] ok [20:39] inside that ansible playbook, there is one tasks which break something [20:40] because when i first boot, there are some scripts which finish to setup things right ? [20:40] right [20:40] those scripts doesnt work because timezone and locales are not working [20:40] if i comment out ansible-playbook run in late command, it works [20:40] then i need to identify which tasks break those first startup scripts [20:40] oh so something your ansible tasks are doing are breaking cloud-init [20:41] yes i think so [20:41] hmm [20:41] one of these tasks is first sudo user remover [20:41] well the sudo user is created by cloud-init, it won't be there when you run your tasks [20:41] as it runs as late command, it removes that user before first reboot [20:42] it may break some latelate scripts ? [20:42] oh ok [20:42] then i need to search more [20:42] actually [20:42] where are stored those first startup scripts ? [20:42] if you remove the identity section from your autoinstall config you won't get a user created at all [20:42] i can do that ?? [20:43] yes [20:43] nice [20:43] it's even documented! [20:43] hm, i didn't see that it was optionnal [20:43] sorry for that [20:43] i opened an issue about this [20:43] i will close it [20:43] https://ubuntu.com/server/docs/install/autoinstall-reference#user-data [20:43] i am pretty behind on bug mail :( [20:44] i didn't get what you mean [20:44] oh ! [20:45] if i set identity section, will it ignore user-data ? [20:45] because i set timezone in user-data [20:45] no they get merged [20:45] hm ok [20:45] (in a fairly unintelligent way, but that shouldn't matter here) [20:46] i fire all my questions because we are reverse about sleeping hours [20:47] what about multilines ? should "early-commands: |" works ? [20:47] no early-commands has to be a list [20:47] the entries in the list can be strings or lists though [20:47] that's sad [20:48] i open an issue about this too [20:48] ryan explained the trick to make these more comfortable right? [20:48] haharper gave me a curtin way [20:48] ah it was ryan [20:48] yes he does [20:48] he did [21:37] ok then i found that there is no problem [21:37] its just that scripts are triggered late [21:37] 4 min after startup [21:42] mwhudson why that behaviour ? why installer doesnt configure everything during install process ? [22:29] no especially good reason, it's just easier [22:29] 4 mins seems very slow [22:35] slow ?? :D [22:35] its an eternity [22:37] the problem seems more to be about cloud-config service (cloud-init ?) dependencies [22:37] it should run before anything else [22:37] just after networking.target [22:37] i fixed my ansible-pull service, adding cloud-init.target as Wants and After [22:38] that service has also Before=lightdm.service [22:38] so it should force the order, cloud-init -> ansible-pull -> lightdm [22:39] for now i get ansible-pull -> lightdm -> ... -> cloud-init [22:39] hope this will not slow down boot process [22:41] driveby sorry, I highlighted on cloud-init. also double check whatever your systemd dependency chain looks like now to make sure as well that something in the image didn't introduce an systemd ordering cycle issue journalctl -b | grep ordering cycle' as well as checking the system-analyze critical-chain on your units you are manipulating. [22:42] helpful tools to debug `cloud-init analyze blame` and `systemd-analyze blame` to checkout the worst offenders in boot [22:48] thanks blackboxsw, it's 23h48 here, lets check it tommorow [22:48] i note your commands [22:49] yowsa +1 [22:49] yowsa ? [22:49] yowsa == a very strange way to say "ohh my" [22:50] :) [22:51] blackboxsw but by default, cloud-init service should run before i get tty1 login ? [23:03] honestly not certain. but systemd-analyze critical-chain says system-logind waits on cloud-init completion https://paste.ubuntu.com/p/YQC9BSzQzr/ [23:05] strange, because, even with a "classic" autoinstall, after first reboot, i get tty1 login, then cloud-init runs and override prompt [23:05] that's dirty [23:08] lets sleep a bit, i on it since 7am without any stop, its 0am