[04:55] Bug #1460515 was opened: package maas-region-controller 1.7.3+bzr3363-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 [04:58] Bug #1460515 changed: package maas-region-controller 1.7.3+bzr3363-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 [05:01] Bug #1460515 was opened: package maas-region-controller 1.7.3+bzr3363-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 === zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_CyberJacob [11:14] Bug #1460614 was opened: FQDN column heading underline space [12:18] so I have a failed deployment - maas.log says: [12:18] Marking node failed: Installation failed (refer to the installation log for more information). [12:19] Which installation log is that - on the node? (and where specifically) [12:44] Bug #1460643 was opened: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 [12:50] Bug #1460643 changed: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 [13:02] Bug #1460643 was opened: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 [14:42] so I have a failed deployment - maas.log says: [14:43] Marking node failed: Installation failed (refer to the installation log for more information). [14:43] Which installation log is that - on the node? (and where specifically) [14:43] allenap: know anyone who can help me with this? ^^^ [14:46] voidspace: I'll find someone who knows what they're doing :) [14:47] voidspace: on the node details page. [14:47] voidspace: or using the API http://maas.ubuntu.com/docs/api.html#commissioning-results [14:49] rvba: thanks the machine details page doesn't give any more information [14:49] in fact it gives less information [14:49] voidspace: which version of MAAS is this? [14:50] Bug #1460678 was opened: MAAS writes logs to maas.log.1 [14:50] rvba: 1.8 from dailybuilds [14:51] rvba: this is from the machine details page [14:51] http://pastebin.ubuntu.com/11498415/ [14:51] ah wait [14:51] I didn't scroll down far enough it seems... [14:51] voidspace: go sall the way to the bottom [14:51] modprobe: FATAL: Module hpvsa not found. [14:51] Installation failed with exception: Unexpected error while running command. [14:51] Command: ['sh', '-c', 'depmod && modprobe hpvsa'] [14:52] voidspace: at the bottom of the page you should have the install log [14:52] thanks [14:53] this is the full log: http://pastebin.ubuntu.com/11498446/ [14:55] so I will disable proprietary drivers and try again [15:03] rvba: with propietary drivers disabled it's working [15:03] rvba: want me to file an issue? [15:05] Bug #1460199 changed: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. [15:07] voidspace: please [15:17] Bug #1460199 was opened: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. [15:20] Bug #1460199 changed: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. [15:46] Hello - I set up MAAS 1.6 on Ubuntu 14.04 and it works well, but I cannot figure out how to run a script on the node after commissioning [15:46] how can this be done? [15:53] Bug #1460128 changed: whitespace above header keeps growing on click for chromium [15:56] garibaldi: I'm pretty sure you can add custom commissioning scripts. Would that do? [15:57] that would work... all I need to do is modify the contents of a file after the server has been provisioned [15:57] how can I add a custom commissioning script [15:57] ? [16:05] Bug #1460714 was opened: WebUI does not support soft power off [16:06] Well, commissioning is before a server is provisioned. [16:06] rbasak, shouldn't he use cloud-init for that? [16:06] garibaldi, can you tell us a bit more about what you are trying to do? [16:17] Bug #1460714 changed: WebUI does not support soft power off [16:23] Bug #1460714 was opened: WebUI does not support soft power off [17:41] Bug #1317601 changed: [SRU] SRU New upstream bugfix release of MAAS === zz_CyberJacob is now known as CyberJacob [18:45] Bug #1329267 was opened: CLI does not tell users to issue a "refresh" when the API gets out of date [18:45] Bug #1387859 was opened: When MAAS has too many leases, and lease parsing fails, MAAS fails to auto-map NIC with network [18:45] Bug #1456969 was opened: MAAS cli/API: missing option set use-fast-installer / use-debian-installer

