[04:55] <mup> 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 <apport-package> <i386> <vivid> <maas (Ubuntu):New> <https://launchpad.net/bugs/1460515>
[04:58] <mup> 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 <apport-package> <i386> <vivid> <maas (Ubuntu):New> <https://launchpad.net/bugs/1460515>
[05:01] <mup> 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 <apport-package> <i386> <vivid> <maas (Ubuntu):New> <https://launchpad.net/bugs/1460515>
[11:14] <mup> Bug #1460614 was opened: FQDN column heading underline space <MAAS:New> <https://launchpad.net/bugs/1460614>
[12:18] <voidspace> so I have a failed deployment - maas.log says:
[12:18] <voidspace> Marking node failed: Installation failed (refer to the installation log for more information).
[12:19] <voidspace> Which installation log is that - on the node?  (and where specifically)
[12:44] <mup> Bug #1460643 was opened: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 <api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1460643>
[12:50] <mup> Bug #1460643 changed: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 <api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1460643>
[13:02] <mup> Bug #1460643 was opened: [1.8] PhysicalBlockDevice endpoint is incorrect for 1.9 <api> <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1460643>
[14:42] <voidspace> so I have a failed deployment - maas.log says:
[14:43] <voidspace> Marking node failed: Installation failed (refer to the installation log for more information).
[14:43] <voidspace> Which installation log is that - on the node?  (and where specifically)
[14:43] <voidspace> allenap: know anyone who can help me with this? ^^^
[14:46] <allenap> voidspace: I'll find someone who knows what they're doing :)
[14:47] <rvba> voidspace: on the node details page.
[14:47] <rvba> voidspace: or using the API http://maas.ubuntu.com/docs/api.html#commissioning-results
[14:49] <voidspace> rvba: thanks the machine details page doesn't give any more information
[14:49] <voidspace> in fact it gives less information
[14:49] <rvba> voidspace: which version of MAAS is this?
[14:50] <mup> Bug #1460678 was opened: MAAS writes logs to maas.log.1 <MAAS:New> <https://launchpad.net/bugs/1460678>
[14:50] <voidspace> rvba: 1.8 from dailybuilds
[14:51] <voidspace> rvba: this is from the machine details page
[14:51] <voidspace> http://pastebin.ubuntu.com/11498415/
[14:51] <voidspace> ah wait
[14:51] <voidspace> I didn't scroll down far enough it seems...
[14:51] <roaksoax> voidspace: go sall the way to the bottom
[14:51] <voidspace> modprobe: FATAL: Module hpvsa not found.
[14:51] <voidspace> Installation failed with exception: Unexpected error while running command.
[14:51] <voidspace> Command: ['sh', '-c', 'depmod && modprobe hpvsa']
[14:52] <rvba> voidspace: at the bottom of the page you should have the install log
[14:52] <voidspace> thanks
[14:53] <voidspace> this is the full log: http://pastebin.ubuntu.com/11498446/
[14:55] <voidspace> so I will disable proprietary drivers and try again
[15:03] <voidspace> rvba: with propietary drivers disabled it's working
[15:03] <voidspace> rvba: want me to file an issue?
[15:05] <mup> Bug #1460199 changed: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. <MAAS:Incomplete> <https://launchpad.net/bugs/1460199>
[15:07] <rvba> voidspace: please
[15:17] <mup> Bug #1460199 was opened: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. <MAAS:Incomplete> <https://launchpad.net/bugs/1460199>
[15:20] <mup> Bug #1460199 changed: NoConnectionsAvailable: Unable to connect to cluster 3e375000-9ece-453c-9b5e-f817ab3a51b2; no connections available. <MAAS:Incomplete> <https://launchpad.net/bugs/1460199>
[15:46] <garibaldi> 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] <garibaldi> how can this be done?
[15:53] <mup> Bug #1460128 changed: whitespace above header keeps growing on click for chromium <ui> <MAAS:Won't Fix by ricgard> <https://launchpad.net/bugs/1460128>
[15:56] <rbasak> garibaldi: I'm pretty sure you can add custom commissioning scripts. Would that do?
[15:57] <garibaldi> that would work... all I need to do is modify the contents of a file after the server has been provisioned
[15:57] <garibaldi> how can I add a custom commissioning script
[15:57] <garibaldi> ?
[16:05] <mup> Bug #1460714 was opened: WebUI does not support soft power off <MAAS:New> <https://launchpad.net/bugs/1460714>
[16:06] <rbasak> Well, commissioning is before a server is provisioned.
[16:06] <kiko> rbasak, shouldn't he use cloud-init for that?
[16:06] <kiko> garibaldi, can you tell us a bit more about what you are trying to do?
[16:17] <mup> Bug #1460714 changed: WebUI does not support soft power off <MAAS:New> <https://launchpad.net/bugs/1460714>
[16:23] <mup> Bug #1460714 was opened: WebUI does not support soft power off <MAAS:New> <https://launchpad.net/bugs/1460714>
[17:41] <mup> Bug #1317601 changed: [SRU] SRU New upstream bugfix release of MAAS <verification-done> <maas (Ubuntu):Fix Released> <maas (Ubuntu Trusty):Fix Released> <https://launchpad.net/bugs/1317601>
[18:45] <mup> Bug #1329267 was opened: CLI does not tell users to issue a "refresh" when the API gets out of date <cli> <upgrade> <MAAS:Fix Committed by allenap> <MAAS 1.7:Fix Committed by allenap> <maas (Ubuntu):New> <https://launchpad.net/bugs/1329267>
[18:45] <mup> Bug #1387859 was opened:  When MAAS has too many leases, and lease parsing fails, MAAS fails to auto-map NIC with network <MAAS:Fix Committed by julian-edwards> <MAAS 1.7:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1387859>
[18:45] <mup> Bug #1456969 was opened: MAAS cli/API: missing option set use-fast-installer / use-debian-installer <api> <canonical-bootstack> <MAAS:Fix Committed by rvb> <MAAS 1.7:In Progress by rvb> <maas (Ubuntu):New> <https://launchpad.net/bugs/1456969>
[18:45] <roaksoax> Good signature on ../maas_1.7.5+bzr3369-0ubuntu1~14.04.1.dsc.
[19:30] <garibaldi> 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] <garibaldi> kiko: so I want to modify the /root/.ssh/authorized_keys file to allow root ssh access
[19:31] <garibaldi> 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] <kiko> smoser, do you have advice for this? or jhobbs?
[19:34] <kiko> oh, jhobbs ain't here
[19:34] <smoser> garibaldi, provide user-data when you deploy nodes.
[19:34] <smoser> #cloud-config
[19:35] <smoser> disable_root: false
[19:35] <smoser> or just learn how to use sudo :)
[19:36] <smoser> maas's cli for 'node start' takes a user_data key
[19:36] <smoser> that is a base64 endoded file. that becomes cloud-init's user-data
[19:40] <garibaldi> smoser: thanks for the help; I am using Ansible to deploy my nodes
[19:41] <garibaldi> 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] <kiko> I see
[19:43] <smoser> 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] <smoser> i suspect that if ansible has support for launching ubuntu images elsewhere, that this is not a new problem
[20:00] <kiko> garibaldi, sounds easy!
[20:10] <garibaldi> smoser, kiko: how do I provide user data?
 maas's cli for 'node start' takes a user_data key
