[02:08] <mup> Bug #1585841 opened: It would be great if MAAS can support ZFS on the 'Storage' configuration part <MAAS:New> <https://launchpad.net/bugs/1585841>
[06:29] <mup> Bug #1585878 opened: It does not remove the DHCP and DNS configurations on MAAS after juju removes LXD container(machine). <MAAS:New> <https://launchpad.net/bugs/1585878>
[06:32] <jojden> why newly created vm using pxe boot is not listing in the maas
[06:53] <mup> Bug #1585878 opened: It does not remove the DHCP and DNS configurations on MAAS after juju removes LXD container(machine). <MAAS:New> <https://launchpad.net/bugs/1585878>
[06:54] <jojden> hi roaksoax
[07:17] <mup> Bug #1585878 changed: Removing a container does not remove the underlying MAAS device representing the container unless the host is also removed. <juju-core:Triaged> <https://launchpad.net/bugs/1585878>
[07:18] <jojden> roaksoax http://askubuntu.com/questions/777665/why-newly-created-vm-using-pxe-boot-is-not-listing-in-the-maas
[08:00] <huats> Nobody  to help me a bit with that "out-of-sync" image thing that I am facing ?
[11:36] <mup> Bug #1586000 opened: Make terminology clearer through tooltips <MAAS:New> <https://launchpad.net/bugs/1586000>
[12:06] <mup> Bug #1586006 opened: Rearrange DHCP information on VLAN details page <MAAS:New> <https://launchpad.net/bugs/1586006>
[13:39] <kiko> huats, sure, what's up?
[13:40] <kiko> terje, the thing is that the whole cluster interfaces API changed
[13:40] <kiko> terje, check out the new API under /docs2.0
[13:40] <kiko> mahmoh, never seen that before, did you figure it out?
[13:45] <roaksoax> jojden: 2016-05-26 06:24:26,012 - url_helper.py[WARNING]: Calling 'http://10.20.0.12/latest/meta-data/instance-id' failed [0/120s]: bad status code [404] -> is 10.20.0.12 the IP of your region controller ?
[14:06] <huats> Hi kiko .
[14:06] <huats> I have added a custom image
[14:06] <huats> and sice I am facing an image "out-of-sync"
[14:06] <huats> and I don't seen how to fix that
[14:06] <huats> (and how course the custom image is not usable...)
[14:07] <kiko> huats, any crashes showing up in /var/log/maas* or syslog?
[14:07] <kiko> huats, if you remove the image does it work again?
[14:07] <huats> actually I can use the "old" image
[14:08] <huats> it is just the new one that is not "showing up"
[14:08] <kiko> huats, images are uploaded first to the region, and then copied to the cluster filesystem
[14:08] <kiko> huats, so it's likely your image is not syncing down
[14:08] <huats> probably
[14:08] <kiko> but why, the logs may be able to tell us
[14:08] <huats> ok
[14:09] <huats> I am ooking
[14:35] <mahmoh> kiko: no, it was technically terj-e's problem, just bubbling it up for him
[14:53] <huats> kiko: sorry I had to switch to something else
[14:53] <huats> I don't see any error in the logs :(
[15:55] <mup> Bug #1426010 changed: Tests using Selenium are all failing <tech-debt> <tests> <MAAS:Fix Released by allenap> <https://launchpad.net/bugs/1426010>
[15:55] <mup> Bug #1459168 changed: Start-up stacktrace: IntegrityError: duplicate key value violates unique constraint "maasserver_config_name_uniq" DETAIL:  Key (name)=(rpc_shared_secret) already exists. <stacktrace> <start-up> <MAAS:Invalid> <https://launchpad.net/bugs/1459168>
[18:03] <shewless> Hello. I have a network that I would like to change the "DNS" IP on (it's currently blank) but I don't see an easy way to edit the subnet from the UI (I can only delete it). Is there a way to do this from the server level?
[18:04] <shewless> sorry. I mean a subnet.. MAAS 2.0
[18:09] <kiko> shewless, the API lets you do this; I believe 2.0 final will give you UI, right roaksoax?
[18:14] <pacavaca> Hi, kiko. Last week me and some other guy were asking here how to create custom ubuntu/centos images, with custom configs and packages installed (custom fs snapshot). You said that someone may write a public answer to that. So, I'm just wondering, maybe it's published somewhere already. Thanks.
[18:15] <kiko> pacavaca, still on my todo, but a short answer for custom ubuntu is lp:curtinator
[18:15] <kiko> that's roadmr's project which helps roll custom ubuntu images
[18:15] <pacavaca> cool, will check it out. thank you
[18:16] <roadmr> pacavaca: with curtinator you can build maas-installable images from stock Ubuntu ISOs, as long as you can express your config in a standard preseed, you should be able to hack curtinator into doing what you need
[18:31] <pacavaca> roadmr: am I right that it downloads ubuntu iso then installs it on some kvm vm then takes an fs snapshot, mixes it with preseed scripts and then packs everythin in a tarball, which is something maas can consume?
[18:32] <kiko> yep
[18:32] <roadmr> pacavaca: somewhat. You need to provide the iso locally (just wget it ;). Also, the preseeds are applied at *install* time
[18:33] <roadmr> pacavaca: so it'll boot the provided ISO in a kvm, pointed to the given preseed, and when the install finishes it'll package the resulting filesystem contents in a tarball for maas
[18:33] <roadmr> pacavaca: the main maas-related thing it does is install cloud-init, but you can hack the preseed to install more packages and maybe write custom files
[18:34] <pacavaca> I see. That sounds like what I need. Thank you
[18:35] <roadmr> cheers!
[18:40] <kiko> you rock roadmr
[18:40] <roadmr> thanks :) I'm glad curtinator is proving helpful
[18:57] <shewless> kiko: thanks. another question:
[18:58] <shewless> I'm trying to make my "fqdn" of my hosts be something specific (say: node-name.foo.com) instead of node-name.maas
[18:58] <shewless> I don't care if .maas is still there.. basically I have a "maas" fiber and a "foo.com" fiber.. and different subnets for both
[18:59] <shewless> right now I have the dns servers and IPs and everything working (the foo.com subnet is statically assinged)
[18:59] <shewless> I'm also using the DNS forwarder option
[18:59] <shewless> all is good except the nodes "hostname -f" still reports node-name.maas instead of node-name.foo.com
[18:59] <roaksoax> shewless: if you are using 1.9, you change the DNS zone / domain in the cluster controller
[19:00] <shewless> roaksoax: 2.0
[19:00] <roaksoax> shewless: if you are using 2.0, you add a new DNS domain, change the domain in the machine itself, and deploy
[19:00] <shewless> roaksoax: I tried that but it seems to map the domain name of the machine to the wrong subnet
[19:00] <shewless> I'm not sure how to change that part
[19:01] <roaksoax> shewless: <hostname>.<domain> will always map against the IP of the PXE interface
[19:02] <roaksoax> shewless: <interface>.<hostname>.<domain> PTR records are available against all of the interfaces
[19:02] <shewless> roaksoax: right I don't want the domain to map to the pxe interface
[19:02] <roaksoax> shewless: you wont be able to change that unfortunately
[19:02] <shewless> I'm not sure what you mean by "interface.hostname.domain" - do you think that would work and how do I do it?
[19:03] <roaksoax> shewless: for example, your node interfaces is this:
[19:03] <roaksoax> eth0 fabric-0 untagged subnet-1 X.X.X.X
[19:04] <roaksoax> eth1 fabric-1 vlan10  subnet-10 Y.y.y.y
[19:04] <roaksoax> shewless: X.X.X.X -> node01.foo.com
[19:04] <roaksoax> shewless: X.X.X.X -> eth0.node01.foo.com
[19:04] <roaksoax> shewless: Y.Y.Y.Y -> eth1.node01.food.com
[19:04] <roaksoax> shewless: Y.Y.Y.Y -> eth1.node01.foo.com
[19:05] <shewless> okay how do I do that? that seems to be what I want
[19:05] <roaksoax> shewless: that's done automatically
[19:05] <shewless> oh wait.. you actually have to have the interface name in the dns?
[19:05] <roaksoax> shewless: yes
[19:05] <shewless> roaksoax: I tried adding a DHCP snippet to the "PXE" subnet... option domain-name 'foo.com" which actually worked from a lease perspective.. but the "lo" interface still has a domain name of "maas"
[19:05] <roaksoax> shewless: go to 'DNS' section
[19:06] <shewless> roaksoax: k
[19:06] <roaksoax> shewless: add a domain 'foo.com'
[19:06] <shewless> did
[19:06] <roaksoax> shewless: go to the machine details page
[19:06] <shewless> (none authoritative)
[19:06] <roaksoax> shewless: click on the hostname, and change node.maas to node.foo.com
[19:06] <shewless> roaksoax: did
[19:06] <shewless> roaksoax: but the dns maps to the PXE interface
[19:07] <roaksoax> shewless: yes, that will never change
[19:07] <roaksoax> shewless: we always map the <hostname>.<domain> to the PXE interface
[19:07] <roaksoax> shewless: so eth0 (PXE) - X.X.X.X - node01.foo.com | eth0.node01.foo.com
[19:07] <shewless> roaksoak: okay. So I need to solve my problem in a different way
[19:08] <shewless> roaksoax: I'm trying to deploy a "production" server on my network with a provisioned IP and a DNS name that is managed by an external DNS server. I think this would be common right?
[19:09] <shewless> roaksoak: so my network guy says "assign static IP y.y.y.y" and I've added a dns record of node.foo.com for you
[19:09] <shewless> roaksoak: right now it's all good (I have maas statically assign IP and update the DNS server) except the fqdn is wrong
[19:10] <roaksoax> shewless: I see your point now. Right, we don't have a way to change that actually
[19:10] <shewless> roaksoak: IE: hostname -f returns "node01.maas".  So I'm so close :)
[19:11] <shewless> if we could make it so "lo" on the nodes doesn't have the domain option set to maas I think it would work with my DHCP snippet
[19:11] <shewless> any chance we could change that?
[19:13] <roaksoax> shewless: i think you could do it via preseeds, as in change the hostname automatically
[19:13] <roaksoax> shewless: like writing a script to change the hostname to what you want
[19:14] <shewless> roaksoax: that could work. I've never done a preseed before. any hints ? :)
[19:15] <roaksoax> shewless: let me get my environment back up and reproduce what you are trying to do
[19:17] <shewless> roaksoax: I think I literally just need to execute this command: echo $(cat /etc/hostname).foo.com > /etc/hostname
[19:18] <shewless> roaksoax: before boot.  If it's after boot I'd also need to run "hostname" to change the rest
[19:20] <roaksoax> shewless: in /etc/maas/preseeds/curtin_userdata try something like thois:http://paste.ubuntu.com/16715744/
[19:25] <shewless> raoksoax: thanks I'll give that a try. I can just edit that file manually?
[19:28] <roaksoax> shewless: yeah
[19:28] <roaksoax> shewless: that's the preseed
[19:35] <roaksoax> shewless: let me konw if that works
[19:35] <roaksoax> shewless: and how are you finding the DHCP snippet feature btw ?
[19:39] <shewless> roaksoax: will let you know. the DHCP snippet worked exactly as expected for the subnet
[19:40] <shewless> roaksoax: for the "node" it just didn't add the snippet at all.. no error.. just didn't add it
[19:43] <shewless> roaksoax: do I have to restart any services to get the preseed to work or just re deploy
[19:43] <roaksoax> shewless: just redeploy IIRC
[19:44] <shewless> roaksoax: trying now.. will keep you posted
[19:51] <shewless> roaksoax: didn't seem to work.. /etc/hostname is not changed
[19:54] <shewless> roaksoax: here is the rsyslog: http://paste.ubuntu.com/16716515
[19:56] <roaksoax> shewless: it doesn't seem like it failed ?
[19:56] <shewless> roaksoax.. you are right... I didn't see anything that appeared to fail
[19:57] <shewless> roaksoax: but at the same time it didn't appear to work
[20:01] <shewless> roaksoax: can I run the userdata thing manually after the fact to see if it worked?
[20:19] <roaksoax> shewless:
[20:19] <roaksoax> root@acerbic-rufus:/home/ubuntu# echo $(cat /etc/hostname).foo.com > /etc/hostname
[20:19] <roaksoax> root@acerbic-rufus:/home/ubuntu# hostname -f
[20:19] <roaksoax> acerbic-rufus.maas
[20:19] <roaksoax> shewless: even doing it manually doesn't work
[20:22] <roaksoax> shewless: do you need the hostname of the machine to reflect the hostname ?
[20:22] <shewless> roaksoax: if you check /etc/hostname you'll see it's changed.. on next boot it would work.. or you can do "sudo hostname `cat /etc/hostname`" if you don't want to wait
[20:23] <shewless> roaksoax: but the point is I can see that the preseed didn't change the /etc/hostname file at all for me
[20:23] <roaksoax> shewless: i think that may be because cloud-init change the hostname after first boot
[20:23] <roaksoax> or at least I think that's what is happening
[20:23] <roaksoax> shewless: so you absolutely need the machine to be deploed with such hostname ?
[20:26] <shewless> roaksoax: I agree I saw a bunch of hostname stuff in cloud.cfg on the box
[20:26] <shewless> roaksoax: I do need it. Right now I'm just manually doing it
[20:26] <roaksoax> shewless: the other thing you could do
[20:27] <roaksoax> shewless: is to write a script that change sit or similar
[20:27] <roaksoax> shewless: after cloud-init writes it
[20:28] <roaksoax> shewless: ohhh I have an idea
[20:28] <roaksoax> shewless: let me test it though
[20:29] <shewless> roaksoax: sounds good
[20:34] <roaksoax> shewless: wont work. I was thinking of giving an IP to second NIC, and assigning a DNS name like nodeXX.foo.com
[20:34] <roaksoax> shewless: so you wouldn;t need external DHCP/DNS
[20:34] <roaksoax> shewless: but that won't set the machine's hostname to <hostname>.foo.com
[20:35] <roaksoax> shewless: i'l talk to the team and see if we can prpovide the ability to selcet which interface would get the actualy hostname you are looking for
[20:35] <roaksoax> shewless: but that wont happen till next week
[20:36] <shewless> roaksoax: thanks for the help.  In the mean time I'll just manually set the hostname. I appreciate your help
[20:36] <roaksoax> sorry i couldn't be of more help though
[22:45] <aslaen> Hello I am not sure I did wrong but I can't get a node to provision.  I have MaaS installed correctly and when I PXE boot a node it pulls IP from MaaS, and starts to bootstrap, but then it stops at "yay system is up!" and doesn't complete the process.
[22:45] <aslaen> any ideas?