v1k0d3nso the error initially is about bootif: siocgifindex: no such device.00:10
v1k0d3nwondering if this could have anything to do with running M.2 drives?00:10
=== CyberJacob is now known as zz_CyberJacob
=== frankban|afk is now known as frankban
mupBug #1611711 opened: [API] block-device 'add/remove_tag' operations use GET method, not POST <MAAS:Triaged> <https://launchpad.net/bugs/1611711>10:42
mupBug #1611726 opened: Documentation for machine create API doesn't say that power_type is required <MAAS:New> <https://launchpad.net/bugs/1611726>11:24
mupBug #1340920 changed: Extra slash in /etc/apt/sources.list; prevents connecting to some servers <papercut> <trivial> <MAAS:Triaged> <https://launchpad.net/bugs/1340920>13:03
mupBug #1611761 opened: [2.0 RC3 ] Unhandled Error - maasserver.models.regioncontrollerprocess.DoesNotExist <oil> <oil-2.0> <MAAS:New> <https://launchpad.net/bugs/1611761>13:33
newmemberI 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:45
newmemberOr get maas to re-try auto discovery?13:46
roaksoaxnewmember: what do you mean by auto-discovery ?13:47
newmemberwhen installing maas it appears to look at the network for nodes, it found one.13:48
newmemberi see all the nodes picked up an IP address form maas13:48
newmemberfrom maas13:49
roaksoaxnewmember: maas doesn;t look at the network for nodes13:54
roaksoaxnewmember: if a machine that maas knows nothing about, DHCP's from MAAS13:54
roaksoaxwe will know that /something/ has DHCP'd13:54
roaksoaxnewmember: but typically, MAAS "auto" discovers machines when machines DHCP from MAAS *and* PXE boot from MAAS13:55
kikonewmember, you basically need to PXE boot all your 12 nodes against MAAS13:58
junaidaliHi everyone, what is the default password that MAAS sets for a node? preseeds master file doesn't specify any password15:53
junaidaliis there a way that we can use for setting up password for the nodes that we deploy?15:54
=== frankban is now known as frankban|afk
kikojunaidali, there's no default password -- use the registered ssh key to log in17:07
kikojunaidali, the default user on ubuntu is called ubuntu, and on centos is centos17:07
junaidalithanks. Is there any setting to set the password for every node that we're provisioning?17:08
junaidalipassword for ubuntu user*17:10
kikojunaidali, 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 though17:21
junaidaliThanks kiko17:41
nturnerIf I want to add CentOS images to my MAAS setup, is that possible?17:42
nturnerThe docs seem to imply that it is, but don't describe how.17:42
junaidaliin MAAS 2.0, it is pretty easy. which version of MAAS are you using?17:44
nturnerjunaidali: I'm using 2.0.0~rc3+bzr5180-0ubuntu2~16.04.117:45
* nturner sees 2.0.0~rc4+bzr5187-0ubuntu1~xenial1 is now available and updates...17:47
blake_rnturner: centos images are in the images page, you can just import them17:49
nturnerhere's what I see on that page: https://snag.gy/XounFl.jpg17:54
nturnerAm I tracking the wrong thing? Under Settings my Boot images Sync URL is https://images.maas.io/ephemeral-v2/releases/17:56
nturnerWhich is whatever MAAS defaulted to. Maybe the default has changed for new installs but upgrades don't change it?17:56
nturnerblake_r: What Sync URL are you using?17:57
kikonturner, can you change releases to daily?17:57
nturnerwell, golly, that was easy!17:58
nturnerThanks all.17:58
newmemberthanks kilo18:39
newmemberI am using the autopilot deployment from Ubuntu18:39
newmemberI installed MAAS18:39
newmemberI created 12 nodes18:39
newmemberWhen I look on MAAS all I see is the one node created in MAAS none of the other nodes are created in MAAS18:40
newmemberI would have thought that they all auto create in MAAS18:40
newmemberthey are all getting DHCP from MAAS18:40
newmemberMaybe autopilot uses the vmware api to get the 'node' names and load them in MAAS, maybe its not a DHCP discovery thing18:41
kikonewmember, you don't need to create the nodes manually19:16
kikonewmember, and in fact, I argue you shouldn't19:16
newmemberkiko, okay19:18
kikonewmember, instead, just PXE-boot the machines and see them appear19:25
kikonewmember, if they don't appear, you have a problem that needs fixing19:27
newmemberkiko, I think I have a problem that needs fixing :)19:28
kikonewmember, do the machines PXE boot successfully?19:29
newmembergets an ip address19:31
newmemberbooting under maas19:31
newmembersome long line of stuff19:31
newmemberthen stops at "boot:"19:31
newmemberthere is a note:  could not find kernel image19:32
kikonewmember, could you get us a screenshot?19:36
newmemberkiko, great idea19:41
kikonewmember, yeah, that's definitely odd. what releases do you have selected in your images page?19:42
roaksoaxnewmember: it is either you are missing the i386 image , or the import of images hasn't completed19:43
kikonewmember, I'm slightly surprised that enlistment is trying to use the i386 image19:45
kikonewmember, what hardware are you enlisting?19:45
newmemberI used the autopilot ova from ubuntu19:48
kikonewmember, what's happening is this:19:48
kiko- pxelinux's ifcpu64 module is determining your machines are 32-bits only19:48
kiko- it then tells MAAS to boot using a 32-bit kernel19:49
kiko- the 32-bit images are not yet imported in MAAS, so it fails19:49
newmemberI think everything has to be 64bit19:49
kikonewmember, definitely -- the question is why is this not working in your situation19:50
kikonewmember, are these actual machines, or VMs?19:51
newmembervms on esxi619:51
kikonewmember, and these vms, are they configured to be 32-bit or 64-bit?19:51
newmemberi imported the ova from ubuntu19:51
kikonewmember, I am a bit clueless about our autopilot vmware install (and vmware) -- so the ova contains the machine definitions already?19:53
newmemberjust on a call, please hang on19:53
newmemberbut thanks19:54
newmemberits 64bit19:59
kikonewmember, well.. that doesn't actually say the machine is 64-bit20:05
kikonewmember, anyway, can you import the i386 images and see if it works?20:05
kikonewmember, I need to split but will look through the channel traffic later tonight or tomorrow morning20:11
roaksoaxnewmember: while it may be 64 bit VM, pxelinux may be identifying it as i38620:13
roaksoaxnewmember: i've seen that before20:13
kikodpb1, ping20:15
kikodpb1, have you seen the above?20:15
roaksoaxnot specifically with vmware though20:15
dpb1we haven't seen that specifically, no20:17
dpb1would be interested to see versions though, if you get to that.20:19
dpb1kiko: just so you know, the autopilot doesn't do anything directly with vmware.  we treat it as a regular maas node.20:19
dpb1the instructions we have also need to be followed exactly20:19
kikodpb1, right, but do we provide the machine definitions (in machine-readable or doc form), or are they to be manually created?20:24
mupBug #1611949 opened: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>20:28
mupBug #1611949 changed: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>20:31
mupBug #1611949 opened: cryptic error when PXE-boot requires an image not yet imported <MAAS:New> <https://launchpad.net/bugs/1611949>20:40
mupBug #1611980 opened: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:New> <https://launchpad.net/bugs/1611980>22:50
mupBug #1611980 changed: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:Incomplete> <https://launchpad.net/bugs/1611980>22:59
mupBug #1611980 opened: Upgrade from MAAS 2.0 RC3 to RC4 has pre-removal script error messages <MAAS:Incomplete> <https://launchpad.net/bugs/1611980>23:05
mupBug #1611984 opened: MAAS images page doesn't correctly report image status <angularjs> <notifications> <yui> <MAAS:Confirmed> <https://launchpad.net/bugs/1611984>23:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!