[18:45] Good signature on ../maas_1.7.5+bzr3369-0ubuntu1~14.04.1.dsc. [19:30] kiko: I want to be able to ssh to the node as root, but the default /root/.ssh/authorized_keys file contains a command that echos out a string and then closes the connection [19:30] kiko: so I want to modify the /root/.ssh/authorized_keys file to allow root ssh access [19:31] kiko: I see also that there is "disable_root" in /etc/cloud/cloud.cfg, but I don't know how to set this from MAAS so that it gets propagated to the node [19:33] smoser, do you have advice for this? or jhobbs? [19:34] oh, jhobbs ain't here [19:34] garibaldi, provide user-data when you deploy nodes. [19:34] #cloud-config [19:35] disable_root: false [19:35] or just learn how to use sudo :) [19:36] maas's cli for 'node start' takes a user_data key [19:36] that is a base64 endoded file. that becomes cloud-init's user-data [19:40] smoser: thanks for the help; I am using Ansible to deploy my nodes [19:41] smoser: and my Ansible setup connects to the nodes as root, so I need to be able to directly connect to root with an SSH key, not using sudo [19:41] I see [19:43] you'll need to provide user-data.that user-data will function for you anywhere (ec2, azure ... where you see an ubuntu cloud image) [19:43] i suspect that if ansible has support for launching ubuntu images elsewhere, that this is not a new problem [20:00] garibaldi, sounds easy! [20:10] smoser, kiko: how do I provide user data? [20:10] maas's cli for 'node start' takes a user_data key [20:10] garibaldi, ^^ [20:10] how do I instruct MAAS to pass it to the nodes? [20:11] use the maas cli as smoser suggests above [20:13] garibaldi, cli/api . you pass 'user_data' key in. [20:13] maas $MYMAASNAME node start system_id user_data=$(base64 my-user-data) distro_series=trusty [20:14] http://bazaar.launchpad.net/~virtual-maasers/+junk/maas-libvirt-utils/view/head:/maas-deploy-node is a wrapper i use lots of places "maas-deploy-node". [20:14] smoser, this is missing from the cli docs on m.u.c it seems? [20:14] smoser: the user_data string could contain a bash command, or the contents of a bash script? [20:15] garibaldi, https://help.ubuntu.com/community/CloudInit covers user-data [20:15] kiko, i dont know if its documented, i dont know how i found it :). i know it does work. [20:16] smoser: e.g maas $MYMAASNAME node start system_id user_data=$(base64 $(cat /tmp/script.sh)) distro_series=trusty [20:19] garibaldi, mine didnt work ? [20:19] i dont think you want or need 'cat' there [20:19] ah. sorry.. .here. [20:19] or is it --user-data-file [20:19] for maas it is: [20:20] maas MAASNAME node start SYSTEM_ID distro_series=RELEASE user_data=$(base64 --wrap=0 YOUR_USERDATA_FILE) [20:21] MAASNAME: as seen in [20:21] MAASNAME: as seen in maas list [20:21] SYSTEM_ID: the system_id from maas MAASNAME nodes list [20:21] RELEASE: trusty, vivid, wily ... [20:22] YOUR_USERDATA_FILE: whatever you want as described in https://help.ubuntu.com/community/CloudInit [20:28] can I pass a userdata file via the Web UI as well? [20:28] when commissioning nodes via the Web UI? [20:42] smoser: I have 4 nodes commissioned in the Web UI, however after running "maas login local http:///MAAS/api/1.0 ", I only see the key data when I do "maas list" [20:42] smoser: I do not see any nodes listed, nor MAASNAME or SYSTEM_ID items [20:57] Bug #1460816 was opened: MAAS doesn't power cycle systems after not seeing a PXE request [21:26] garibaldi, I don't know whether you can pass userdata via the web UI, I think not [21:26] garibaldi, sounds like you don't have the cli working, oddly [21:27] garibaldi, before you annoy yourself further, I wonder, could you upgrade to 1.7 as per the topic? === jfarschman is now known as MilesDenver === jfarschman is now known as MilesDenver === CyberJacob is now known as zz_CyberJacob