[06:21] <mpontillo> ccit-spence: it should be fine to do that; MAAS supports VMware for power management. if you will be creating virtual bridges on VMware hosts, (like to create containers, etc) just be aware that there can be issues with the way VMware virtual switches optimize traffic sent to VMs
[07:15] <mup> Bug #1596428 opened: [2.0b8] VLAN listed with unconfigured subnet and wrong DHCP address after deployment <MAAS:New> <https://launchpad.net/bugs/1596428>
[08:54] <mup> Bug #1596452 opened: [2.0b8] Node with IPv6-only second public VLAN fails deployment <MAAS:New> <https://launchpad.net/bugs/1596452>
[09:06] <mup> Bug #1596452 changed: [2.0b8] Node with IPv6-only second public VLAN fails deployment <MAAS:New> <https://launchpad.net/bugs/1596452>
[09:12] <mup> Bug #1596452 opened: [2.0b8] Node with IPv6-only second public VLAN fails deployment <MAAS:New> <https://launchpad.net/bugs/1596452>
[10:31] <mup> Bug #1596483 opened: [2.0b8] Support for IPv6 autoconfigured IP addresses , and avoid confusion with "auto" label <MAAS:New> <https://launchpad.net/bugs/1596483>
[12:40] <mup> Bug #1596522 opened: [2.0] Using two networks w. default route requires network metric <MAAS:New> <https://launchpad.net/bugs/1596522>
[13:38] <f1gjam> hey guys, I have a very weird problem. I have two nodes which I can deploy to via MaaS and two nodes which i cant. The two nodes which work are the HP ML110 G6 servers and the two nodes I cannot deploy to are Lenovo TS140
[13:38] <f1gjam> the error I get is: https://screencloud.net/v/C1lI
[15:50] <blake_r_> f1gjam: what version of MAAS are you using?
[15:55] <f1gjam> blake_r_, 1.9
[15:55] <f1gjam> i tried both ubuntu 14.04 and 16.04 images
[16:02] <blake_r_> f1gjam: try recommissioning the machine first then deploying
[16:02] <blake_r_> f1gjam: only one disk should be installed to the other disks should have the superblock wiped that way it does not try to boot to it
[16:20] <f1gjam> hmm
[16:20] <f1gjam> if i remcommission
[16:21] <f1gjam> can i format both disks?
[16:50] <kiko> f1gjam, you can always format two disks, as long as MAAS knows about the disks
[16:51] <f1gjam> well
[16:51] <f1gjam> im gona try again in a sec
[16:57] <f1gjam> so it just seems to sit here during deployment
[16:57] <f1gjam> https://screencloud.net/v/n1X6
[16:58] <roaksoax> f1gjam: did you look at /var/log/maas/rsyslog/<hostname> or did you look at the node event log to see whta's going on?
[16:59] <f1gjam> is always empty
[16:59] <f1gjam> on 1.9
[17:00] <roaksoax> ah, yeah 2.0 is the one that adds rsyslog
[17:00] <roaksoax> f1gjam: what about node event log ? the node event log will tell you what's going on
[17:00] <f1gjam> where is the node event log
[17:01] <roaksoax> f1gjam: if you are using the CLI, you can see the "events" endpoing
[17:02] <f1gjam> i was using the gui
[17:02] <roaksoax> f1gjam: if you are using the UI, you can see it in the Machine details page (the one you are trying to deploy)
[17:02] <f1gjam> https://screencloud.net/v/tdX5
[17:02] <roaksoax> f1gjam: you are tring to access a metadata server for curtin
[17:03] <roaksoax> f1gjam: you can access the UI: http://<ip>/MAAS
[17:03] <roaksoax> f1gjam: click on the machine you are trying to deploy
[17:03] <roaksoax> f1gjam: you will find the node event lo there
[17:03] <f1gjam> https://screencloud.net/v/mgeT
[17:04] <f1gjam> https://screencloud.net/v/wcO2
[17:05] <f1gjam> i can logon to the machine
[17:05] <f1gjam> thats being provisioned
[17:05] <f1gjam> is there anything i can get from there>
[17:07] <f1gjam> check this: http://paste.ubuntu.com/17980452/
[17:07] <f1gjam> i got this from the provisioned node cloud-init-output.log
[17:07] <f1gjam> MaaS still thinks the node is deploying
[18:22] <f1gjam> still no luck
[18:22] <f1gjam> i installed ubuntu on the machine and tried that but i still cant get this to work
[18:24] <kiko> f1gjam, does ubuntu installed on the machine work?
[18:24] <f1gjam> yes
[18:24] <f1gjam> it booted
[18:25] <f1gjam> then i tried maas again
[18:25] <f1gjam> same issue
[18:25] <f1gjam> pxe to localboot fails
[18:26] <kiko> f1gjam, I don't think it's clear what your problem is
[18:27] <f1gjam> https://screencloud.net/v/C1lI
[18:27] <f1gjam> this is the problem i am facing
[18:30] <kiko> f1gjam, is this after installation?
[18:30] <kiko> which boot is that
[18:33] <f1gjam> thats after the initial OS deploy is done by MaaS
[18:33] <f1gjam> and it reboots the system
[18:33] <f1gjam> this happens
[18:34] <f1gjam> if you want i can do a google hangout or something and you can see this live???
[18:34] <f1gjam> brb 5 mins
[18:37] <f1gjam> ok back
[18:50] <f1gjam> kiko, are you about?
[18:51] <kiko> f1gjam, I'm otp so very slow
[18:52] <kiko> f1gjam, UEFI or legacy boot?
[19:13] <f1gjam> i have enabled legacy boot
[19:13] <f1gjam> should i change it uefi?
[19:30] <f1gjam> enabled UEFI
[19:30] <f1gjam> initial install completed, machine rebooting
[19:30] <f1gjam> moment of truth
[19:31] <f1gjam> nope same problem
[19:32] <f1gjam> help
[19:32] <f1gjam> woops
[19:34] <f1gjam> ]ok so i think i figured it out
[19:34] <f1gjam> i just did a boot slection and chose the correct disk my self and it booted, and MaaS said deployed
[19:35] <f1gjam> so its basically choosing the wrong disk to boot off
[19:38] <kiko> ah
[19:38] <kiko> very interesting
[19:38] <kiko> f1gjam, do all the machines you have present the same behaviour?
[19:41] <f1gjam> no only the Lenovo machines
[19:41] <f1gjam> doing another deploy to confirm
[19:41] <f1gjam> if its true
[19:41] <f1gjam> its the silliest bios option ever
[19:41] <kiko> what is the bios option?
[19:41] <f1gjam> there is an option to choose USB key
[19:42] <f1gjam> vs USB HDD - Sandisk
[19:42] <kiko> oh m
[19:42] <f1gjam> so i chose the USB - San disk
[19:42] <f1gjam> well usb key didnt wor
[19:42] <f1gjam> now let me try
[19:42] <mup> Bug #1596683 opened: node network settings revert after failed bootstrap <MAAS:New> <https://launchpad.net/bugs/1596683>
[19:44] <f1gjam> im guessing the device name is incorrect
[19:44] <f1gjam> for the pxe?
[19:44] <f1gjam> or someting
[19:54] <kiko> f1gjam, I think I lost you in the last part of the chat
[19:55] <f1gjam> baically
[19:55] <f1gjam> basically
[19:55] <f1gjam> i thought the boot option was screwed up
[19:55] <f1gjam> but its not that, I tried UEFI, but I selected UEFI first then legacy, now i have forced it to just boot in UEFI mode and I am trying again
[19:56] <f1gjam> my thought is that during the insall everything goes well, but when PXE is configured for the local disk boot it messes up which disk to boot off
[19:56] <f1gjam> UEFI MaaS boot happening now
[20:08] <f1gjam> IT WORKED!!!
[20:08] <f1gjam> no wait
[20:08] <f1gjam> lol
[20:08] <f1gjam> it was commssioning :)
[20:21] <f1gjam> ok looks like it did work
[20:21] <f1gjam> :)
[20:21] <f1gjam> kiko, so Lenovo TS140 has to be in UEFI mode
[20:26] <kiko> f1gjam, interesting. the x240 blades can't. :-)
[20:33] <f1gjam> wel the blades would be old bios right?
[20:33] <f1gjam> im testing the second server now
[20:34] <f1gjam> btw this is my home lab
[20:34] <f1gjam> so i can test most scenarios without anyy issues
[20:34] <kiko> f1gjam, neat
[20:35] <kiko> f1gjam, the very latest blade BIOS (which Lenovo provides) still fails with us on UEFI
[20:36] <kiko> f1gjam, happy it works for you though 8)
[20:37] <kiko> f1gjam, could you file a bug describing how legacy boot mode fails and the failure mode, perhaps attaching the screenshots?
[20:40] <nturner> I have a raw disk image that I've prepared for creating amazon machine images (AMI). This works. Is it reasonable for me to think that I can take this raw disk image and turn it into a custom MAAS image? I've read the docs, and it's not clear.
[20:41] <kiko> nturner, hah, that's a really good question.
[20:42] <kiko> smoser, blake_r_: do either of you know the answer to nturner's question?
[20:42] <kiko> we get so many custom images questions
[20:49] <f1gjam> kiko, will do but letme confirm first it is 100% working
[20:49] <kiko> yeah
[21:59] <f1gjam> kiko, https://bugs.launchpad.net/maas/+bug/1596719
[21:59] <kiko> thanks f1gjam
[22:00] <kiko> f1gjam, it has to do with how we tell the firmware to select drive 1 I think
[22:00] <f1gjam> np
[22:00] <f1gjam> no once you do UEFI
[22:00] <f1gjam> you have to recommisson
[22:00] <f1gjam> which is what I am trying now
[22:00] <f1gjam> to confirm
[22:00] <f1gjam> machine two works all the time now
[22:00] <f1gjam> machione one didnt work after the  changes
[22:00] <f1gjam> but ididnt recommission
[22:00] <f1gjam> so trying now
[22:01] <f1gjam> im doing all this and i know landscape will break !! :'(
[22:10] <f1gjam> confirmed works now
[22:15] <mup> Bug #1596719 opened: Lenovo TS140 Server UEFI only supported by MaaS <MAAS:New> <https://launchpad.net/bugs/1596719>
[22:17] <pacavaca_> When using custom image MAAS says it can't configure network, network config only supported for Ubuntu. Which is fair, but is there any way to let MAAS think my custom image is actually an ubuntu image? Because it actually is an ubuntu + few extra packages and configs.
[22:18] <mup> Bug #1596719 changed: Lenovo TS140 Server UEFI only supported by MaaS <MAAS:New> <https://launchpad.net/bugs/1596719>
[22:22] <mup> Bug #1596719 opened: Lenovo TS140 Server UEFI only supported by MaaS <MAAS:New> <https://launchpad.net/bugs/1596719>
[22:31] <kiko> f1gjam, shouldn't break, I have a few users running landscape happilly
[22:32] <kiko> pacavaca_, I do believe there is a way, look up curtinator to see if they do anything special?
[22:33] <pacavaca_> kiko: Curtinator doesn't do anything special, it just installs cloud-init. But curtinator-created images are recognized as custom by MAAS.
[22:39] <f1gjam> kiko,  it broke yesterday so we shall see, but at that point i didnt know about this issue :)
[22:52] <roaksoax> pacavaca_: in 2.0+ we "pass" the curtin config that has the network configuration
[22:52] <roaksoax> pacavaca_: so it would be up to you to understand that and translate that into the image
[22:52] <roaksoax> pacavaca_: or you could always contribute to maas that code :)
[23:00] <f1gjam> kiko, looks like landscape may actually work :D
[23:00] <f1gjam> woooot
[23:01] <f1gjam> will today be the day i can install autopilot and openstack!!!
[23:06] <f1gjam> oh wait
[23:06] <f1gjam> i think i just screwed my network design :(
[23:06] <f1gjam> so landscape worked :D
[23:13] <f1gjam> There must be at least one machine, available in the MAAS cluster, that has two or more network interfaces connected to the networks that are defined in MAAS.
[23:35] <LoRez> 
[23:35] <LoRez> sm