=== mwhudson is now known as Guest60520
=== Guest60520 is now known as mwhudson_
=== mwhudson is now known as Guest18633
=== Guest18633 is now known as mwhudson_
=== mwhudson is now known as Guest42456
=== Guest42456 is now known as mwhudson_
=== frankban|afk is now known as frankban
[09:20] <cnf> anyone seen maas trying to install BIOD grub on UEFI machines?
[09:20] <cnf> my hp gen9's won't boot because of it
[11:55] <cnf> jamespage: I think i am running in to https://bugs.launchpad.net/maas/+bug/1732980
[11:55] <cnf> FYI
[13:00] <roaksoax> cnf: that's fixed on 2.3.2
[13:01] <roaksoax> cnf: well , you have now the option to force what boot method to use in the power settings
[13:56] <cnf> roaksoax: i ru n 2.3.2
[13:56] <cnf> roaksoax: aha, let me see if i can find that option
[13:57] <cnf> roaksoax: ah, ok... and that "fixes" that bug?
[13:59] <roaksoax> cnf: go to the machine details page, go the configuration tag, and select the BIOS boot method
[14:00] <cnf> yeah, i just found it
[14:01] <cnf> roaksoax: we just downgraded the ilo firmware on the urgent machines, but i'll try that on a spare tomorrow, thanks!
[14:44] <roaksoax> cnf: gotcha
[16:20] <xygnal>  when I change the boot disk, do i have to recommision to apply that? i noticed if i simply change it in the UI it still shows the old/wrong disk as root
=== frankban is now known as frankban|afk
[17:02] <kzach> Hi all. I'm looking into using Maas for image deployment, but would like to make sure it will satisfy the requirements I've been given. The main thing is that I need to be able to create images of machines (most RHEL and a little Windows) after everything has been installed on them. Does Maas provide that capability, or do I look for other software to do it
[17:08] <ananke> kzach: I think you can create your own images, but I haven't gotten that far in my research process
[17:08] <roaksoax> kzach: maas can deploy windows/rhel. You would have to talk to Canonical to get the ability to do that in a supported way
[20:46] <Hey> roaksoax: is there a way to add more kernel types as even on older hardware, I can't detect the storage.
[20:46] <Hey> This is also the case for hyper-v vm's
[20:58] <roaksoax> Hey: it could be a thing with hyper-v vm's. We discover attached storage with lsblock
[21:03] <Hey> roaksoax: I'm trying to image asus x99-ws ipmi motherboard with samsung ssd. It detects everything other than Storage.  Could bios setting affect this?
[21:05] <roaksoax> unlikely, but could be... iit could be a driver issues too
[21:06] <Hey> I'm not sure what kernel to use
[21:29] <Hey> roaksoax: wow.. that was an ordeal
[21:29] <Hey> Finally found the hard drive.. I'm imaging now..
[21:37] <Hey> roaksoax: I used 17.10 then did hardware test.
[21:40] <roaksoax> Hey: hold on, so you used another kernel and it did work now ?
[21:41] <Hey> I'm not sure if it was the kernel.. or me doing the hardware test
[21:41] <Hey> I will try it again and confirm and get back to you.
[21:42] <Hey> basically.. I comission.. everything shows with exception of hard drive.  Then did hardware test
[21:42] <Hey> hardware test failed.. but It detected the size of the HD
[21:42] <Hey> and showed a mount point
[21:44] <Hey> I'm also imaging windows 10
[21:44] <Hey> I'll see how it goes.
[23:26] <lilac> hi :)
[23:26] <lilac> does anyone know why attempting to add a VMWare ESXi server as a chassis with the VMWare power type doesn't seem to do anything?
[23:26] <lilac> adding individual machines with teh vmware power type doesn't work either
[23:26] <lilac> yet individual machines can be added using virsh to connect to esxi
[23:27] <lilac> but i can't do the same with it as a chassis (doesn't detect any machines)