[15:47] <stealthadmin> Hello, I am trying to preseed an 18.04 ubuntu server installation. I have tried using a debian preseed file and passing the path of the file to the kernal on install. This preseed file has been validated by debian-installer and was previously used for a 14.04 instalation. We have also investigated using an answers.yaml file to seed the installation, but there is not much documentation on this method. Have there been breaking changes f
[15:50] <CarlFK> answers.yaml?
[15:51] <CarlFK> I would post the details of your problem  - like you don't even say you have a problem
[15:54] <stealthadmin> I am unable to seed the installation. When booting the live iso, none of the preseeded values have been used.
[15:56] <stealthadmin> From what I can tell, answers.yaml is another way to preseed subiquity. Although the only references I can find are here: https://ubuntuforums.org/showthread.php?t=2390710 and here https://github.com/CanonicalLtd/subiquity/blob/master/examples/answers.yaml
[15:59] <CarlFK> unable to seed - how are you giving the file to the installer?
[15:59] <CarlFK> I host it on a http server on my lan, and add a kernel append: url=hostname
[16:00] <CarlFK> it sounds like the installer isn't aware of your file
[16:00] <stealthadmin>  By passing the file path to the kernal as a parameter : file=/cdrom/preseed/mypreseed.seed
[16:01] <CarlFK> try url=file://cdrom/...  or maybe  url=file:///cdrom...
[16:02] <CarlFK> I think I have seen file= but I am not sure now
[16:02] <stealthadmin> Ok let me give that a try. Is there somewhere in a log that would say it failed to find the file?
[16:03] <CarlFK> for me, the installer errors and halts.  but I also have debug=5 or something that might cause that
[16:03] <stealthadmin> I have been trying to follow this documentation: https://help.ubuntu.com/lts/installation-guide/s390x/apbs01.html#preseed-methods
[16:05] <CarlFK> if you want to try to trace what I use.. which works, but is pretty convoluted...
[16:05] <CarlFK> https://salsa.debian.org/debconf-video-team/ansible/blob/master/scripts/mk_usb_installer.sh#L29
[16:06] <CarlFK> the preseed files are way over here: https://salsa.debian.org/debconf-video-team/ansible/tree/master/roles/tftp-server/files
[16:07] <CarlFK> because they get used by both "mk usb install media" and "pxe boot the installer"
[16:07] <CarlFK> the usb stick is made with that shell script, the pxe server is built with ansible - using the same files for both is ... convoluted
[16:11] <stealthadmin> Is the debug level for the installer something I can also pass as a kernal parameter?
[16:13] <CarlFK> yes
[16:13] <CarlFK> loking ... it is in/around that script...
[16:15] <CarlFK> https://salsa.debian.org/debconf-video-team/ansible/blob/master/scripts/syslinux.cfg#L5
[16:15] <CarlFK> APPEND --- debconf/priority=high auto=true netcfg/dhcp_timeout=60
[16:15] <CarlFK> debconf/priority=high
[17:02] <stealthadmin> Ok I think it might be a problem for how I am creating the iso. I will look over your script and keep playing with it. Thank you for the help.
[17:04] <CarlFK> are you burning to CD or making a usb thumb drive?
[17:05] <CarlFK> I 'hate' making CDs - so hard to make changes
[17:05] <stealthadmin> Using a thumbdrive. Me too haha, CDs are the worst
[17:14] <CarlFK> you might want to try that script - it tries to support Ubuntu too
[17:15] <CarlFK> I waffle between ubuntu and debian - currently using debian because it is more tested, and I haveent taken the time to test ubuntu in  a while