meenasomebody please unstale this: https://github.com/canonical/cloud-init/pull/200300:33
-ubottu:#cloud-init- Pull 2003 in canonical/cloud-init "move get_ib_* functions to cloudinit.distros.networking" [Open]00:33
holmanbI gotchu meena03:37
holmanbmeena: re bug 269767: for the title might want to strike mention of LXC and mention instead that lxd is using qemu as the emulator03:43
-ubottu:#cloud-init- Bug 269767 in usb-creator (Ubuntu) "Depends: syslinux" [Undecided, Fix Released] https://launchpad.net/bugs/26976703:43
holmanbbad ubottu03:43
holmanbI was refering to the freebsd bug, not whatever ubottu dragged up03:55
cpaelzerholmanb: hehe, bug numbers are techs "They-Who-Must-Not-Be-Named" :-P06:11
meenaholmanb: I got six other FreeBSD VMs running just fine under qemu on that machine07:07
meenaholmanb: https://github.com/freebsd/freebsd-src/pull/664 i got a weak start on a fix, but had no time for testing yet12:32
-ubottu:#cloud-init- Pull 664 in freebsd/freebsd-src "apic: prevent divide by zero in CPU frequency init" [Open]12:32
anankehah. I spent couple hours beating my head agains the wall trying to figure out why a certain program would run just fine from cron or directly, but it would just exit without a single error when executed from a per-boot script13:30
anankecome to find out, it expected HOME env variable to exist13:30
meenaananke: I think somebody in here is working on a cc_env module14:21
-ubottu:#cloud-init- Pull 1965 in canonical/cloud-init "add proxy support for ansible galaxy" [Open]14:23
anankeohh, that plugin would be nice, since all of our systems are behind proxies, and configuring it everywhere is a bane of my existance14:28
anankefor this particular issue I'm just going to set HOME locally in the script, but it was such a pain to figure out what was going on. I was saving strace log files trying to find out why it would just exit14:29
anankeit was xfreerdp client btw14:30
anankeon the subject of environment variables, they can be such a pain. For example, we've found out that that various distros have limit on the length of variables that pam_env will accept from /etc/environment14:33
anankefor some distros it was 1024 bytes, for some it was 25614:33
anankewe found out, because our NO_PROXY is about 1050 bytes14:33
meenaananke: oooooooooof.15:09
meenaso what happened? did it truncate? or reject?15:09
anankemeena: it truncates it. 15:30
anankeI forget which ones truncate to what length, but both debian and ubuntu are affected. 15:31
anankeit was disappointing to see that, to say the least. we had to pivot from being able to rely on /etc/environment to having additional script in /etc/profile.d/15:35
waldii would say, everyone chooses their own problems. maybe reducing the size of NO_PROXY by using wildcards would be a good idea. but what do i know15:42
anankewaldi: NO_PROXY doesn't support wildcards15:56
anankethe whole proxy setup via env variables is a huge mess in the linux world. different rules govern no_proxy than http/s/ftp/all_proxy15:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!