=== shoutme is now known as hallyn
=== psivaa_ is now known as psivaa
=== daxcat is now known as dax
=== tsimonq2alt is now known as tsimonq2-
=== tsimonq2- is now known as tsimonq2
=== tjaalton_ is now known as tjaalton
[10:29] <rbasak> apw: around? We're testing some upgrade paths for MySQL from Trusty to Xenial, and may be impacted by the "from" kernel version because I don't think the original Trusty kernel supports Apparmor on Unix sockets.
[10:29] <rbasak> apw: we'll test this path, but we also want to test the Precise->Trusty->Xenial path.
[10:29] <rbasak> apw: so the question is: do you know the set of kernels users can end up with on upgrading from Precise to Trusty?
[10:29] <apw> rbasak, that sounds about fair analysis of the trusty -release kernel
[10:30] <rbasak> apw: will they always end up with the Trusty non-HWE kernel, or is there a case where a user upgrading from Precise could end up with an HWE Trusty kernel?
[10:31] <apw> rbasak, in theory all hwe kernels upgrade to the release kernel in the following LTS if we have done our meta-packages right
[10:32] <rbasak> That's great. We'll check to be sure, but hopefully this will help reduce our test matrix, because then our Precise->Trusty->Xenial test will cover the Trusty -release kernel to Xenial case too.
[10:32] <rbasak> Thanks!
[10:32] <apw> rbasak, and yes during upgrade you run the old kernel the entire time, until the upgrade completes, so you do expect some issues until you reboot
[10:37] <rbasak> Got it. Thanks!
[10:38] <apw> i wonder if we support upgrading P->T->X without a reboot at T
[10:38] <apw> i'd really hope not
[10:45] <rbasak> I expect not. I'm not worried about that case.
[10:46] <rbasak> Our reason for testing P->T->X is really the state in /var/lib/mysql etc.
[10:47] <rbasak> But it also nicely covers the T -release kernel -> X case so we don't need to independently test that in theory.
[10:47] <rbasak> Given that we're testing P->T->(reboot)->X
[10:47] <rbasak> P->T->(reboot)->X->(reboot) I suppose.
[10:57] <Skuggen> I'll do the upgrade from Precise to Trusty then, and verify that it has 3.13
[10:57] <Skuggen> Thanks :)
[10:58] <apw> of course that ship has sailed if we got it wrong
[11:37] <Skuggen> It does say a restart is required, at least, after going from Precise to Trusty :)
[11:38] <Skuggen> And now I'm on 14.04.4 with kernel 3.13.0
=== phil42 is now known as phil43
=== phil43 is now known as phil42
=== yofel_ is now known as yofel
[13:07] <caribou> Will any other release receive the 4.4+ kernels other than Xenial ? The crash tool fails to load these so I'm fixing it
[13:09] <rtg> caribou, the last 14.04 point release (14.04.5 ?) will have the Xenial kernel.
[13:09] <caribou> rtg: ok, I'll SRU the fix to Trusty as well
=== ghostcube_ is now known as ghostcube
=== JanC_ is now known as JanC
=== adrian is now known as adrian|sick