=== jaskal_ is now known as jaskal [11:51] Do I need to worry about any gotchas on a Ubuntu Server 18.04 -> 20.04 upgrade if I am using LXC/LXD + LXDUI? This is on ppc64el [12:58] dbungert: sorry to ping you again. 1) FYI, asap I will file a bug concerning subiquity and about my problem of "apt-get purge snapd", just in case. 2) Now, I have a problem with storage config in my user-data file which doesn't work (http://paste.alacon.org/47350). Have I missed something in the "storage" key of my user-data file? [13:01] dbungert: I have forgotten: the size of my swap file is not taken into account too. === genii-core is now known as genii [14:36] flaf: so the two partitions thing is expected, subiquity will look at incoming partitions and create a boot partition if it perceives that there isn't one. This appears to be BIOS boot but it still structures that first 1M as a partition. I think other systems just 'skip' 1MiB to achieve a similar effect. [14:37] line 94 in your paste needs to be 'mount', I think [14:41] dbungert: OK, I see for the first "bios" partition. So, in this case, my "number: 1" is incorrect in the "type: partition" item, no? I Have to set "number: X" where X start from 2, no? [14:43] I'm a little unclear on this part but I believe it gets renumbered for you due to the boot partition being created. I would leave it as 'number: 1' and try that. I think the 'noatime' problem is because the mount directives are being sent as type 'format' [14:43] dbungert: Thx. Indeed, I have made mistakes in the "mount" item and "format" item too. I try to fix, but it seems to me that my conf is still ignored. Furthermore the swap size is still ignored. [14:45] 256g swap looks fishy [14:45] meant to be 256m swap maybe/ === Avago_Broadqual2 is now known as Avago_Broadqual [14:45] dbungert: Yes I have fixed that too. [14:46] I'm trying a new version of user-data and I will show you if it doesn't work. Thx. [14:46] cool, good luck [14:46] :) [15:42] dbungert: sorry, "storage" still not work for me. I have put some details here https://gist.github.com/flaf/1d34ae7867374fe6ce36e37652de39d0 [15:44] As I explain in the gist, it seems that the "storage" part is completely overriden. [15:55] flaf: is this still a VM with a 5G disk? I wonder if the swap code is objecting to 1G swap in that state. [15:55] dbungert: the VM has just one disk of 5GB. [15:56] does a smaller size swap get respected? or does it just ignore entirely? [15:57] dbungert: in the gist, the file /var/log/installer/autoinstall-user-data has a "config" key completely overriden and the "swap" sub-key is not present. [15:58] dbungert: I can try a smaller swap size if you want (for instance 521M). [15:59] (oops 512M) [16:00] yea, I'm wondering if we're tripping some sort of free space check where it decides 1G is too large for the swap file on that disk size. [16:00] dbungert: during the install session, I wanted run something like that “h -c "LANG=C.UTF-8 python3 -m subiquity.cmd.tui --autoinstall /autoinstall.yaml"” but I have the error “ModuleNotFoundError: No module named 'subiquity'”. [16:01] the noatime option looks completely fine, other than I wonder if the yaml processing is objecting to the lack of quotes. If you quote it and it still gets ignored then that's 100% a bug [16:02] dbungert: is there a command I can run during the install session to check if the "/autoinstall.yml" file is correct? [16:02] like a schema check? or that it was downloaded and matching what you thought was there? [16:04] dbungert: a schema check. For me the file /autoinstall.yml is downloaded correctly but, after, the "storage" part seems to be ignored (I don't know why) so I would the check if the /autoinstall.yml file is fully OK for subiquity. [16:05] *I would like to... [16:06] we don't have an end-to-end tool covering that, though I would like us to. Parts are validated, but network and storage config get handed to curtin and netplan respectively. [16:07] dbungert: and do you know why in my case thes files "/autoinstall.yml" and "/var/log/installer/autoinstall-user-data" are not the same? [16:07] the /autoinstall.yml should be identical to the data you provide [16:08] it is the case. [16:08] autoinstall-user-data is the result after it has gone thru subiquity and come out the other end - we generate that file also for users who are just using the UI, so that they have a reference autoinstall file to start automation work with [16:09] I'm not worried about some minor rewriting of the curtin storage object IDs, because those values are arbitrary and just need to be self-consistent among the objects [16:09] but the missing swap and mount options is not good [16:10] dbungert: yes but there are another changes. [16:10] flaf: what else do you see? I'm interested in subiquity being able to round-trip autoinstall config. [16:11] dbungert: for instance id (in storage: => config:) are changed, name: and label: has been removed. [16:14] dbungert: it seems to me it's not a kind of rewriting, I think of a complete replace by a kind of defaut storage/config: [16:15] on your invocation of subiquity tui, I think you might have better luck with 'snap run subiquity' - that autoinstall location is picked up by default, and the tui cmd doesn't take an autoinstall arg [16:16] dbungert: FYI, I have just tried with "size: 521M" (for the swap) and the "swap:" key is ignored (in fact, just not present in `/target/var/log/installer/curtin-install-cfg.yml`. [16:16] ok, so I think the bug there is that swap and mount options are getting ignored [16:17] dbungert: and the label for the filesystem, and the name of the gpt partition too. [16:18] flaf: you've got some great data here, do you mind capturing it in a bug report? I don't want to lose this stuff. [16:19] dbungert: I can reproduce the problem automatically (I'm using packer). so no problem. [16:20] dbungert: so I will file 2 bugreport, 1) for "apt-get purge snapd" and 2) for the "storage" problem. [16:21] Probably this week-end. I will ping you with the link of the 2 bugreports here. [16:22] Anyway, thx for your help. The tool (subiquity) is very interesting. [16:22] Good chat flaf, I appreciate you stepping thru the debugging [16:22] :) [16:51] dbungert: I will file a bugreport, no problem with that. But just FYI, imho it's the complete sub-key `storage:` which is ignored (not just mount options, or swap size etc.). Indeed, I have tried a config with 2 patitiions "/" and "/var/log" (on the same disk) but in /target/var/log/installer/curtin-install-cfg.yaml, only one partition/mountpoint for "/". [16:51] (https://gist.github.com/flaf/1d34ae7867374fe6ce36e37652de39d0#gistcomment-3920831) [16:51] Got to go. Bye and thx again... === zareem5 is now known as zareem === sahilister5 is now known as sahilister === not_phunyguy is now known as phunyguy [23:16] Having a samba issue on ubuntu. I can't seem to connect. I set this up a year ago and it seems to be broke. Any two cents? I'm trying to connect to samba from OS X right now [23:18] If I make it browsable it works fine