[01:34] <mup> Bug #1664424 opened: Add easy BMC console access to MAAS <MAAS:New> <https://launchpad.net/bugs/1664424>
[08:31] <MaWe_> client ntp error while commissioning: /usr/sbin/ntpd: error while loading shared libraries: libcap.so.2: cannot stat shared object: Permission denied
[08:33] <MaWe_> I've done commissioning with ssh access. After connecting to maas-client 'service ntp restart' failed with the error above
[08:33] <MaWe_> any suggestions?
[08:56] <MaWe_> -- Unit ntp.service has begun starting up. Feb 14 10:55:14 ech2 ntp[7535]:  * Starting NTP server ntpd Feb 14 10:55:14 ech2 audit[7544]: AVC apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="overlay/etc/ld.so Feb 14 10:55:14 ech2 audit[7544]: AVC apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" n
[08:56] <MaWe_> upps... sorry strange newlines :-(
[10:46] <MaWe_> ?
[13:04] <mup> Bug #1533719 changed: Adding a device with a MAC address that's belongs to another node, fails without providing any feedback <error-surface> <MAAS:Fix Released> <MAAS 1.9:Triaged> <MAAS 2.1:Triaged> <MAAS trunk:Fix Released> <https://launchpad.net/bugs/1533719>
[13:04] <mup> Bug #1664558 opened: [UI] Save machine without MAC address does nothing <error-surface> <MAAS:Triaged> <https://launchpad.net/bugs/1664558>
[13:04] <MaWe_> Hello there, I had a strange error while commisioning: "update clock skew to -7324" and "http error 401"
[13:04] <MaWe_> after investigating a bit I found out that my client is not able to start ntpd
[13:04] <MaWe_> -- Unit ntp.service has begun starting up.
[13:04] <MaWe_> Feb 14 10:55:14 ech2 ntp[7535]:  * Starting NTP server ntpd
[13:05] <MaWe_> Feb 14 10:55:14 ech2 audit[7544]: AVC apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="overlay/etc/ld.so
[13:05] <MaWe_> Feb 14 10:55:14 ech2 audit[7544]: AVC apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="lib/x86_64-linux-
[13:05] <MaWe_> Feb 14 10:55:14 ech2 kernel: audit: type=1400 audit(1487069714.478:32): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/
[13:05] <MaWe_> Feb 14 10:55:14 ech2 kernel: audit: type=1400 audit(1487069714.478:33): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 profile="/usr/
[13:05] <MaWe_> Feb 14 10:55:14 ech2 ntp[7535]: /usr/sbin/ntpd: error while loading shared libraries: libcap.so.2: cannot stat shared object: Permission denied
[13:05] <MaWe_> Feb 14 10:55:14 ech2 ntp[7535]:    ...fail!
[13:06] <MaWe_> Installation is quite new ... any suggestions?
[13:12] <kklimonda> any idea why after trusty deployment sources.list is being overwritten by defaults?
[13:16] <mup> Bug #1664558 changed: [UI] Save machine without MAC address does nothing <error-surface> <MAAS:Triaged> <https://launchpad.net/bugs/1664558>
[13:16] <mup> Bug #1533719 opened: Adding a device with a MAC address that's belongs to another node, fails without providing any feedback <error-surface> <MAAS:Fix Released> <MAAS 1.9:Triaged> <MAAS 2.1:Triaged> <MAAS trunk:Fix Released> <https://launchpad.net/bugs/1533719>
[13:19] <mup> Bug #1533719 changed: Adding a device with a MAC address that's belongs to another node, fails without providing any feedback <error-surface> <MAAS:Fix Released> <MAAS 1.9:Triaged> <MAAS 2.1:Triaged> <MAAS trunk:Fix Released> <https://launchpad.net/bugs/1533719>
[13:19] <mup> Bug #1664558 opened: [UI] Save machine without MAC address does nothing <error-surface> <MAAS:Triaged> <https://launchpad.net/bugs/1664558>
[13:19] <mup> Bug #1664563 opened: Abort fails when deploying <MAAS:Triaged> <https://launchpad.net/bugs/1664563>
[13:25] <mup> Bug #1664563 changed: Abort fails when deploying <MAAS:Triaged> <https://launchpad.net/bugs/1664563>
[13:34] <mup> Bug #1664563 opened: Abort fails when deploying <MAAS:Triaged> <https://launchpad.net/bugs/1664563>
[15:58] <mup> Bug #1664618 opened: Spurious test failure in TestPostgresListenerService.test__handles_missing_system_handler_on_notification <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1664618>
[16:07] <mup> Bug #1664618 changed: Spurious test failure in TestPostgresListenerService.test__handles_missing_system_handler_on_notification <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1664618>
[16:16] <mup> Bug #1664618 opened: Spurious test failure in TestPostgresListenerService.test__handles_missing_system_handler_on_notification <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1664618>
[17:09] <myra> hello world !
[17:25] <myra> Is anyone here expert in MaaS ?
[17:26] <bdx> myra: you will find a myriad of the type here :-)
[17:27] <myra> a what ?
[17:30] <myra> ...
[17:31] <ms2i> 	Can anyone point me in the right direction regarding discovery of new nodes and subsequent commissioning? I have 10 nodes in "New" status and I can't see in the GUI how any "New" node is related to IP addresses in the BMC subnet of my nodes.
[17:32] <ms2i> When I randomly set the power IP of a node and then select the "Commission" action, I can see in the MAAS logs that MAAS has a different idea about which node name is associated with that power IP.
[17:33] <ms2i> How can I see the associations that MAAS has pre-determined? And why am I asked to enter a power IP if there's already a mapping buried somewhere inside MAAS?
[17:34] <ms2i> I'm able to commission nodes successfully only by guessing at the power IP, then selecting the commission action, then aborting the action when I see what the actual node name connected to that power IP is, then configuring that node name that appears in the rsyslog folder with the Power IP I selected originally.
[17:35] <ms2i> There must be something wrong here. What am I missing? This can't possibly be intended behavior can it?
[17:36] <ms2i> My BMC/IPMI network ports are on their own VLAN, and the machine's also have a 10Gbe port on another VLAN. These are Quanta Opencompute nodes and have two MAC addresses associated with the BMC port, so the same physical port can be used by the OS as well.
[17:37] <mup> Bug #1661022 changed: [2.2beta1] artifact collection fails because of MAAS 2.2 API errors - TypeError: Incorrect padding <MAAS:Triaged by newell-jensen> <https://launchpad.net/bugs/1661022>
[17:43] <myra>  how I can deploy a Debian image on Maas ?
[17:43] <myra> All I found were Ubuntu releases and CentOS and I tried with the custom image option but I just didn't know how to do it. Is it not supported? because if so, they didn't mention it in the docs.
[17:46] <mup> Bug #1661022 opened: [2.2beta1] artifact collection fails because of MAAS 2.2 API errors - TypeError: Incorrect padding <MAAS:Triaged by newell-jensen> <https://launchpad.net/bugs/1661022>
[17:55] <mup> Bug #1661022 changed: [2.2beta1] artifact collection fails because of MAAS 2.2 API errors - TypeError: Incorrect padding <MAAS:Triaged by newell-jensen> <https://launchpad.net/bugs/1661022>
[18:46] <mate_> how I can deploy a Debian image on Maas ?
[18:46] <mate_> All I found were Ubuntu releases and CentOS and I tried with the custom image option but I just didn't know how to do it. Is it not supported? because if so, they didn't mention it in the docs.
[19:19] <mup> Bug #1664664 opened: Compose causes infinite loop on MAAS rack <MAAS:In Progress by newell-jensen> <MAAS RSD :In Progress by newell-jensen> <https://launchpad.net/bugs/1664664>
[19:19] <mup> Bug #1664667 opened: Pod architectures are listed multiple times <MAAS:In Progress by newell-jensen> <MAAS RSD :In Progress by newell-jensen> <https://launchpad.net/bugs/1664667>
[19:22] <cj9255> JOIN
[20:22] <mup> Bug #1660182 changed: [2.1.2] not able to locate regiond connection issue log messages in regiond.log and rackd.log <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1660182>
[22:17] <mup> Bug #1664732 opened: Deleting RSD Pod fails because it tries deleting composed node twice. <MAAS:Confirmed for blake-rouse> <MAAS RSD :Confirmed for blake-rouse> <https://launchpad.net/bugs/1664732>
[22:29] <mup> Bug #1664732 changed: Deleting RSD Pod fails because it tries deleting composed node twice. <MAAS:Confirmed for blake-rouse> <MAAS RSD :Confirmed for blake-rouse> <https://launchpad.net/bugs/1664732>
[22:35] <mup_> Bug #1664732 opened: Deleting RSD Pod fails because it tries deleting composed node twice. <MAAS:Confirmed for blake-rouse> <MAAS RSD :Confirmed for blake-rouse> <https://launchpad.net/bugs/1664732>
[22:59] <mup> Bug #1310846 changed: amt template gives up way too easily <patch> <MAAS:Fix Released by kirkland> <maas (Ubuntu):Fix Released> <maas (Ubuntu Trusty):Fix Released> <https://launchpad.net/bugs/1310846>
[22:59] <mup> Bug #1664748 opened: wifi connection drops, reconnects every 10 minutes <maas-at-home> <maas (Ubuntu):New> <https://launchpad.net/bugs/1664748>
[22:59] <mup> Bug #1664751 opened: assign static ip from the web ui <maas-at-home> <maas (Ubuntu):New> <https://launchpad.net/bugs/1664751>
[23:05] <mup> Bug #1664751 changed: assign static ip from the web ui <maas-at-home> <maas (Ubuntu):New> <https://launchpad.net/bugs/1664751>