[06:22] <mup> Bug #1717543 opened: [FFe] Standing Feature Freeze Exception for MAAS 2.3 <verification-needed> <verification-needed-artful> <maas (Ubuntu):New> <https://launchpad.net/bugs/1717543>
[06:22] <mup> Bug #1717543 changed: [FFe] Standing Feature Freeze Exception for MAAS 2.3 <verification-needed> <verification-needed-artful> <maas (Ubuntu):New> <https://launchpad.net/bugs/1717543>
[06:55] <mup> Bug #1721454 opened: Finding how to rename a node is difficult <MAAS:New> <https://launchpad.net/bugs/1721454>
[07:18] <boolman> I'm having trouble with my Maas, I can pxe boot. but the servers wont register. where can I get a complete list of network port requirements?
[07:18] <boolman> for my firewall
[08:31] <mup> Bug #1717543 changed: [FFe] Standing Feature Freeze Exception for MAAS 2.3 <verification-needed> <verification-needed-artful> <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1717543>
[11:18] <roaksoax> boolman: what's the error you see ?
[11:19] <roaksoax> d you have a console log ?
[11:47] <mup> Bug #1721523 opened: [2.3] tgt continues to get restarted and managed even when disabled <MAAS:Triaged> <https://launchpad.net/bugs/1721523>
[11:47] <mup> Bug #1721524 opened: [2.3, UI, HWTv2] When upgrading from older MAAS, Storage HW tests are not mapped to a disk <MAAS:Triaged> <https://launchpad.net/bugs/1721524>
[11:47] <mup> Bug #1721525 opened: [2.3, UI, HWTv2] Storage card on machine details page missing red bar on top if there are failed tests <MAAS:Triaged by newell-jensen> <https://launchpad.net/bugs/1721525>
[12:38] <mup> Bug # changed: 1389811, 1706462, 1707674, 1707675, 1710867, 1715337, 1715687
[12:59] <mup> Bug #1394306 changed: maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration <canonical-bootstack> <canonical-is> <MAAS:Won't Fix> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1394306>
[12:59] <mup> Bug # changed: 1394306, 1443644, 1537095, 1540539, 1540548, 1587201, 1612755, 1715345, 1715353
[13:05] <mup> Bug #1394306 opened: maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration <canonical-bootstack> <canonical-is> <MAAS:Won't Fix> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1394306>
[13:05] <mup> Bug # opened: 1394306, 1443644, 1537095, 1540539, 1540548, 1587201, 1612755, 1715345, 1715353
[13:08] <mup> Bug #1394306 changed: maas 1.7 upgrade: document potential need for maas-proxy.conf manual setup migration <canonical-bootstack> <canonical-is> <MAAS:Won't Fix> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1394306>
[13:08] <mup> Bug # changed: 1352582, 1379566, 1394306, 1443644, 1537095, 1540539, 1540548, 1575625, 1587201, 1612755, 1715345, 1715353
[13:17] <mup> Bug #1352582 opened: MAAS doesn't detect invalid YAML in curtin_userdata <canonical-is> <internal> <tech-debt> <MAAS:Fix Released> <https://launchpad.net/bugs/1352582>
[13:17] <mup> Bug #1379566 opened: maas-cluster depends on secure_path settings in sudoers <canonical-is> <MAAS:Fix Released> <https://launchpad.net/bugs/1379566>
[13:17] <mup> Bug #1575625 opened: Can't find way for MAAS to autodiscover IPMI settings <canonical-is> <MAAS:Invalid> <https://launchpad.net/bugs/1575625>
[13:26] <mup> Bug #1352582 changed: MAAS doesn't detect invalid YAML in curtin_userdata <canonical-is> <internal> <tech-debt> <MAAS:Fix Released> <https://launchpad.net/bugs/1352582>
[13:26] <mup> Bug #1379566 changed: maas-cluster depends on secure_path settings in sudoers <canonical-is> <MAAS:Fix Released> <https://launchpad.net/bugs/1379566>
[13:26] <mup> Bug #1575625 changed: Can't find way for MAAS to autodiscover IPMI settings <canonical-is> <MAAS:Invalid> <https://launchpad.net/bugs/1575625>
[13:38] <mup> Bug #1593487 changed: [2.0b7]maas-region-controller failed to preconfigure exit 127 <cdo-qa> <internal> <MAAS:Invalid> <https://launchpad.net/bugs/1593487>
[13:38] <mup> Bug #1628338 changed: 2.1a4:syslog flooded with whoami requests <cdo-qa> <internal> <MAAS:Invalid> <https://launchpad.net/bugs/1628338>
[13:44] <mup> Bug #1721548 opened: [2.3] Failure on controller refresh seem to be causing version to not get update <MAAS:Triaged> <https://launchpad.net/bugs/1721548>
[14:02] <mup> Bug #1721548 changed: [2.3] Failure on controller refresh seem to be causing version to not get update <MAAS:Triaged> <https://launchpad.net/bugs/1721548>
[14:08] <mup> Bug #1721548 opened: [2.3] Failure on controller refresh seem to be causing version to not get update <MAAS:Triaged> <https://launchpad.net/bugs/1721548>
[14:24] <saudk> Hello Guys
[14:24] <saudk> I am trying to import the ubuntu 16.04 image in MAAS
[14:25] <saudk> and seeing this error
[14:25] <saudk>  [ERROR] Failed to download images: [Errno 2] No such file or directory: u'/tmp/maas-Ud4i5y/usr/lib/shim/shim.efi.signed'
[14:25] <saudk> any ideas?
[14:25] <saudk> thanks
[14:33] <xgrid> exit
[16:50] <mup> Bug #1721587 opened: [2.3, UI, HWTv2] Commissioning logs (and those of v2 HW Tests) are not being show <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1721587>
[17:07] <roaksoax> saudk_: what version of MAAS are you using ?
[17:37] <junaidali> roaksoax: I had a private chat with saudk, he is using maas 1.9 on trusty
[17:39] <junaidali> with maas 2.2, he was facing an issue where importing image gets stuck. Moving on to 1.9, the image gets imported but in maas.log and clusterd.log, it errors out with the msg he shared
[17:43] <roaksoax> junaidali: he needs to upgrade to latest 1.9 in -proposed
[17:46] <shubjero> Anyone here work with Intel PCH RAID (available on supermicro servers and others).. I've got two SSD's configured as RAID-1 in the intel raid bios but MaaS still see's two separate SSD's.. I was expecting MaaS to see 1 virtual disk
[17:54] <junaidali> roaksoax: noted, thanks
[17:55] <roaksoax> shubjero: that could actually be an issue with the OS itself, since maas uses lsblk
[17:56] <shubjero> i would think the os would just show 1 device even with lsblk though.. since the whole point of a raid controller is to add a layer of abstraction
[17:58] <shubjero> im going to ignore the fact that maas see's the two disks, and just configure one of them to boot & install the os on and see what happens inside the os once it's deployed :)
[17:59] <roaksoax> shubjero: that's my point, it could be an issue with the os
[17:59] <shubjero> ok, fingers crossed.. here goes :)
[18:12] <shubjero> roaksoax: weird, the deploy crashed on ntp stuff? https://pastebin.com/ULXEc8Rg
[18:20] <roaksoax> shubjero: that's a known bug, are you sure you using your latest images ?
[18:20] <roaksoax> shubjero: it was an issue with the kernel
[18:21] <shubjero> mine are set to sync automatically
[18:23] <roaksoax> shubjero: what version of MAAS ?
[18:29] <shubjero> 2.1, but i see there are updates to my maas packages so im upgrading to 2.2
[18:35] <mup> Bug #1721611 opened: [2.3] Rack refresh failures may be causing controllers to become degraded <MAAS:Triaged> <https://launchpad.net/bugs/1721611>
[22:44] <JoeJulian> I cannot find a release schedule. When is 2.3.0 expected to go GA?