[11:51] <Avago_Broadqual> 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] <flaf> 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] <flaf> dbungert: I have forgotten: the size of my swap file is not taken into account too.
[14:36] <dbungert> 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] <dbungert> line 94 in your paste needs to be 'mount', I think
[14:41] <flaf> 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] <dbungert> 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] <flaf> 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] <dbungert> 256g swap looks fishy
[14:45] <dbungert> meant to be 256m swap maybe/
[14:45] <flaf> dbungert: Yes I have fixed that too.
[14:46] <flaf> I'm trying a new version of user-data and I will show you if it doesn't work. Thx.
[14:46] <dbungert> cool, good luck
[14:46] <flaf> :)
[15:42] <flaf> dbungert: sorry, "storage" still not work for me. I have put some details here https://gist.github.com/flaf/1d34ae7867374fe6ce36e37652de39d0
[15:44] <flaf> As I explain in the gist, it seems that the "storage" part is completely overriden.
[15:55] <dbungert> 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] <flaf> dbungert: the VM has just one disk of 5GB.
[15:56] <dbungert> does a smaller size swap get respected?  or does it just ignore entirely?
[15:57] <flaf> 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] <flaf> dbungert: I can try a smaller swap size if you want (for instance 521M).
[15:59] <flaf> (oops 512M)
[16:00] <dbungert> 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] <flaf> 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] <dbungert> 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] <flaf> dbungert: is there a command I can run during the install session to check if the "/autoinstall.yml" file is correct?
[16:02] <dbungert> like a schema check?  or that it was downloaded and matching what you thought was there?
[16:04] <flaf> 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] <flaf> *I would like to...
[16:06] <dbungert> 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] <flaf> 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] <dbungert> the /autoinstall.yml should be identical to the data you provide
[16:08] <flaf> it is the case.
[16:08] <dbungert> 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] <dbungert> 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] <dbungert> but the missing swap and mount options is not good
[16:10] <flaf> dbungert: yes but there are another changes.
[16:10] <dbungert> flaf: what else do you see?  I'm interested in subiquity being able to round-trip autoinstall config.
[16:11] <flaf> dbungert: for instance id (in storage: => config:) are changed, name: and label: has been removed.
[16:14] <flaf> 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] <dbungert> 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] <flaf> 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] <dbungert> ok, so I think the bug there is that swap and mount options are getting ignored
[16:17] <flaf> dbungert: and the label for the filesystem, and the name of the gpt partition too.
[16:18] <dbungert> 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] <flaf> dbungert: I can reproduce the problem automatically (I'm using packer). so no problem. 
[16:20] <flaf> dbungert: so I will file 2 bugreport, 1) for "apt-get purge snapd" and 2) for the "storage" problem.
[16:21] <flaf> Probably this week-end. I will ping you with the link of the 2 bugreports here.
[16:22] <flaf> Anyway, thx for your help. The tool (subiquity) is very interesting.
[16:22] <dbungert> Good chat flaf, I appreciate you stepping thru the debugging
[16:22] <flaf> :)
[16:51] <flaf> 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] <flaf> (https://gist.github.com/flaf/1d34ae7867374fe6ce36e37652de39d0#gistcomment-3920831)
[16:51] <flaf> Got to go. Bye and thx again...
[23:16] <foo> 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] <foo> If I make it browsable it works fine