[00:34] <Kyoku> is the ubuntu core image for IoT fully encrypted?
[00:43]  * tomreyn pointed Kyoku to #snappy in #ubuntu-arm (CP)
[00:43] <mybalzitch> since you can install from it, I doubt it
[00:44] <genii> If it was, the passphrase/key would be identical on every machine it got installed to, defeating the purpose of having encryption
[00:46] <Kyoku> trying to find a guide to fully encrypt an ubuntu core image for Pi4 but not much luck, the general ones for ubuntu don't list core as a valid option
[00:47] <Kyoku> unless docs are just out of date
[00:47] <tomreyn> ubuntu desktop/server on the one hand and core on the other are really rather different systems, at least at this time.
[00:48] <tomreyn> see also https://ubuntu.com/core -> "Add-ons to SMART START" -> "Full Disk Encryption"
[00:53] <Kyoku> oh great, a $30,000 plugin just to get encryption
[00:53] <Kyoku> no thanks
[07:14] <lordievader> Good morning
[07:15] <cpaelzer> hiho lordievader
[07:15] <cpaelzer> how are you today?
[07:15] <lordievader> Hey cpaelzer, doing good here. How are you?
[07:15] <cpaelzer> good while fighting the world (of bugs)
[07:19] <lordievader> As regular ;)
[14:54] <coreycb> jamespage: sahid: I updated the dh-python patch in ca-patches. it switches python2-* to python-* binaries. something to keep an eye on if we get any odd behavior in that area. it should fix up the current sphinx backport failure.
[14:55] <jamespage> coreycb: great thanks for the headsup
[14:57] <sahid> coreycb: ack thanks
[20:54] <Olof_szary> hello, I am trying to install ubuntu server. The installer crashed in probert/storage.py on line 169. fdisk -l seems to see all the drives correctly
[20:55] <tomreyn> which version of ubuntu server is this, can you tell by the .iso name?
[20:56] <Olof_szary> is there any way to tell if from inside the boot system?
[20:57] <Olof_szary> 4.15.0-55-generic kernel, #60 Ubuntu
[20:57] <ChmEarl> bionic
[20:58] <Olof_szary> yes
[20:58] <ChmEarl> Eoan 19.10 has kernel-5.3+
[20:58] <Olof_szary> oh, I thought you meant the numeric number. It is bionic
[20:59] <tomreyn> bionic is now at linux-image-4.15.0-74-generic - so this *may* be 18.04.3
[20:59] <ChmEarl> its easy to tell from kernel version what release
[20:59] <tomreyn> so which is it?
[20:59] <Olof_szary> bionic. (as seen from /etc/apt )
[21:00] <Olof_szary> seems from Jul 2019
[21:00] <tomreyn> that'd be 18.04.3 indeed
[21:00] <tomreyn> now, is your goal identifying the root cause or getting the installation working?
[21:01] <ChmEarl> Olof_szary, might want to write zeros to the MBR of your install drive
[21:02] <Olof_szary> the ultimate goal is to have ubuntu server running on that machine
[21:02] <tomreyn> https://github.com/CanonicalLtd/probert/issues/77 https://bugs.launchpad.net/subiquity/+bug/1858447
[21:03] <Olof_szary> I believe the best bet is to get a newer version and try again. but also: since I am here in server room and don't want to go back to office to redownliad it, i was wondering if it's well know bug
[21:03] <Olof_szary> so, it was reported
[21:04] <tomreyn> do you have similar hardware (HW RAID, dell poweredge server) there?
[21:04] <Olof_szary> yes
[21:05] <tomreyn> it's a rather young report and there's no indication that it's been fixed yet so the workaround i had in mind, updating subiquity, may not help.
[21:06] <tomreyn> you could still try though ("snap refresh subiquity" from another tty)
[21:06] <Odd_Bloke> Some of the comments in that report suggest that it has been fixed already, so a refresh might do it.
[21:06] <tomreyn> Olof_szary: either way, please add what you can to qualify this report further, since it could use more info.
[21:06] <Olof_szary> what is interesting is that my collegue was able to install ubuntu desktop version here.
[21:07] <tomreyn> they use different installers, so it's not too surprising
[21:07] <Olof_szary> but ubuntu server fais
[21:07] <Olof_szary> ok
[21:08] <tomreyn> Odd_Bloke: right i missed comment 2
[21:09] <tomreyn> https://github.com/CanonicalLtd/subiquity/commit/8097ad62bf2072729bdee44c6d0e7e73e7b10429
[21:09] <Olof_szary> is gpm missing in ubuntu server?
[21:09] <Odd_Bloke> That does look like it would have fixed it.
[21:10] <tomreyn> a server with a mouse?
[21:10] <Odd_Bloke> Olof_szary: GPM?  (There is a package named gpm.)
[21:11] <Olof_szary> ok, it was not in the default installer, but apt-get update got the package
[21:11] <Olof_szary> https://github.com/CanonicalLtd/subiquity/commit/8097ad62bf2072729bdee44c6d0e7e73e7b10429
[21:11] <Olof_szary> sorry
[21:11] <Olof_szary> using elinks + gpm combo to follow the links
[21:12] <Olof_szary> ok, how to restart the installer?
[21:12] <tomreyn> you don't strictly need to view those web sites. either refreshing the snap helps or not
[21:14] <Olof_szary> error: requested a non-existing branch on latest/stable for snap "subiquity": ubuntu-18.04.3
[21:14] <Olof_szary> on: sudo snap refresh subiquity
[21:16] <tomreyn> oh interesting, it vanished off the snap store
[21:18] <Olof_szary> it seems that the bug in python is with using list instead of dictionary.
[21:19] <Olof_szary> but the file is not editable, since it is there: /dev/loop6       51M   51M     0 100% /snap/subiquity/1093
[21:22] <Olof_szary> So, best way to re-download the installer then, isn't it?
[21:22] <tomreyn> https://github.com/CanonicalLtd/subiquity discusses how to build your own installer
[21:23] <tomreyn> you could also try a daily image if there still are any, but those can be broken
[21:23] <tomreyn> or try your luck again here suring UK business hours
[21:23] <tomreyn> *during
[21:24] <Olof_szary> well, thanks
[21:28] <tomreyn> that would have been http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-live/current/