[07:58] <xnox> kentb-out: hm? driver-injection-disk/load has default as "true", so if the driver-injection-disk-detect udeb is present it should auto detect & use OEMDRV disk.
[11:13] <cjwatson> xnox: I'm working on bug 1197766, BTW - I think I see what you did wrong
[11:13] <ubot2`> Launchpad bug 1197766 in OEM Priority Project "Different partition layout after recovery with keep home partition" [Critical,Confirmed] https://launchpad.net/bugs/1197766
[11:14] <cjwatson> need to do the filtering in choose_recipe instead.  Trying a similar-but-different patch
[11:14] <xnox> hm. ok.
[11:15] <xnox> cjwatson: note that at the moment the workaround is to use "0 0 0" for the UEFI partition in the recipe. Then it's reused without affecting calculated size required.
[11:15] <cjwatson> min_size is too low-level to go modifying $scheme
[11:15] <cjwatson> mm, I guess that would work too
[13:19] <kentb> xnox: right. That's what I interpreted as well, but, it seems that if we don't do something like "anna/choose_modules=driver-injection-disk-detect" at the installer command line the dirver disk on USB stick won't get picked up (at least from what I can tell).  I'll be glad to try again without the command line parameters to be sure, but, we won't see
[13:19] <kentb> anything in /var/cache/firmware/ if we don't.  I could completely be missing something, though.
[13:21] <xnox> kentb: interesting, that indicates that driver-injection-disk-detect udeb is missing by default and needs a manual nudge to be fetched. What media are you installing from?
[13:22] <kentb> xnox: usb for the OS and then the driver disk on a separate USB stick, formatted fat32 with an OEMDRV label.  The anna portion of the command line is so far the nudge that it needed to load the driver-injection-disk udeb.
[13:22] <xnox> kentb: "usb for the OS" netinstall, server, mini image?
[13:23] <kentb> xnox: so, if there's a way to get that udeb loaded up by default, that'll be a big help (I think).
[13:23] <kentb> xnox: the server image in this case
[13:30] <xnox> cjwatson: infinity: driver-injection-disk-detect is currently "Priority: optional", is ok to bump it to "Priority: standard" such that it gets auto-loaded by default, as per ^
[13:32] <cjwatson> That's probably fine, but its value in the package makes no difference - it has to be overridden in the archive.
[13:33] <cjwatson> It'll slow down the installer a bit by iterating over all USB partitions.  Probably not significantly.
[13:34] <cjwatson> I dunno.  It does mean that if you leave a malicious stick inserted unwarily, it can silently own your installation, since driver-injection-disk/load is true by default and not displayed.
[13:34] <cjwatson> So it does make me a bit nervous.
[13:41] <xnox> and there is no signature checks / validation of the installed debs on the sticks.
[13:42] <xnox> =/ essentially an open backdoor into otherwise verified installation.
[13:42] <xnox> kentb: ^^^
[13:42] <kentb> xnox: right. understood.
[13:45] <cjwatson> Is it so bad to need to pass anna/choose_modules=driver-injection-disk-detect?  We could add an alias for that if it's just about length.
[13:55] <infinity> It's not wildly intuitive for the "average user".
[13:55] <infinity> But I'd expect a debconf template asking me if I want to use driver disks before scanning and copying willy-nilly.
[13:55] <infinity> (Which then adds another question if we make it a default component, which sucks)
[13:56] <kentb> cjwatson: what infinity said.  Plus we're looks to streamline the process a bit.  RHEL has it built into anaconda to check for those OEMDRV disks automatically.  Big picture, we're looking to get Ubuntu listed in the lifecycle controller on poweredge as an option to install the OS on poweredege servers.  RHEL, Windows, and SLES are on there now.  When you
[13:56] <kentb> select the OS, the lifecycle controller will provide out-of-box drivers via a virtual disk labeled OEMDRV.  It might be possible for the lifecycle controller folks to add that command line automatically, but, we're still working on getting our foot in the door with them so to speak.
[13:57] <infinity> Could we just scan and *if* we find OEMDRV disks, then trigger a yes/no template before doing Very Bad Things?
[13:58] <kentb> infinity: that'd be good, too.  That's how RHEL does it now.  It stops and asks even with the OS selected in lifecycle controller.
[14:04] <cjwatson> Yeah, if there were UI then I'd be less unhappy
[14:04] <cjwatson> (Preseedable, of course)
[14:05] <cjwatson> That's probably just a matter of lifting the priority of that question to high.
[14:05] <cjwatson> It's medium right now.
[14:06] <kentb> I'm game for whatever you guys think is the safest way to do it
[14:12] <infinity> cjwatson: Well, raising it to high would trip it all the time, wouldn't it?
[14:13] <infinity> cjwatson: (I haven't looked, but I assume it asks before scanning currently, rather than after)
[14:13] <cjwatson> No, it's only displayed if there's actually something to do
[14:13] <cjwatson>         if [ "$label" = "OEMDRV" ]; then
[14:13] <infinity> Ahh.
[14:13] <cjwatson>                 db_input medium driver-injection-disk/load || true
[14:13] <infinity> Well, that would be perfect, then.
[14:20] <kentb> indeed!
[14:24] <xnox> cjwatson: raise the priority on the question to high, raise the priority on the package, keep the default at true?
[14:26] <cjwatson> Sounds right
[14:36] <xnox> ack, will update merge proposal.
[18:57] <rostam> HI all,  so I have created a list of installed packages on my system: "dpkg --get-selections > my-packages". Now I have created kickstart/preseed iso image installing ubuntu 12.04 LTS.  How could I install packages listed in 'my-packages' during kickstart installation? thx
[21:13] <rostam> Hello, during custom installation Ubuntu 12.04 LTS server, I still get asked: "Write the changes to disks?" how could I preseed that please? thx
[21:32] <maxb> d-i partman/confirm boolean true
[21:32] <maxb> d-i partman/confirm_nooverwrite boolean true
[21:32] <maxb> rostam: ^
[21:33] <maxb> You can include just the _nooverwrite line to skip prompting only if there are no existing partitions that will be overwritten (fresh empty drives)
[22:00] <rostam> maxb: I did have the first d-i, but not the second one so I will try that now. Thanks
[23:32] <jbicha> xnox: ubiquity's autopkgtest fails because python3-oauthlib isn't installed, you can add dependencies to debian/tests/control if you need to
[23:32] <jbicha> https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/5989


[02:04] <alkisg> Guest65: grep fsck /usr/share/initramfs-tools/init
[02:04] <alkisg> forcefsck|fsck.mode=force) and	fsckfix|fsck.repair=yes)
[02:04] <alkisg> So these two parameters are supported, to automatically check and/or to fix
[17:05] <Guest65> v22, In grub menu I choose recovery, select fsck, and get this error: /lib/recovery-mode/recovery menu: line 80: /etc default/rcS: No such file or directory fsck from util-linux 2.37.2   /dev/sda2 is mounted. e2fsck: Cannot continue: aborting. Finished, please press ENTER.. any thoughts???


[16:01] <zaki> hmm
[17:30] <pavlushka> zaki: o/
[17:31] <pavlushka> zaki: https://www.youtube.com/watch?v=SbrgXE4KqdI
[17:31] <u-la-la> [ Knee vs Arslan Ash - Grand Finals Evo 2019 - Tekken 7 - Tekken World Tour - YouTube ] - www.youtube.com ( https://tinyurl.com/yxqo7e7b )
[17:37] <zaki> hey pavlushka
[17:44] <pavlushka> hello
[17:44] <pavlushka> zaki:
[17:58] <pavlushka> zaki: hello
[18:01] <zaki> pavlushka, how are you doing ?
[18:02] <pavlushka> doing okay
[18:02] <pavlushka> zaki: you?
[18:03] <zaki> pavlushka, i'm fine
[18:05] <pavlushka> zaki: haven't seen you around for a while, got your computer?
[18:05] <zaki> pavlushka, yea :)
[18:05] <zaki> pavlushka, yesterday
[18:05] <pavlushka> zaki: cool
[18:05] <pavlushka> zaki: config?
[18:05] <zaki> pavlushka, sudo hdparm -t --direct /dev/sdXn what this do?
[18:06] <pavlushka> zaki: reports hdd/ssd read/write speed
[18:06] <zaki> ah
[18:07] <zaki> pavlushka,
[18:08] <zaki> Timing O_DIRECT disk reads: 1164 MB in  3.00 seconds = 387.73 MB/sec
[18:08] <pavlushka> zaki: your machine specs?
[18:09] <zaki> pavlushka, HP EliteBook G2 i5 5300U
[18:10] <zaki> alada kore 256 ssd insert korsi
[18:10] <zaki> Transcend
[18:11] <pavlushka> zaki: I don't know if it will change or not but I will keep buying Lenovo thinkpads everytime :)
[18:12] <pavlushka> zaki: nice, 256! that will be enough for both /root and /home together I guess
[18:13] <zaki> he he :D great thinkpad is cool too.
[18:13] <zaki> pavlushka, yeah /root and /home everything
[18:13] <zaki> even windows :P
[18:15] <pavlushka> hahaha
[18:16] <zaki> yeah
[18:18] <zaki> what I'm enjoying most  is backlit keyboard
[18:57] <pavlushka> zaki: wow backlit!
[18:57] <zaki> pavlushka, yes
[19:32] <pavlushka> night night
[20:16] <zaki> good night


[08:51] <ffledgling> Hello, I'm trying to figure out how to get packages to install via cloud init behind a proxy, I haven't been able to find a good way to do so, are there any recommendations? Seems like there's an open bug about it - https://bugs.launchpad.net/cloud-init/+bug/1089405
[09:05] <b0stik> ffledgling, tried with a bash command to add a line for proxy in apt configuration ?
[09:11] <ffledgling> b0stik: That's the last resort, and I'm not sure if the `packages` directive from cloud config is run before or after runcmd
[09:46] <ffledgling> Is there a guaruntee on the order in which things are run by cloud-init when reading from cloud-config
[13:29] <ffledgling> Answer to my previous question seems to be - https://git.launchpad.net/cloud-init/tree/config/cloud.cfg
[14:11] <smoser> ffledgling, i'm guessing this is not ubuntu / debian ?
[14:11] <smoser> you can define proxy for apt.
[14:12] <ffledgling> smoser: nope, fedora
[14:12] <smoser> but for general system proxy there isnt.
[14:12] <smoser> proxies are a regula pita
[14:12] <smoser> generally speaking.
[14:12] <smoser> ie, setting one up "system wide" never actually works.
[14:12] <smoser> thats myexperience.
[14:13] <smoser> that said, i'm open to patches that set environment in cloud-init.
[14:13] <ffledgling> That's not entirely unexpected, some tools don't support the standard proxy variables etc and then there's the lowercase vs uppercase issue
[14:14] <ffledgling> But yeah, it'd still be nice to have the ability to set variables in the env for at least the cloud-init parts
[14:14] <ffledgling> My current work around for this usecase is to use runcmd to add a proxy via a config file, but that relies on the order in which the steps are executed by cloud-init
[14:15] <ffledgling> Which is okay I guess, but fairly fragile if the ordering is changed
[14:15] <smoser> ffledgling, probably runcmd runs after package installation
[14:15] <smoser> so i'd use a bootcmd which is guaranteed to run before package installation
[14:15] <smoser> order is not fragile really. bootcmd will run as early as it can.
[14:16] <smoser> i suspect there is some way specifically to tell yum about package config ?
[14:16] <ffledgling> smoser: I didn't actually find where the package instruction is run, but for ubuntu it seems to be in the 'final' stage?
[14:16] <smoser> er... sorry. about proxy ?
[14:16] <ffledgling> smoser: /etc/yum.conf
[14:16] <smoser> with the move to systemd, package installation started happening at 'final' stage. it used to run at 'config' stage.
[14:17] <smoser> yeah, so waht i'd do is just in a boot cmd, edit/append to that
[14:17] <smoser> bootcmd:
[14:17] <smoser>  - [sh, -c, 'echo http_proxy=http://proxy.host:port >> /etc/yum.conf']
[14:17] <ffledgling> bootcmd + cloud-init-run-once (I think that's what it's called?)
[14:17] <ffledgling> otherwise isn't bootcmd run at every boot?
[14:17] <smoser> ah, yeah. bootcmd do run every time
[14:18] <smoser> so yeah, you coul use cloud-init-per too
[14:18] <smoser> or
[14:18] <smoser> just otherwise idempotently update that file
[14:18] <ffledgling> That might be a little harder
[14:19] <smoser> well,  yeah, ini file
[14:20] <ffledgling> I was trying to figure out if there's a way to just tell cloud-init to take a file I hand it and stick it someplace on the target system
[14:20] <ffledgling> but I didn't find anything like that yet
[14:20] <smoser> well, there is write_files
[14:21] <smoser> http://cloudinit.readthedocs.io/en/latest/topics/examples.html#writing-out-arbitrary-files
[14:21] <smoser> and that runs very early
[14:21] <smoser> right after bootcmd
[14:21] <ffledgling> That might work as well
[14:22] <ffledgling> Doesn't say if it's written everytime or just once, I suspect, just one?
[14:22] <ffledgling> *once
[14:22] <smoser> that will run once per instance
[14:22] <smoser> so yeah, that'd probably work for you.
[14:23] <ffledgling> sounds good, I'll try both probably and see what works best
[14:23] <smoser> configuring yum is preferable in my opinion to configuring system wide, or relying on environment variables.
[14:23] <ffledgling> smoser: well, the problem is I really do need a system wide proxy for my eventual operations
[14:23] <smoser> well, you can write /etc/environment if you want.
[14:23] <ffledgling> Except in my case I'm using ansible to configure the VM after it's up so I can push that problem down there
[14:23] <smoser> my experience with system wide proxies is just they always end up sucking
[14:24] <smoser> for reasons largely of 'no_proxy'
[14:24] <ffledgling> Applications not respecting no_proxy or people not setting it?
[14:24] <smoser> ie, if the proxy is on the other side of the router, and it wont proxy some cidr, then globally setting http_proxy=that.proxy ends up sending all http requests to it, and it can't proxy for your network
[14:25] <smoser> most obvious example is:
[14:25] <smoser>  http_proxy=http://example.com wget http://<IP_ADDRESS>:8000/my-test-application
[14:25] <smoser> but the same general thing occurs when the proxy doesn't work for your <IP_ADDRESS>/24 or something.
[14:26] <ffledgling> right, that probably doesn't workt without no_proxy whitelisting your local network
[14:26] <smoser> and no_proxy only works very coarsely (python apps can't take a cidr, but some others doo)
[14:26] <smoser> ie, if you wantto white list <IP_ADDRESS>/24 you end up having to do:
[14:26] <smoser>  no_proxy=<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,.....<IP_ADDRESS>
[14:26] <smoser> which quickly becomes unmaintainable.
[14:27] <ffledgling> ah, right, no_proxy is "only" respects domains
[14:27] <ffledgling> s/is//
[14:27] <smoser> the only solution to such a thing that i've come accross is using a local proxy and pointing everything at that, and having its richer syntax do the selection for you.
[14:27] <smoser> ffledgling, well, no_proxy in some cases (i think wget) supports 10.0.0.*
[14:28] <smoser> but it does not in python's implementation and probably many others
[14:28] <smoser> http://bazaar.launchpad.net/~smoser/+junk/sstack-proxy/view/head:/sstack-proxy
[14:28] <smoser> that is what i've done that actually works... but comes at a cost of a middle man
[14:28] <smoser> then, you can change the config of tinyproxy and restart it, and you dont have to deal with getting the environment changed in existing processes.
[14:29] <smoser> but... that is just really neither here nor there... just sort of my experience with setting proxy and coming out hating the whole thing.
[14:29] <ffledgling> Yeah, proxies aren't really great, but i've just come to treat them as a necessary evil
[14:30] <smoser> the above is what i ended up having to do, and does work fairly well.
[14:30] <smoser> when you realize you forgot yourhost.com from the proxy config, you just add it in tinyproxy and restart tinyproxy
[14:30] <smoser> and tinyproxy config supports cidr
[14:30] <smoser> fully
[14:30] <smoser> so <IP_ADDRESS>/24 or <IP_ADDRESS>/32
[14:30] <smoser> and ipv6 and all that...
[14:31] <ffledgling> yep, I've seen the same setup recommended by a lot of people, after a certain point I'm sure it become necessary
[14:32] <ffledgling> smoser: speaking of patches (saw your comment on the bug for env var support as well), I have a doc fix that I sent in a couple of days ago
[14:34] <smoser> where did i comment on that ?
[14:34] <smoser> i've lost it now
[14:34] <smoser> did i comment?
[14:34] <smoser> https://code.launchpad.net/~ffledgling/cloud-init/+git/cloud-init-1/+merge/312917
[14:34]  * ffledgling was looking for the link to it himself, the launchpad interface is new and confusing
[14:34] <ffledgling> smoser: yeah, that one
[14:35] <smoser> ffledgling, so the link you want is https://code.launchpad.net/%7Ecloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews
[14:35] <smoser> then from there you can find things...
[14:35] <smoser> (that is the topic of this channel too)
[14:35] <smoser> also...
[14:36] <smoser> did you delete another one ?
[14:36] <smoser> you dont hve to delete a MP you can just push to it again (even push --overwrite)
[14:36] <smoser> then you dont lose the history of comments and such
[14:36] <ffledgling> I deleted the repo I think
[14:36] <ffledgling> I'd originally created  repo called ~ffledgling/cloud-init/something/cloud-init
[14:37] <ffledgling> I don't think I've deleted an MP specifically
[14:46] <smoser> did i comment ?
[14:46] <smoser> i swear i commented somehwere.
[14:47] <ffledgling> smoser: I don't see it on the MP
[14:47] <ffledgling> I didn't get an email for a comment either, I just checked
[14:48] <ffledgling> Maybe it's saved as a draft or something?
[14:48] <smoser> well, i'llj ust type again
[15:06] <ffledgling> smoser: thanks
[15:06] <ffledgling> re: the patch for env variable support, is there a particular place in the code I should start with if I wanted to implement it?
[15:21] <smoser> ffledgling, i commented there now. sorry. i thought i did that yesterday but failed i guess.
[15:23] <ffledgling> smoser: thanks, I haven't looked at upstart (don't use ubuntu much outside of experiments), I'll take a look and get back to you
[18:32] <smoser> rangerpbzzzz, around ?
[20:21] <rharper> smoser: looking to detect if the running distro supports netplan;  I'm checking 3 things  1) do we have /etc/netplan dir  2) do we have netplan binary in $PATH 3) do we have systemd-networkd .  (3) is harder as it's not in $PATH and it's not a package (it's part of systemd) possibly optional on other distros ...   thoughts on (3) ?   Also, I was thinking this was a cloudinit.net.netplan method but each distro may need t
[20:21] <rharper> o check for support differently so could be part of the distro obj
[20:25] <smoser> why not just check util.which('netplan') ?
[20:26] <smoser> netplan should depend on systemd-networkd if it needs it
[20:30] <rharper> ok
[20:33] <smoser> dont you think ?
[21:05] <rharper> smoser: I think that's reasonable


[05:49] <mup> Bug #1902822 opened: Redfish power control on Dell iDrac9 fails due to charset on the POST content-type <MAAS:New> <https://launchpad.net/bugs/1902822>
[05:52] <mup> Bug #1902822 changed: Redfish power control on Dell iDrac9 fails due to charset on the POST content-type <MAAS:New> <https://launchpad.net/bugs/1902822>
[05:55] <mup> Bug #1902822 opened: Redfish power control on Dell iDrac9 fails due to charset on the POST content-type <MAAS:New> <https://launchpad.net/bugs/1902822>
[05:58] <mup> Bug #1902822 changed: Redfish power control on Dell iDrac9 fails due to charset on the POST content-type <MAAS:New> <https://launchpad.net/bugs/1902822>
[06:01] <mup> Bug #1902822 opened: Redfish power control on Dell iDrac9 fails due to charset on the POST content-type <MAAS:New> <https://launchpad.net/bugs/1902822>
[11:56] <mup> Bug #1902867 opened: config.list websocket call results in: '<' not supported between instances of 'NoneType' and 'str' <MAAS:Triaged> <https://launchpad.net/bugs/1902867>
[11:59] <mup> Bug #1902867 changed: config.list websocket call results in: '<' not supported between instances of 'NoneType' and 'str' <MAAS:Triaged> <https://launchpad.net/bugs/1902867>
[12:02] <mup> Bug #1902867 opened: config.list websocket call results in: '<' not supported between instances of 'NoneType' and 'str' <MAAS:Triaged> <https://launchpad.net/bugs/1902867>
[16:12] <johnny101> In a snap maas install (2.8), should the /var/snap/maas/current/preseeds directly come populated with more than just *.sample files?  (Still trying to figure out why cloud init fails on enlistment with no data source found)
[16:32] <mup> Bug #1899023 changed: add support to encrypt swap partition <MAAS:Invalid> <https://launchpad.net/bugs/1899023>