Unblocking cert on this since we can now deploy using HWE-V or later via
MAAS
** Tags removed: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
maas
** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
maas uses 3.13 (hwe-t) kernel which does not work on
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM
Will this be fixed in the 1.9 release?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM
power
To
** Changed in: maas-images
Status: New => Confirmed
** Changed in: maas-images
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1508565
My suggested plan forward would be:
a.) promote the 14.04:ppc64el:hwe-v to released for ppc64el
I will need someone to test that and suggest its reasonable
That can be done by using the daily stream and doing an install to a
system marked as 'generic/hwe-v'
b.) remove
> Can a MaaS customer still get the hwe-t kernel through manual steps if
desired?
they could apt-get install it after the fact (same as for option 'b').
> What are consequences to support on hwe-u? Are they know forced up to
16.04 sooner (since hwe-u does not have lifetime of hwe-t)?
Well, no.
WRT option c (lie about LTS kernel):
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1508565/comments/3
Can a MaaS customer still get the hwe-t kernel through manual steps if
desired?
What are consequences to support on hwe-u? Are they know forced up to
16.04 sooner (since hwe-u does not
