[00:11] <mup> Bug #1661445 opened: Asked MAAS for a windows machine, but that failed due to missing drivers in windows <oil> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1661445>
[03:22] <shahaan> Hello, since upgrading to 2.1.3+bzr5573-0ubuntu1~16.04.1 500, GPT partitioning is causing MBR corruption leading to grub-rescue prompt upon booting, any ideas ??
[04:27] <roaksoax> shahaan: did you upgrade curtin too ?
[04:27] <roaksoax> shahaan: maas has not made any changes to GPT in 2.1.3 or to storage, but maybe curtin has which is breaking
[11:12] <thiagolib> Hi does anyone know where I can find a guide to deploy ubuntu cloud 16.04.
[11:31] <mup> Bug #1661579 opened: Adding devices from discovery listing is opaque <MAAS:New> <https://launchpad.net/bugs/1661579>
[12:01] <mup> Bug #1661581 opened: "Parent" should be demoted in "Add device from discovery" form <MAAS:New> <https://launchpad.net/bugs/1661581>
[12:01] <mup> Bug #1661583 opened: Importing HTML documentation into the codebase <MAAS:New> <https://launchpad.net/bugs/1661583>
[12:55] <mup> Bug #1661591 opened: [UX] Remove filter feedback from search bar in machine listing <MAAS:New> <https://launchpad.net/bugs/1661591>
[14:34] <mup> Bug #1655176 changed: [2.1.2]  Power state could not be queried: Could not connect to BMC.  Check BMC configuration and try again. <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1655176>
[14:34] <mup> Bug #1655981 changed: removing rack controller from region controller doesn't remove it from maas db <4010> <MAAS:Triaged> <https://launchpad.net/bugs/1655981>
[15:04] <roaksoax> /quer/win 4
[15:10] <mup> Bug #1660179 changed: [2.1.2] A number of servers fails Deployment following PXE local boot at around same time <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1660179>
[15:22] <mup> Bug #1660179 opened: [2.1.2] A number of servers fails Deployment following PXE local boot at around same time <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1660179>
[15:22] <mup> Bug #1661203 opened: [2.1+] Cannot create a bridge on an interface that also has VLAN interfaces <curtin:Invalid> <MAAS:Triaged> <https://launchpad.net/bugs/1661203>
[15:53] <mup> Bug #1652301 changed: [Device Discovery] In the device listing the chevron intended to open the row is not discoverable <MAAS:Confirmed> <https://launchpad.net/bugs/1652301>
[15:53] <mup> Bug #1661445 changed: Asked MAAS for a windows machine, but that failed due to missing drivers in windows <oil> <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1661445>
[16:23] <mup> Bug #1661662 opened: ImportError: cannot import name 'Origin' with Django 1.10 <django1.10> <MAAS:New> <https://launchpad.net/bugs/1661662>
[16:53] <mup> Bug #1661672 opened: [2.1] When you can't access rescue mode, it doesn't show message why <MAAS:New> <https://launchpad.net/bugs/1661672>
[19:27] <mimizone> hi all.
[19:29] <mimizone> how can I modify the enlisting image to add a file in /etc/modprobe.d/ . I need a specific config so the reboot works properly on my hardware. Same question for adding this file in the ubuntu installation.
[19:47] <kiko> mimizone, what is the module, incidentally?
[19:48] <kiko> mimizone, I don't know if you can specify preseeds for the ephemeral impact -- roaksoax?
[19:48] <mimizone> mei-me.conf
[19:48] <kiko> aha
[19:48] <mimizone> I need this 'options mei-me disable_msi=1'
[19:48] <kiko> mimizone, what hardware is this?
[19:48] <mimizone> for the Open Compute old hardware we have
[19:49] <kiko> mimizone, interesting, I have the same hack on a pair of supermicro avoton nodes I have; MAAS hangs when booting them otherwise
[19:50] <kiko> but IIRC I just hacked the ephemeral image
[19:50] <kiko> which isn't the right way to handle this
[19:51] <mimizone> where is that image?
[19:51] <mimizone> I would be ok just adding a file inthere...
[19:52] <kiko> dig around /var/lib/maas/, I would assume images and then the current directory under it, but my rack is offline
[19:53] <mimizone> I am right in there now
[20:02] <mimizone> I am running MAAS 2.1.3 if it matters
[20:03] <kiko> it shouldn't
[20:03] <kiko> mpontillo, ltrager: are either of you around to see what mimizone has to say?
[20:05] <kiko> mimizone, https://maas.ubuntu.com/docs/troubleshooting.html
[20:06] <mimizone> kiko: I see the section on the ephemeral image, thanks
[20:06] <kiko> mimizone, also, see the backdoor FAQ here https://maas.ubuntu.com/docs/troubleshooting.html
[20:06] <kiko> err
[20:06] <kiko> here: https://docs.ubuntu.com/maas/2.1/en/troubleshoot-faq
[20:06] <kiko> you should be able to crib from that
[20:06] <kiko> sorry, Friday afternoons are a bit slow here
[20:07] <mimizone> kiko: I'll look into it. Thanks again.
[20:08] <kiko> sure thing -- I'm out for a bit but just write and I'll see it when I'm back
[20:17] <ltrager> mimizone, kiko: You should be able to create a tag which will add the option to the kernel parameters list - http://maas.ubuntu.com/docs/api.html#tag
[20:19] <mimizone> can all nodes in a zone be automatically tagged?
[21:10] <roaksoax> mimizone: you can add global kernel parameters, or you can add per node kernel parameters as above
[21:13] <mimizone> roaksoax: thanks.