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