[02:13] <shewless> anyone still around?
[02:13] <shewless> for some reason I can't get the DNS forwarder to work in maas.
[02:14] <shewless> I have it working on my old maas server but the new one just doesn't seem to want to forward .. not sure how to debug
[02:21] <shewless> figured it out.. /var/log/syslog was spewing "bind broken trust chain resolving"
[02:21] <shewless> fixed it
[04:17] <sujeet_> Hi kiko
[04:18] <sujeet_> kiko: where can i get the document of uploading the commission script on MAAS 2.0?
[07:34] <sujeet_> Hi
[07:35] <sujeet_> where can i get the document of uploading the commission script on MAAS 2.0?
[07:37] <roaksoax> sujeet_: API docs: http://maas.ubuntu.com/docs2.0/api.html#commissioning-script
[07:38] <sujeet_> i mean , where can i get the document for writing commission script and its step
[07:39] <roaksoax> sujeet_: there's no document. it is just a script
[07:39] <roaksoax> sujeet_: it it, literally, any script that you can run on a system with root priviliges
[07:39] <sujeet_> we need to upload the script and then commission it?
[07:41] <sujeet_> if we upload one script, and want to delete that script then?
[07:42] <roaksoax> sujeet_: the commissioning scripts are run in commissioning
[07:42] <roaksoax> so yes, you upload an script
[07:42] <roaksoax> you commissioning your machine
[07:42] <roaksoax> the script will run
[07:42] <sujeet_> if we want to delete script then?
[07:42] <roaksoax> and you can delete your script later if you dont want any subsequent commissioning to run your script
[07:43] <roaksoax> sujeet_: see the Settings page, under the commissioning scripts section
[07:43] <roaksoax> if you upload one, it will be used
[07:43] <roaksoax> and you can remove it
[07:43] <sujeet_> i dont see remove option in it
[07:44] <sujeet_> there is only one button to "upload script" and i cant find delete
[07:53] <roaksoax> sujeet_: there's an X icon on the right side
[07:53] <roaksoax> sujeet_: where you can delete it
[07:54] <sujeet_> MAAS2.0?
[07:55] <roaksoax> sujeet_: yup
[07:55] <roaksoax> sujeet_: i just did it here
[07:56] <roaksoax> in chorme
[07:56] <roaksoax> chrome browser
[08:00] <sujeet_> i can't see that option
[08:01] <sujeet_> i checked in IE, Firefox and chrome
[08:02] <sujeet_> the script is getting overlapped with other sections
[08:03] <mup> Bug #1617195 opened: Cannot collapse commissioning script <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1617195>
[08:03] <sujeet_> roaksoax : is there any other way to delete the script?
[08:04] <roaksoax> sujeet_: via the API
[08:04] <roaksoax> sujeet_: yeah I just filed a bug for the overlapping
[08:04] <roaksoax> sujeet_: but click on the title of the script
[08:04] <roaksoax> sujeet_: it will "expand" and stop the overlapping
[08:05] <sujeet_> yes i know that, but delete "X" option i cant see
[08:06] <sujeet_> i saw your screenshot and i can see "X" option on it, but in my setup i cant see it
[08:14] <sujeet_> using API i am getting "The requested URL /MAAS/DELETE /api/2.0/commissioning-scripts/abc.sh was not found on this server."
[08:27] <sujeet_> roaksoax: i think i got the "x" icon where it was hidden behind the <pre> tag after reducing the width i got it
[08:46] <neith> Hello, I'm deploying maas and I'm facing an issue, I'm booting an enlinsting node via PXE. Everything works fine until it runs the cloud init script called modules:final at this point the node brutally shuts down
[08:46] <neith> How I can retreive the log to analyze whats going on?
[08:47] <neith> If I try to reboot the same node it fails at PXE. I have to delete it from maas ans try angin
[09:08] <neith> ok well It just send a power down
[09:09] <neith> seems normal
[09:09] <neith> but the next reboot is failing at pxe boot
[09:15] <neith> http://imgur.com/a/ech4F
[09:29] <sujeet_> roaksoax : How to upload two or more script files which is dependent on each other? For instance call the python file from shell script
[09:54] <roaksoax> sujeet_: we dont support dependency like that, but typucally, if you name them like 01_xyz, 02_xyz it should do the right thing
[09:55] <roaksoax> neith: enlistment processes registers the machine into MAAS and it then shutdowns
[09:55] <roaksoax> neith: after the enlistment, do you see your machines registered in MAAS ?
[09:55] <sujeet_> yes
[09:56] <sujeet_> added simple sh with echo, i am able to see the prints
[09:58] <sujeet_> for instacne i have sample sh file in which it execute the python file(or call python class or function) can i do like this by using 01_xyz.sh, 02_abc.py?
[09:59] <roaksoax> sujeet_: if the sh file executes the python one, try 01_xyz.py 02_ab.py
[09:59] <roaksoax> sujeet_: if the sh file executes the python one, try 01_xyz.py 02_ab.sh
[09:59] <roaksoax> i think that would render the python script before the shell
[10:02] <sujeet_> ok
[10:50] <neith> roaksoax: It is enlisted, but boot fails
[10:50] <neith> roaksoax: I found a workaround by forcing the use of xenial kernel for commisionning
[10:51] <neith> using Trusty always displays file not found
[11:18] <neith> roaksoax: The weird thing is that I switched back to Trusty kernel and now it works
[11:18] <neith> I really dont't get it
[11:43] <roaksoax> neith: strange
[11:43] <roaksoax> neith: if you can get console logs
[11:43] <roaksoax> that'd be great
[11:43] <neith> roaksoax: I'm struggling extracting console logs from iLo remote console
[12:10] <sujeet_> Hi roaksoax
[12:13] <sujeet_> i added the print("Hello") in python file and uploaded the script and tried to commission, in Commissioning Output i get the following error "Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE (.*?)}/ at /usr/bin/print line 528. Error: no such file "Hello""
[12:19] <roaksoax> sujeet_: if you can pastebin your scripts i can give it a try locally
[12:22] <sujeet_> And for adding our storage raid controller on MAAS gui, what need to be done?
[12:26] <roaksoax> sujeet_: what is your storage raid controoller ?
[12:29] <sujeet_> using our controller we can create volumes, secure erase, firmware upgrade, and so on
[12:31] <roaksoax> sujeet_: right, but what do you mean by adding your storage raid controller to MAAS gui ?
[12:33] <kiko> roaksoax, he's talking about an actual UI feature to support hardware raid controllers
[12:36] <sujeet_> we need to add the controller storage section below the "Used disks and partitions" with button like "Create volume", "Secure Erase"
[12:37] <sujeet_> yes kiko is right
[12:38] <sujeet_> during commissioning python script i get the following error "/tmp/user_data.sh.UdvSZP/commissioning.d/02_xyz.py: 1: /tmp/user_data.sh.UdvSZP/commissioning.d/02_xyz.py: name: not found"
[12:41] <kiko> sujeet_, put your script in a pastebin please so we can look at it
[12:42] <kiko> roaksoax, for the moment, I've advised him to just do this as a commissioning script
[12:42] <sujeet_> ok
[12:43] <sujeet_> Its just a simple script like
[12:43] <sujeet_> print("Hello")
[12:45] <sujeet_> in xyz.py file i wrote print("hello") thats it
[12:51] <kiko> sujeet_, can you put it in a pastebin?
[12:52] <sujeet_> i didnt get pastebin
[12:52] <kiko> sujeet_, paste.ubuntu.com
[12:53] <sujeet_> i did did you get it?
[12:54] <kiko> sujeet_, you need to give me the resulting URL
[12:54] <sujeet_> http://paste.ubuntu.com/23093114/
[12:55] <kiko> sujeet_, I don't think python is available in the commissioning environment unless you install it
[12:55] <kiko> sujeet_, if it is available, then you probably need to put a #!/usr/bin/python at the beginning of the file?
[12:55] <sujeet_> ok
[12:58] <sujeet_> python should be install where maas is installed?
[12:59] <sujeet_> i am able to execute on putty
[13:01] <kiko> sujeet_, sure, apt-get install python-minimal
[13:02] <kiko> or just use shell script, i.e. 02_xyz.sh?
[13:03] <sujeet_> ok
[13:08] <roaksoax> sujeet_: /win 4
[13:08] <roaksoax> err
[13:09] <sujeet_> we need to save in unix file format?
[13:10] <sujeet_> currently its in windows file format
[13:17] <sujeet_> i have the client which is written in python ,so i need to use python file to get the data, if i use shell script, then i need to rewrite the code
[13:17] <roaksoax> sujeet_: the commissioning process happens in linux
[13:17] <roaksoax> sujeet_: so if yout script is a windows python script
[13:17] <roaksoax> then you may need to do some porting
[13:18] <sujeet_> ok
[13:27] <sujeet_> so i created python file on ubuntu with same statement, this can work?
[13:37] <sujeet_> i written mock.py on putty and uploaded it but i got "/var/lib/cloud/instance/scripts/user_data.sh: 177: /var/lib/cloud/instance/scripts/user_data.sh: /tmp/user_data.sh.RLbmqr/commissioning.d/mock.py: not found"
[13:41] <roaksoax> sujeet_: http://paste.ubuntu.com/23093247/
[13:41] <roaksoax> sujeet_: i created that script
[13:41] <roaksoax> sujeet_: and uploaded it to maas
[13:41] <roaksoax> and it just worked
[13:41] <sujeet_> can you send that script?
[13:41] <roaksoax> "script.py.outFri, 26 Aug. 2016 21:38:101 lines"
[13:42] <roaksoax> sujeet_: copy paste the contents of that pastebin into a file like "test.py"
[13:42] <roaksoax> sujeet_: upload test.py as a commissioning script in the settings page
[13:42] <roaksoax> sujeet_: and commission your machine
[13:43] <sujeet_> ok, can you send that script ?
[13:43] <kiko> sujeet_, it's in the pastebin URL roaksoax gave you earlier
[13:44] <roaksoax> sujeet_: the script is here : http://paste.ubuntu.com/23093247/
[13:45] <sujeet_> ok
[13:56] <sujeet_> Hi rasksoax and kiko, you guys are awesome, thanks it worked
[13:56] <kiko> sujeet_, woot
[13:56] <kiko> sujeet_, you really need to get off Windows now.. I'll give you a free Ubuntu license :)
[13:57] <sujeet_> sure
[13:57] <sujeet_> and i need the overview of what need to be done for adding the Raid controller section on MAAS gui?
[14:05] <kiko> sujeet_, that's much more complex, and requires some design input. I suggest for the moment getting the controller management done via scripts, possibly by driving the API
[14:10] <sujeet_> but this stuff can only be seen in commission output
[14:12] <sujeet_> can you guys help in that or it follow different procedure to develop?
[14:27] <neith> Do you know how long is bootstrapping juu in the openstack install?
[14:27] <neith> i'm at 1200sec
[14:27] <neith> ans still running
[14:27] <neith> where are the logs?
[14:43] <kiko> neith, do a juju bootstrap --debug
[14:43] <kiko> that will give you output to stdout
[14:43] <neith> thks
[14:44] <neith> kiko: I have to run it on the maas node?
[14:44] <neith> or enlisted node?
[14:44] <kiko> neith, on the node issuing the juju bootstrap
[14:44] <kiko> neith, or are you using conjure-up or autopilot?
[14:44] <neith> autopilot
[14:45] <kiko> neith, are you able to manually deploy nodes into your maas successfully?
[14:45] <neith> kiko yes
[14:57] <kiko> neith, all of the nodes?
[14:57] <kiko> neith, is there any proxy in the way?
[14:57] <neith> kiko: yes all nodes and no proxy
[14:58] <kiko> neith, it's odd that a bootstrap would take very long, tbh
[14:58] <kiko> neith, can you test a bootstrap independently?
[14:58] <neith> kiko: yes how?
[14:59] <kiko> neith, apt-get install juju-core, set up the maas provider and juju bootstrap --debug
[14:59] <kiko> observing the correct version as MAAS 2 only works with Juju 2
[14:59] <kiko> check out jujucharms.com for the low-down
[14:59] <kiko> need to go otp for a bit but keep asking
[15:00] <neith> I'll try
[15:07] <neith> kiko: I assume I have to run these commands from the commisionned node?
[15:08] <kiko> neith, from any node that can talk to MAAS
[15:08] <kiko> neith, including a node deployed by MAAS itself
[15:35] <prav> I am unable to login to ubuntu cloud-init image using the ssh keys that I created. Am I doing something wrong?
[15:40] <kiko> prav, probably. MAAS 2.0 final?
[15:50] <prav> yea...MAAS Version 2.0.0 (rc2+bzr5156)
[15:51] <kiko> prav, and you put your SSH key into your account, deploy a node, and can't SSH ubuntu@node into it?
[15:51] <prav> correct..
[15:51] <kiko> prav, something's wrong with your key? or operator error?
[15:51] <kiko> I mean, that absolutely works!
[15:53] <prav> can I login from any box or only from the maas server?
[15:55] <kiko> prav, from any box where the private key is right? I mean.. it's ssh right
[15:55] <prav> right
[15:56] <kiko> ssh -v will tell you more
[15:56] <prav> let me create another user and keygen once again
[15:59] <prav> kiko, do you work for Canonical?
[16:00] <prav> how can I get support for maas?
[16:00] <kiko> prav, yes, I'm the product owner, and absolutely yes
[16:04] <prav> we want to use maas for bare metal deployments, but our infra is mostly Centos. Does support work for such deployments?
[16:04] <kiko> yes
[16:04] <kiko> prav, it works for centos, windows, rhel, sles
[16:04] <kiko> prav, I just privmsgd you with contact info
[16:05] <prav> cool
[16:15] <x58> What would cause bugs that used to be public (for over a year) to suddenly be set to Proprietary?
[16:15] <x58> Specifically these are bugs that I have reported...
[16:16] <x58> (Also, logging in to Ubuntu One to login to Launchpad doesn't work on iOS Safari)
[16:17] <x58> Specifically, this is related to maas-image-builder
[16:20] <kiko> prav, what does your ssh -v look like?
[16:30] <prav> Initially it was giving me public key denied..after I assingned the nodes static IP, it says no route to host.. even though the gateway is the same
[16:30] <roaksoax> x58: do you have links  to these bugs ?
[16:31] <roaksoax> x58: maas-image-builder used to be available for centos image generation, and now it is not anymore, as we provide centos images, and maas-image-builder does no longer provide that support to create centos images
[16:32] <x58> roaksoax: Sure, bug ID: 149518 and 1477704
[16:32] <x58> roaksoax: That's fine, I had bzr branches though, it used to be open source. I submitted patches because it was open soruce.
[16:32] <x58> roaksoax: My bzr branches are now missing, my code that I submitted is now no longer available, nor are my bug reports (even to me).
[16:33] <x58> 1479518
[16:34] <kiko> prav, you no longer can ping?
[16:35] <roaksoax> x58: try now ?
[16:36] <x58> roaksoax: No permission.
[16:36] <x58> https://bugs.launchpad.net/maas-image-builder/+bug/1479518 (not allowed here)
[16:38] <x58> Still can't access my branches in bzr either.
[16:39] <roaksoax> x58: let me dig into it
[16:39] <x58> roaksoax: ok.
[16:41] <mup> Bug #1617082 opened: Curtin not able to write MAAS official images that are inserted as "Custom" images <hwcert-server> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1617082>
[16:41] <roaksoax> x58: try now ?
[16:42] <x58> Still no go on both.
[16:42] <x58> roaksoax: ^
[16:42] <x58> I've gotta run to a meeting. Will be back later.
[16:45] <roaksoax> x58: strange, it is telling me that your branches and bugs are public "This branch contains Public information Edit
[16:45] <roaksoax> Everyone can see this information."
[16:46] <x58> https://code.launchpad.net/%7Ebertjwregeer/maas-image-builder/update-centos-7/ fails hard.
[16:47] <x58> https://bugs.launchpad.net/maas-image-builder/+bug/1477704 (The information on this page is private._
[16:50] <roaksoax> x58: now ?
[16:52] <prav> nope. I cant ping.. but when I change it to DHCP, it gets another IP in the same subnet , but it starts pinging
[16:52] <kiko> prav, looks like deployment is failing with a static IP?
[16:52] <kiko> you cant ssh -v the dhcp IP?
[16:53] <mup> Bug #1617082 changed: Curtin not able to write MAAS official images that are inserted as "Custom" images <hwcert-server> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1617082>
[16:53] <prav> yes I can
[16:54] <kiko> prav, this is centos or ubuntu?
[16:57] <prav> ubuntu..
[17:14] <roaksoax> prav: can you upgrade to 2.0 GA ?
[17:14] <roaksoax> prav: you can find it in ppa:maas/stable