[00:10] <v1k0d3n> so the error initially is about bootif: siocgifindex: no such device.
[00:10] <v1k0d3n> wondering if this could have anything to do with running M.2 drives?
[10:42] <mup> Bug #1611711 opened: [API] block-device 'add/remove_tag' operations use GET method, not POST <MAAS:Triaged> <https://launchpad.net/bugs/1611711>
[11:24] <mup> Bug #1611726 opened: Documentation for machine create API doesn't say that power_type is required <MAAS:New> <https://launchpad.net/bugs/1611726>
[13:03] <mup> Bug #1340920 changed: Extra slash in /etc/apt/sources.list; prevents connecting to some servers <papercut> <trivial> <MAAS:Triaged> <https://launchpad.net/bugs/1340920>
[13:33] <mup> Bug #1611761 opened: [2.0 RC3 ] Unhandled Error - maasserver.models.regioncontrollerprocess.DoesNotExist <oil> <oil-2.0> <MAAS:New> <https://launchpad.net/bugs/1611761>
[13:45] <newmember> I am using MAAS with auto pilot and it only auto detects one node out of 12.  Is there a place to look to help mass find all the nodes?
[13:46] <newmember> Or get maas to re-try auto discovery?
[13:47] <roaksoax> newmember: what do you mean by auto-discovery ?
[13:48] <newmember> when installing maas it appears to look at the network for nodes, it found one.
[13:48] <newmember> i see all the nodes picked up an IP address form maas
[13:49] <newmember> from maas
[13:54] <roaksoax> newmember: maas doesn;t look at the network for nodes
[13:54] <roaksoax> newmember: if a machine that maas knows nothing about, DHCP's from MAAS
[13:54] <roaksoax> we will know that /something/ has DHCP'd
[13:55] <roaksoax> newmember: but typically, MAAS "auto" discovers machines when machines DHCP from MAAS *and* PXE boot from MAAS
[13:58] <kiko> newmember, you basically need to PXE boot all your 12 nodes against MAAS
[15:53] <junaidali> Hi everyone, what is the default password that MAAS sets for a node? preseeds master file doesn't specify any password
[15:54] <junaidali> is there a way that we can use for setting up password for the nodes that we deploy?
[17:07] <kiko> junaidali, there's no default password -- use the registered ssh key to log in
[17:07] <kiko> junaidali, the default user on ubuntu is called ubuntu, and on centos is centos
[17:08] <junaidali> thanks. Is there any setting to set the password for every node that we're provisioning?
[17:10] <junaidali> password for ubuntu user*
[17:21] <kiko> junaidali, no, you'll need to do that through a curtin hook. I don't know if I think that's a sane thing to do though
[17:41] <junaidali> Thanks kiko
[17:42] <nturner> If I want to add CentOS images to my MAAS setup, is that possible?
[17:42] <nturner> The docs seem to imply that it is, but don't describe how.
[17:44] <junaidali> in MAAS 2.0, it is pretty easy. which version of MAAS are you using?
[17:45] <nturner> junaidali: I'm using 2.0.0~rc3+bzr5180-0ubuntu2~16.04.1
[17:47]  * nturner sees 2.0.0~rc4+bzr5187-0ubuntu1~xenial1 is now available and updates...
[17:49] <blake_r> nturner: centos images are in the images page, you can just import them
[17:51] <nturner> hmmm
[17:54] <nturner> here's what I see on that page: https://snag.gy/XounFl.jpg
[17:56] <nturner> Am I tracking the wrong thing? Under Settings my Boot images Sync URL is https://images.maas.io/ephemeral-v2/releases/
[17:56] <nturner> Which is whatever MAAS defaulted to. Maybe the default has changed for new installs but upgrades don't change it?
[17:57] <nturner> blake_r: What Sync URL are you using?
[17:57] <kiko> nturner, can you change releases to daily?
[17:57] <nturner> sure...
[17:58] <nturner> well, golly, that was easy!
[17:58] <nturner> Thanks all.
[18:39] <newmember> thanks kilo
[18:39] <newmember> I am using the autopilot deployment from Ubuntu
[18:39] <newmember> I installed MAAS
[18:39] <newmember> I created 12 nodes
[18:40] <newmember> When I look on MAAS all I see is the one node created in MAAS none of the other nodes are created in MAAS
[18:40] <newmember> I would have thought that they all auto create in MAAS
[18:40] <newmember> they are all getting DHCP from MAAS
[18:41] <newmember> Maybe autopilot uses the vmware api to get the 'node' names and load them in MAAS, maybe its not a DHCP discovery thing
[19:16] <kiko> newmember, you don't need to create the nodes manually
[19:16] <kiko> newmember, and in fact, I argue you shouldn't
[19:18] <newmember> kiko, okay
[19:25] <kiko> newmember, instead, just PXE-boot the machines and see them appear
[19:27] <kiko> newmember, if they don't appear, you have a problem that needs fixing
[19:28] <newmember> kiko, I think I have a problem that needs fixing :)
[19:29] <kiko> newmember, do the machines PXE boot successfully?
[19:31] <newmember> gets an ip address
[19:31] <newmember> booting under maas
[19:31] <newmember> some long line of stuff
[19:31] <newmember> then stops at "boot:"
[19:32] <newmember> there is a note:  could not find kernel image
[19:36] <kiko> newmember, could you get us a screenshot?
[19:41] <newmember> kiko, great idea
[19:41] <newmember> http://picpaste.com/Capture-50dZaauj.PNG
[19:42] <kiko> newmember, yeah, that's definitely odd. what releases do you have selected in your images page?
[19:43] <newmember> checking
[19:43] <roaksoax> newmember: it is either you are missing the i386 image , or the import of images hasn't completed
[19:45] <kiko> newmember, I'm slightly surprised that enlistment is trying to use the i386 image
[19:45] <kiko> newmember, what hardware are you enlisting?
[19:48] <newmember> I used the autopilot ova from ubuntu
[19:48] <kiko> newmember, what's happening is this:
[19:48] <kiko> - pxelinux's ifcpu64 module is determining your machines are 32-bits only
[19:49] <kiko> - it then tells MAAS to boot using a 32-bit kernel
[19:49] <kiko> - the 32-bit images are not yet imported in MAAS, so it fails
[19:49] <newmember> I think everything has to be 64bit
[19:50] <kiko> newmember, definitely -- the question is why is this not working in your situation
[19:51] <kiko> newmember, are these actual machines, or VMs?
[19:51] <newmember> vms on esxi6
[19:51] <kiko> ah
[19:51] <kiko> newmember, and these vms, are they configured to be 32-bit or 64-bit?
[19:51] <newmember> i imported the ova from ubuntu
[19:51] <newmember> looking
[19:52] <kiko> hmmm!
[19:53] <kiko> newmember, I am a bit clueless about our autopilot vmware install (and vmware) -- so the ova contains the machine definitions already?
[19:53] <newmember> just on a call, please hang on
[19:54] <kiko> sure
[19:54] <newmember> but thanks
[19:59] <newmember> its 64bit
[19:59] <newmember> http://picpaste.com/Capture2-ybPaWJdf.PNG
[20:05] <kiko> newmember, well.. that doesn't actually say the machine is 64-bit
[20:05] <kiko> newmember, anyway, can you import the i386 images and see if it works?
[20:11] <kiko> newmember, I need to split but will look through the channel traffic later tonight or tomorrow morning
[20:12] <newmember> cheers
[20:13] <roaksoax> newmember: while it may be 64 bit VM, pxelinux may be identifying it as i386
[20:13] <roaksoax> newmember: i've seen that before
[20:15] <kiko> dpb1, ping
[20:15] <kiko> dpb1, have you seen the above?
[20:15] <roaksoax> not specifically with vmware though
[20:17] <dpb1> we haven't seen that specifically, no
[20:19] <dpb1> would be interested to see versions though, if you get to that.
[20:19] <dpb1> kiko: just so you know, the autopilot doesn't do anything directly with vmware.  we treat it as a regular maas node.
[20:19] <dpb1> the instructions we have also need to be followed exactly
[20:24] <kiko> dpb1, right, but do we provide the machine definitions (in machine-readable or doc form), or are they to be manually created?
[20:28] <mup> Bug #1611949 opened: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>
[20:31] <mup> Bug #1611949 changed: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>
[20:40] <mup> Bug #1611949 opened: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>
[22:50] <mup> Bug #1611980 opened: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:New> <https://launchpad.net/bugs/1611980>
[22:59] <mup> Bug #1611980 changed: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:Incomplete> <https://launchpad.net/bugs/1611980>
[23:05] <mup> Bug #1611980 opened: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:Incomplete> <https://launchpad.net/bugs/1611980>
[23:32] <mup> Bug #1611984 opened: MAAS images page doesn't correctly report image status <angularjs> <notifications> <yui> <MAAS:Confirmed> <https://launchpad.net/bugs/1611984>