=== mamarley is now known as Guest27279
=== mamarley_ is now known as mamarley
=== amitk_ is now known as amitk
[12:42] <rbasak> Could someone please take a look at my comments in bug 1648143? I tried to verify the fix, but found that it's fixed in Xenial (but seems to have been released before verification), still broken in Yakkety (but already released before verification) and still broken in Zesty. Not sure how to triage it.
[12:42] <ubot5> bug 1648143 in linux (Ubuntu Yakkety) "tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_<var-lib-lxd>" profile="unconfined" name="system_tor"" [Undecided,Confirmed] https://launchpad.net/bugs/1648143
[12:47] <rtg> jjohansen, ^^
[16:28] <hallyn> where does one sign up for livepatch?
[16:43] <mdeslaur> hallyn: https://www.ubuntu.com/server/livepatch
[16:54] <hallyn> thx!
[16:54] <hallyn> oh noes - i need snap? :)
[16:56] <hallyn> oh-double-noes - and snap requires systemd?
[16:56] <hallyn> ok good enough for my server, not my laptop.  i can live with that - thx :)
[18:24] <jjohansen> rtg: thanks, I'll take a look at it
[18:30] <shubjero> Hi all. I was updating a bunch of servers kernel's for Ubuntu Trusty and noticed that a slew of them received 3.13.0-111, but the rest received 3.13.0-110. Did someone push -111 to the repository before it was supposed to be pushed?
[18:31] <shubjero> I now have about 100 servers running -111
[18:31] <shubjero> and 25 running -110
[18:53] <rtg> infinity, apw ^^
[18:55] <infinity> shubjero: Yeah, -111 was accidentally released and reverted.  It should be mostly harmless.  Hopefully.  But if you're paranoid, rebooting those into -110 would not be a crazy option.
[18:56] <infinity> -111 (or possibly a -112) will release properly in a week or so.
[18:58] <infinity> shubjero: Anyhow, if they're happy on -111, I wouldn't worry about it.  We accidentally released if before our testing was done, but there aren't any known issues with it either.
[19:00] <shubjero> thanks for your feedback infinity 
[19:00] <shubjero> we're a research organization so running 111 isnt a big deal. if we have issues we can do an emergency maintenance to install -110
[19:23] <apw> shubjero, we'd be interested in knowing if you have to revert and why
[19:25] <shubjero> apw: yeah if i have any issues ill be sure to come visit here and let everyone know
[19:25] <shubjero> or i may throw a post on the ubuntu mailing list
[19:25] <shubjero> either way 
[19:25] <shubjero> im sure we'll be fine
[20:19] <hallyn> has anyone here followed the bus1 progress?  It seems to be an out of tree module now - is it slated to go upstream at some point?
=== JanC_ is now known as JanC
[22:23] <stgraber> FYI we're getting panics every few minutes on our Jenkins test runners ever since we upgraded to the latest 16.04 kernel (4.4.0-65)
[22:23] <stgraber> trying to get those systems setup in a way that we can actually see said panic rather than just have them drop from the network and not print anything...
[23:24] <stgraber> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669611 filed as critical SRU regression with traces from 4 different systems
[23:24] <ubot5> Ubuntu bug 1669611 in linux (Ubuntu) "Regression in 4.4.0-65-generic causes very frequent system crashes" [Critical,Triaged]
[23:33] <stgraber> bjf: ^
[23:35] <bjf> jsalisbury, ^ can you jump on that
[23:36] <stgraber> I'm moving all those test runners to the zesty 4.10 now, we'll see if it's affected too or not
[23:44] <bjf> jjohansen, you might take a look at ^ there are a bunch of __aa_fs_* symbols in the call trace (in case that's apparmor)
[23:44] <stgraber> yeah, I pinged him in #security when I saw the aa stuff in there
[23:59] <jsalisbury> bjf, ack