[20:10] <kiko> garibaldi, ^^
[20:10] <garibaldi> how do I instruct MAAS to pass it to the nodes?
[20:11] <kiko> use the maas cli as smoser suggests above
[20:13] <smoser> garibaldi, cli/api . you pass 'user_data' key in.
[20:13] <smoser> maas $MYMAASNAME node start system_id user_data=$(base64 my-user-data) distro_series=trusty
[20:14] <smoser> 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] <kiko> smoser, this is missing from the cli docs on m.u.c it seems?
[20:14] <garibaldi> smoser: the user_data string could contain a bash command, or the contents of a bash script?
[20:15] <smoser> garibaldi, https://help.ubuntu.com/community/CloudInit covers user-data
[20:15] <smoser> kiko, i dont know if its documented, i dont know how i found it :). i know it does work.
[20:16] <garibaldi> smoser: e.g maas $MYMAASNAME node start system_id user_data=$(base64 $(cat /tmp/script.sh)) distro_series=trusty
[20:19] <smoser> garibaldi, mine didnt work ?
[20:19] <smoser> i dont think you want or need 'cat' there
[20:19] <smoser> ah. sorry.. .here.
[20:19] <garibaldi> or is it --user-data-file
[20:19] <smoser> for maas it is:
[20:20] <smoser>  maas MAASNAME node start SYSTEM_ID distro_series=RELEASE user_data=$(base64 --wrap=0 YOUR_USERDATA_FILE)
[20:21] <smoser> MAASNAME: as seen in
[20:21] <smoser> MAASNAME: as seen in maas list
[20:21] <smoser> SYSTEM_ID: the system_id from maas MAASNAME nodes list
[20:21] <smoser> RELEASE: trusty, vivid, wily ...
[20:22] <smoser> YOUR_USERDATA_FILE: whatever you want as described in https://help.ubuntu.com/community/CloudInit
[20:28] <garibaldi> can I pass a userdata file via the Web UI as well?
[20:28] <garibaldi> when commissioning nodes via the Web UI?
[20:42] <garibaldi> smoser: I have 4 nodes commissioned in the Web UI, however after running "maas login local http://<my-mass-hostname>/MAAS/api/1.0 <key>", I only see the key data when I do "maas list"
[20:42] <garibaldi> smoser: I do not see any nodes listed, nor MAASNAME or SYSTEM_ID items
[20:57] <mup> Bug #1460816 was opened: MAAS doesn't power cycle systems after not seeing a PXE request <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1460816>
[21:26] <kiko> garibaldi, I don't know whether you can pass userdata via the web UI, I think not
[21:26] <kiko> garibaldi, sounds like you don't have the cli working, oddly
[21:27] <kiko> garibaldi, before you annoy yourself further, I wonder, could you upgrade to 1.7 as per the topic?