[10:07] <mup> Bug #1682374 changed: [2.2, UI, mobile] The navigation doesn't work on mobile <ui> <ux-qa-2.2> <MAAS:Fix Released by ricgard> <MAAS 2.2:Fix Released by ricgard> <https://launchpad.net/bugs/1682374>
[12:54] <dholt> hello, I'm all of a sudden unable to deploy 16.04 because apparmor is preventing the ntp service from starting properly; does anyone else have this issue?
[12:55] <dholt> MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1)
[12:55] <mup> Bug #1692557 changed: [2.2] Menu on mobile view does not work.  <MAAS:Fix Committed by ricgard> <https://launchpad.net/bugs/1692557>
[12:55] <mup> Bug #1701256 opened: Creating a subnet with fabric specified gets the default fabric anyway <api> <MAAS:Triaged> <https://launchpad.net/bugs/1701256>
[13:06] <Woods_> Hello world!
[13:07] <Woods_> I am interested in using MAAS with juju to build a private cloud. Has anyone done this (I am guessing so). Can anyone provide links (how to page)?
[13:24] <Woods_> Would this work? https://linux.dell.com/files/whitepapers/Deploying_Workloads_With_Juju_And_MAAS-14.04LTS-Edition.pdf
[14:40] <gimmic> In 2.2, during commissioning I am getting an error in IPMI power cycle, even though maas can power the node on/off
[15:00] <gimmic> might be an ipmi backoff issue ala: https://bugs.launchpad.net/maas/+bug/1609496
[15:08] <gimmic> http://i.imgur.com/3XsqrlP.png
[15:09] <gimmic> does-not-compute
[15:09] <roaksoax_> gimmic: that seems like a BMC issue
[15:09] <gimmic> Right, didn't have this issue in 1.9, now seeing it in 2.2
[15:09] <roaksoax_> gimmic: that's because 1.9 vs 2.2 do different things when it comes to power management
[15:09] <roaksoax_> gimmic: and maas 2.2 checks things differently, which is tripping the issue in the BMC
[15:10] <gimmic> a timeout doesn't make sense as the ipmi interfaces are static allocated
[15:10] <gimmic> same switched environment as the data
[15:24] <gimmic> interesting.. the bmc stops pinging when comissioning starts, unless that's just maas powering it off/on
[15:31] <gimmic> very curious.. I lose ping while the drac is power state changing, for a long time
[15:49] <roaksoax_> gimmic: are you using the latest version of the firmware ?
[15:49] <gimmic> doubtful.
[16:50] <ghost12345> Hello. Can someone help me with MAAS on ubuntu 16.04 ? I have created question https://askubuntu.com/questions/930023/how-to-add-custom-power-type-to-maas-2-1-x-to-use-pc-power-control-using-raspber
[16:51] <ghost12345> There was old tutorial about how to add custom power type to maas 1.5.x
[16:51] <ghost12345> but maas 2.1 does not have power templates, and also I can't find provisioning server plugin
[16:59] <mup> Bug #1701322 opened: Installing maas on a xenial VM fails. <MAAS:New> <https://launchpad.net/bugs/1701322>
[16:59] <roaksoax_> ghost12345: this could give you an idea: https://stgraber.org/2017/04/02/using-wake-on-lan-with-maas-2-x/
[17:03] <ghost12345> роаксоах_ thanks for article, but looks like provisioning server plugin was deprecated
[17:04] <ghost12345> rlak
[17:04] <ghost12345> roaksoax_ can I use deprecated plugin with maas 2.1.5 or it will conflict ?
[17:13] <roaksoax_> ghost12345: you would need to add your own plugin, the blog post shows what he did to add his
[17:38] <ghost12345> roaksoax_ he modified source code of maas, its to complicated, i will try to install old 14.04 version :(
[17:49] <mskalka_> hey everyone. Is there a way to specify which hardware tests are run during commissioning through the CLI? I can see where the tests are defined, but that's it
[17:58] <ltrager> mskalka: You can use the commissioning_scripts argument and specify scripts by name or tag, comma separated
[17:58] <ltrager> mskalka: However the builtin scripts must always run, you can only select which custom scripts are run
[17:59] <roaksoax_> ltrager: example ?
[17:59] <ltrager> roaksaox: maas <profile> machine commission <system_id> commissioning_scripts=<script1>,<script2>
[18:00] <mskalka> ltrager, that's for commissioning, I'm talking about the 2.2 specific hardware tests which should be post commissioning if I understand correctly
[18:00] <ltrager> mskalka: ^
[18:00] <mskalka> ltrager, as in "ntp" or "stress-ng-cpu-short"
[18:00] <ltrager> mskalka: ah for hardware tests we have the testing_scripts option
[18:00] <ltrager> mskalka: maas <profile> machine commission <system_id> testing_scripts=ntp,stress-ng-cpu-short
[18:01] <ltrager> mskalka: You can pass none to disable testing
[18:01] <mskalka> ltrager, d'oh, missed that reading the parameters. Thank you!
[18:01] <ltrager> mskalka: np
[18:02] <mup> Bug #1701322 changed: Installing maas on a xenial VM fails. <MAAS:Invalid> <https://launchpad.net/bugs/1701322>
[18:02] <mskalka> ltrager, final question, is there a way to configure the defaults for that field?
[18:03] <mskalka> say I always want to pass ntp
[18:04] <ltrager> mskalka: Any testing script which is tagged with 'commissioning' runs by default at commissioning time
[18:05] <ltrager> mskalka: By default only smartctl-validate is tagged commissioning since its the only test we have that runs quickly in all environments
[18:05] <mskalka> ltrager, that's perfect, thank you
[18:05] <ltrager> mskalka: maas <profile> node-script add-tag ntp tag=commissioning
[18:06] <jamesbenson_> has anyone upgraded from 2.1.5 to stable 2.2.0?  Is it smooth?  It was hard enough to get 2.1.5 running properly, I'm worried about the upgrade.
[18:07] <roaksoax> jamesbenson_: i have, didn't come across any issues, i have not tested again though, I'm trunning trunk now
[18:08] <jamesbenson_> roaksoax, have you implemented any of the hardware testing?  That's the main feature I'm interested in.
[18:12] <roaksoax> jamesbenson_: myself personally, no, my team has though
[18:13] <roaksoax> jamesbenson_: but I can asnwer questions
[18:13] <jamesbenson_> no real questions, just wanted to see how well it works.  We use hardware based raid, just wondering if it would detect individual drives and errors, etc.
[18:22] <roaksoax> jamesbenson_: if they are seen to the os as individual disks, yes hardware testing wuld test all those disks individually
[18:22] <roaksoax> jamesbenson_: but you could also write your own test scripts
[18:23] <jamesbenson_> Thanks roaksoax
[20:17] <jfkw> I've updated maas-2.0 to 2.1 and now 2.2. Nodes are failing deployment with: cloud-init util.py: Running module ntp (<module 'cloudinit.config.cc_ntp' from '/(...)/cc_ntp.py'>) failed
[20:22] <pmatulis> jfkw, if all you did was upgrade and something is broken please open a bug. you may be asked for logs
[20:44] <mup> Bug #1701352 opened: Curtin failure is not detected as an installation script failure <MAAS:In Progress by ltrager> <https://launchpad.net/bugs/1701352>
[20:58] <jfkw> @pmatulis: thanks, looking into filing a bug report now, after checking duplicates. There is no mention of bug reporting on https://docs.ubuntu.com/maas/2.2/en/troubleshoot-getting-help.
[20:59] <jfkw> There is an existing bug https://bugs.launchpad.net/maas/+bug/1686485 which has a  similar report, but for that user node deployments succeed, whereas mine do not.
[21:02] <pmatulis> jfkw, https://bugs.launchpad.net/maas/+filebug
[21:08] <jfkw> Is there a syntax in cloud-init to disable a module, ntp in this case? Looking at my node's console log, I think ntp is only a warning, and the deployment fails for other reasons.
[21:17] <gimmic> noticed this in rackd: 2017-06-29 16:15:19 provisioningserver.utils.services: [info] observe-arp[em1]: FileNotFoundError: [Errno 2] No such file or directory: b'/bin/maas-rack'
[21:17] <gimmic> I don't see any bin/maas-rack, but I do see an sbin/maas-rack. What does this break?
[21:23] <roaksoax> jfkw: do you have full output
[21:23] <roaksoax> ?
[22:29] <dholt> @jfkw did you file a bug? I think I'm seeing the same issue
[22:56] <roaksoax> dholt: can you confirm you are using 2.2 or 2.1 ?
[22:56] <roaksoax> dholt: also, do you have a full log ?
[23:03] <dholt> i'm on 2.1: MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1)
[23:04] <dholt> i'll have to re-provision to get new logs, which would be most helpful?
[23:05] <jfkw> dholt: this seems to already describe the bug: https://bugs.launchpad.net/maas/+bug/1686485 My problem is more likely with lack of apt being able to reach my proxy during deploy, and failing for that reason.
[23:07] <dholt> ok, thanks; that seems unrelated to my issue. I can't deploy 16.04 at all any longer
[23:07] <dholt> it didn't coincide with an update or anything, just changed overnight
[23:15] <roaksoax> dholt: ah yes, there seems to be  kernel issue that's preventing deployment of xenial
[23:16] <roaksoax> dholt: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1701297
[23:17] <dholt> oh yeah, that's the one :) thanks
[23:18] <roaksoax> dholt: a *work-around* is to add a kernel param with apparmor=0
[23:30] <jfkw> roaksoax: where does one add a global kernel param? UI or CLI
[23:32] <jfkw> roaksoax: found it https://docs.ubuntu.com/maas/2.2/en/installconfig-nodes-kernel-boot-options
[23:47] <mup> Bug #1701400 opened: [2.3] Events page no longer auto-updates in chrome <MAAS:New> <https://launchpad.net/bugs/1701400>
[23:47] <mup> Bug #1701401 opened: [2.3, UI] Events page no longer auto-updates in chrome <MAAS:Triaged> <https://launchpad.net/bugs/1701401>