[01:14] if anyone knows the syntax for /etc/maas/presee/curtain_userdata please ping me === X-Rob_ is now known as X-Rob [03:15] found a good one: http://astokes.org/customizing-fastpath-curtin-installations/ [03:15] this should be part of the official documentation! [05:25] Bug #1461389 was opened: Parse errors for curtin preseeds aren't reported <1.7> [09:20] Bug #1461462 was opened: Node action permission not updated as node status changes [12:24] Quick question for everyone, any suggestions on where to start with debugging dns not working? Whenever I try to ssh in between boxes that were stood up with maas using their dns names I just get no route to host even though I have dns configured [12:24] Everything else about my maas setup is working [12:49] bleepbloop: are you sure that /etc/resolv.conf is pointing to the MAAS DNS server when you are trying to ssh ? [12:50] roaksoax, the resolv.conf on one of the instantiated machines has nameserver 172.16.0.1 and search maas in it [12:51] roaksoax: however trying to ping ping kit-fisto.maas (the maas server) from it gets ping: unknown host kit-fisto.maas [12:53] bleepbloop: where are you trying to ping kit-fisto.maas ? [12:53] bleepbloop: in the same machine where you are trying to ping kit-fisto.maas, does /etc/resolv.conf have nameserver as first nameserver entry? [12:54] roaksoax: from a server that is on the same network as maas and which was provisioned by maas, and yeah the resolv.conf was on the machine provisioned by maas (which is the one I was trying to ping from) [12:54] bleepbloop: so kit-fisto.maas is the machine deployed by mAAS? [12:55] bleepbloop: or you are trying to ping another machine deployed by MAAS [12:55] roaksoax: I am kit-fisto.maas is the maas server, plo-koon (the machine I tried to ping kit-fisto from) is the maas provisioned client [12:56] bleepbloop: right, so if kit-fisto.maas is the maas server, that's not in the DNS server that MAAS server controls [12:56] rvba: ^^ [12:58] bleepbloop: so 172.16.0.1 is kit-fisto.maas ? [12:59] rvba:yes [12:59] roaksoax: so the maas server doesn't add an entry for itself in dns? [13:00] bleepbloop: nope [13:01] bleepbloop: otherwise it would have to add an entry for the same DNS name in all of the networks MAAS can be present [13:01] i.e. if we have 10 cluster controllers on different networks, there would be 10 dns entries for different IP's [13:02] roaksoax: hmm okay fair, would it be a bad idea to add it manually? [13:09] Bug #1461295 changed: Maas is not picking up new release root-tgz automatically [13:30] Bug #1461389 changed: Parse errors for curtin preseeds aren't reported <1.7> [16:45] Bug #1461612 was opened: make static ip ranges required [17:45] what is the difference between the follwing: "curtin in-target -- sh -c script", "['curtin', 'in-target', '--', script], ['curtin', 'in-target', '--', 'sh', '-c', script] ? [17:45] maybe smoser can help? [17:46] if the entry in the late_commands is a string, then it will be passed to sh [17:46] if it is an array, then it will be executed like execve [17:46] array is much more specific, you dont leave naything up to shell interpretation. [17:47] ['curtin', 'in-target', '--', script] [17:47] thats not going to do anything. unless the string 'script' is an executable. [17:47] inside the root [17:47] ...which it actually is :) [17:54] Bug #1461639 was opened: Spurious test failure maasserver.tests.test_forms_nodeaction.TestNodeActionForm.test_save_performs_requested_action [17:58] mmh so custom: ["mkdir", "/some/dir"] should do the same as custom: "mkdir /some/dir" ? [18:33] none of them seem to have an effect on my machine. :/ [19:00] smoser: I upgraded MAAS to the latest stable, 1.7.5, and still have not had any luck getting user_data to run on nodes commissioned with this new version [19:01] smoser, if we could figure this out I'd like it documented in the maas docs -- but we need to find out how it is to be done. maybe write up a txt file we could use as a starter? :) [19:04] kiko: I'd be happy to test out any techniques for deploying user_data to help with the documentation process [19:05] thanks [19:06] drhalan, yes to your answer above. [19:07] kiko, i'm 98% certain that user_data works [19:07] so i'm 100% certain that user data works [19:07] otherwise juju wouldn twork [19:07] i'm 99% certain that it works via maas cli [19:08] i've used it before, but dont have anything i can use it with righ tnow [19:18] garibaldi: same here.. it does something but not sure what... gave up after about 10 hours of trying different commands [19:23] smoser, we can get you access to a maas installation easily, would that suffice? you're right now the only person who I think knows how this works [19:34] hi. So I installed maas while installing ubuntu server. When I connect to maas region controller web interface, I see standard apache web page instead of maas page, why ? [19:36] solsTiCe: http://XYZ/MAAS ? [19:36] ah ok. forgot /MAAS [19:36] Bug #1461659 was opened: UEFi x64 failing to commission [19:41] kiko, sure. let me see a maas. [19:48] smoser, does the garage maas work? [19:49] checking [19:49] cool [19:57] kiko, ok. i just did: [19:57] http://paste.ubuntu.com/11549450/ [19:57] smoser, and can you paste the raw userdata? [19:58] nice [19:58] well, garage maas is broken [19:58] its left in bcache-development limbo [19:59] and that means we can't? [19:59] so kiko until that is fixed i cant test install something, so ... [19:59] test [20:00] http://paste.ubuntu.com/11549482/ [20:00] but that is the user-data [20:02] ok. just ran this. [20:02] http://paste.ubuntu.com/11549501/ [20:02] on my local maas (i didn't want to shoot that node, but i did) [20:03] local maas is [20:03] # dpkg-query --show maas [20:03] maas 1.7.3+bzr3363-0ubuntu1~trusty1 [20:04] weird [20:04] ah [20:04] I see what you are saying [20:04] smoser, and what is the raw user data for that? [20:05] same [20:05] you can see it. [20:05] ah yes I for some reason didn't match the strings [20:06] garibaldi, drhalan: can either of you verify that the above works for you? [20:06] i.e. using http://paste.ubuntu.com/11549482/ as your user-data [20:06] which should result in the string that you see on the command-line here: http://paste.ubuntu.com/11549501/ [20:07] kiko, and then... [20:07] $ cat /run/my.log [20:07] ======================================== [20:07] ============== Wed Jun 3 20:07:02 UTC 2015 ================= [20:07] ======== Hi World ====================== [20:07] ======================================== [20:07] system came up. had that there. [20:07] yeah, I was expecting you'd say that 8) [20:08] and 'sudo cat /var/lib/cloud/instance/user-data.txt' [20:08] will show you the input user-data [20:10] so, tats about all i can easily do at the moment. but it does show user-data functioning via maas-cli [20:10] with maas at 1.7.3 === cgseller_is_away is now known as imthewherd [21:02] I am using VM to test maas. What size must be my hdd to be able to import the boot image ? [21:13] smoser: can you send me the exact maas cli command you used? [21:13] just to make sure I reproduce exactly [23:01] Bug #1461712 was opened: 1.8rc1: sm15k systems - non-PXE NIC's mac address doesn't get linked back to cluster [23:55] garibaldi, its in that pastebin [23:55] http://paste.ubuntu.com/11549450/ [23:56] maas smoser nodes acquire [23:56] 'smoser' is the maas name (first argument to maas) [23:56] acquire returned the node with system-id node-86787e7e-cd78-11e4-8df8-001b21006d7f [23:57] then maas smoser node start node-86787e7e-cd78-11e4-8df8-001b21006d7f user_data=IyEvYmluL3NoCgooCmVjaG8gPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQplY2hvID09PT09PT09PT09PT09ICQoZGF0ZSkgPT09PT09PT09PT09PT09PT0KZWNobyA9PT09PT09PSBIaSBXb3JsZCA9PT09PT09PT09PT09PT09PT09PT09CmVjaG8gPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQopIHwgdGVlIC9ydW4vbXkubG9nCg== distro_series=trusty