[04:22] Bug #1582070 opened: Pick up wrong grub.cfg if another filesystem exist === Guest16410 is now known as CyberJacob [11:33] hello! [11:34] I have downloaded images to install to my nodes but maas sends me "could not find kernel image" [11:34] do you know whats happening [11:34] ? [11:53] plz ? :D47 [12:10] fantastic maas gurus? :D [13:45] Bug #1569483 changed: [2.0] Can't deploy CentOS [14:15] Bug #1582243 opened: [2.0b5] Rack controller FAILED authentication from '192.168.10.3:59270'; dropping connection. === frankban|afk is now known as frankban [16:04] Bug #1582293 opened: Allow secure wipe of New systems before Commissioning [fails] [16:56] hi, I have some compute nodes I'd like to install, that contain a pre-existing OS. [16:56] They have a /ec2/ directory with some cloud-init stuff in there and so maas isn't imaging them properly. [16:57] Is there a way to tell MAAS to wipe the disks before trying to commissioning them? [17:07] hello. I installed maas on ubuntu 16.04 and I cannot find the "DHCP configuration" part in the web interface. I think I have to add a subnet but I'm not sure [17:07] Bug #1582323 opened: Commissioning fails when competing cloud metadata resides on disk [17:08] I know which interface I want to be the dhcp/pxe server. But I'm unsure exactly how to configure that. Do I just add a subnet and "provide DHCP"? Do I have to assign an IP from the DHCP range on my MAAS server? [17:09] The getting started page is kind of useless http://maas.io/get-started I think because I'm using 16.04... but [17:09] The turn on DHCP and DNS part is totally different [17:10] shewless: networks -> click untagged for the network [17:10] then, take action [17:12] shewless, what terje said [17:12] shewless, it will get better with the new install experience we're working on [17:12] terje: thanks. I did that. It told me there is no subnet. So I created a subnet [17:13] terje: but do I have to manually assign an IP address to my maas interface? [17:13] or does maas take care of that [17:14] (I have a management network already setup so I can get to the UI, but I want to use a different interface for dhcp) [17:17] kiko: I think I have to assign an IP address to the interface I intend to use as the dchp provider. Is there a way to do that through maas? [17:17] manually assign it [17:18] no, there isn't. Edit /etc/network/interfaces [17:18] shewless, no, it's a common question [17:19] thanks guys. I can do that. Should the "gateway" be the maas server itself (I'm setting up a private network just for maas to provision) [17:20] shewless: that's how I do it. [17:21] you then have to configure nat/masquerading in iptables [17:21] so you're computes can get out to the world and download stuff they need. [17:21] on the gateway/maas system. [17:22] yikes.. how do I do that? [17:25] something like this: http://pastebin.com/raw/fvVjJPg9 [17:27] eth0 would be my "management" port with internet access? [17:30] yes, the interface with an IP that can 'ping 8.8.8.8' for example. [17:33] terje: Sould the "dhcpd" service be running in the "services" section of my maas controller? [17:33] my machines don't appear to be getting dhcp offers from my maas server [17:33] on the maas server, do: ps aux|grep dhcp [17:34] hmm.. doesn't appear to be running [17:34] can you show me (on pastebin): [17:34] ip a s [17:34] and [17:35] cat /etc/network/interfaces [17:36] http://pastebin.com/26zy0TWC [17:36] you don't have an IP on enp2s0 for your private network [17:37] 48 [17:37] oops [17:37] actually.. [17:38] you're using 169.254 [17:38] this is a special network - don't use it. [17:38] change that to 172.20.0/24 for example. [17:39] ah crap.. how embarassing [17:45] terje: that actually makes more sense. as soon as a added the IP to the interface maas automatically picked up the subnet [17:48] terje: okay dhcpd is now running .. that's good. for some reason my device still didn't pxe boot though [18:15] terje: I can see that dhcpd is running, but when I boot my node via PXE is does not receive an offer. I tried booting my node from hard disk and then manually configuring the pxe NIC to ensure they can talk.. and they can [18:15] any ideas? [18:21] I see this in the logs: [18:21] DHCPDISCOVER from 00:25:90:52:3c:cd via enp2s0: network vlan-5002: no free leases [18:23] I tried to reconfigure the dhcp in the "take action" menu. we'll see if that helps [18:28] you can't pxeboot on a VLAN'd interface. [18:29] needs to be a flat network [18:32] terje: I'm not sure why it has a vlan there. After re-configuring DHCP on the interface it seems to allow the systems to PXE boot [18:32] I can see they are all running 16.04 LTS now.. but they are not showing up in maas for some reason [18:32] Would I see them in the "Nodes" tab? [18:32] yes [18:33] so, login on console to one of them and manually pxeboot it [18:33] then, watch it go [18:33] I did [18:33] it looks like it puts ubuntu on it [18:33] that's not how it works. [18:34] so I shouldn't be staring at a login prompt? [18:34] no [18:34] that's likely from a previous install [18:34] I can see it PXE boots [18:34] I'll watch the console more closely [18:34] it will pxeboot an image, then publish information to maas about the hardware. [18:35] maas will mark the hardware as 'new' [18:35] can you login to one of the 16.04 systems? [18:35] I'm curious about something [18:35] I see booting under MAAS dircation.. [18:36] loading ubunttu/amd64/generic/xenial/release/boot-kernel [18:36] yep, that's all correct [18:36] and then it proceeds to boot [18:36] can you login to the OS once it boots? [18:36] uh.. not sure what the login would be [18:37] under nodes, you don't see anything, correct? [18:37] oddly it's presenting itself as "node-1" should it have that hostname? [18:37] correct.. .nodes is empty [18:37] ok, so maas didn't install that OS [18:38] but I can see the whole "MAAS direction" [18:38] what's happening is [18:38] and I know these guys weren't running 16.04before [18:38] maas pxeboot's the thing [18:38] loads a ramdisk [18:39] decides for some reason that it's not going to use it and it reboots from disk. [18:39] you're maas didn't put an OS on there.. [18:39] trust me. :) [18:39] I trust you :) [18:39] ok, so you need to login to one of those computes. [18:40] I don't know what the login is [18:41] ok, so boot one of those computes from the ubuntu 16.04 install ISO and go into rescue mode. [18:42] okay. I can do that. What will I be looking for? [18:42] you want to boot into a shell [18:42] once you have a shell, run: dd if=/dev/zero of=/dev/sda bs=512 count=1000 [18:43] then, pxeboot that compute again [18:43] this obviously nukes your disk so just tripple check this is the compute you think it is. :) [18:44] I see. I used a different "imager" mirantis fuel.. so maybe it left these nodes in a weird state [18:45] I think I know the issue [18:45] and that is, maas uses cloud-init when it profiles the system. [18:45] if the previous installer left some cloud-init stuff on sda, maas will refuse to use it. [18:47] I see. it's weird because I knew what the root password was but maas seemed to have changed it.. is that possible? [18:47] by wiping sda, you'll resolve the issue. [18:47] no [18:48] maas isn't doing anything to those systems. [18:49] okay. let me try and wipe the disks [19:03] if booting from ISO, use "rescue a broken system" to get a shell [19:11] terje: thanks.. . my first system is now showing in "nodes" so I guess that did the trick [19:11] one last question for you.. [19:13] sure [19:13] who's the man? [19:13] :P [19:15] terje is the man :P [19:16] I'm setting up my own 16.04 OS cluster right now as well. [19:16] so, maybe we can help each other [19:16] I'll do what I can to help [19:18] it would be supper if MAAS could give the option to auto clear the cloud-init space [19:18] or just wipe the disks prior to doing an inventory [19:18] yeah [19:19] perhaps it can [19:19] and I just don't know about it [19:32] terje: So My IPMI is on my "management" network.. my maas controller is on the same network but for some reason cannot ping the IPMI guys [20:12] you're not able to ping your IPMI interfaces from the maas controller? [20:14] that doesn't sound right to me. [20:14] are you planning to install openstack on your cluster? [20:14] terje: I can now. I guess the default state for un-commissioned nodes is to turn them off [20:15] yea, it is. [20:15] that kept screwing with me [20:15] ah [20:15] so, again, is this going to be an openstack deployment? [20:15] I am planning on installing openstack, yes [20:15] have a look at this: http://conjure-up.io/ [20:17] hmm. so maas, juju, and now conjure-up? [20:17] conjure-up is for 16.04 only [20:17] if you're using 14.04 then I think it's autostart [20:17] and pretty awesome [20:17] "autopilot"? [20:19] I guess I need to figure out how to get juju installed then first [20:19] no, I don't think you do [20:19] sudo apt-get install conjure-up [20:19] sudo conjure-up openstack [20:22] so what is the intention of this conjure-up? [20:23] and should I conjure "OpenStack" or "OpenStack Autopilot" [20:24] done for now.. good luck [20:24] okay thanks terje [20:36] network-interface-peeps: https://github.com/juju/juju/issues/5409 [21:41] Bug #1582418 opened: # of cpu cores and amount of ram incorrectly reported [22:30] Hey guys! Is it possible to deploy an image created by clonezilla with maas? Or, what's the other good way to get customized (some configs + packages) ubuntu/centos version deployed by maas?