[00:28] <mup> Bug #1729474 opened: Feature request, option to enable SR-IOV in the bios <canonical-bootstack> <MAAS:Triaged> <https://launchpad.net/bugs/1729474>
[00:34] <mup> Bug #1729474 changed: Feature request, option to enable SR-IOV in the bios <canonical-bootstack> <MAAS:Triaged> <https://launchpad.net/bugs/1729474>
[00:52] <mup> Bug #1729474 opened: Feature request, option to enable SR-IOV in the bios <canonical-bootstack> <MAAS:Incomplete> <https://launchpad.net/bugs/1729474>
[10:32] <mup> Bug #1729555 opened: [2.3b3, Filtering] I want to be able to filter out the VMS of a Pod from the machine listing <ui> <MAAS:New> <https://launchpad.net/bugs/1729555>
[11:02] <mup> Bug #1729567 opened: [2.3b3, UI] The selected images is not visible unless I scroll so I don't know what the status of the images is <ui> <MAAS:New> <https://launchpad.net/bugs/1729567>
[11:08] <mup> Bug #1729567 changed: [2.3b3, UI] The selected images is not visible unless I scroll so I don't know what the status of the images is <ui> <MAAS:New> <https://launchpad.net/bugs/1729567>
[11:11] <mup> Bug #1729567 opened: [2.3b3, UI] The selected images is not visible unless I scroll so I don't know what the status of the images is <ui> <MAAS:New> <https://launchpad.net/bugs/1729567>
[11:11] <mup> Bug #1729570 opened: [2.3, UI] Custom is a weird name for the images source <ui> <MAAS:New> <https://launchpad.net/bugs/1729570>
[11:29] <mup> Bug #1729570 changed: [2.3, UI] Custom is a weird name for the images source <ui> <MAAS:New> <https://launchpad.net/bugs/1729570>
[11:32] <mup> Bug #1729570 opened: [2.3, UI] Custom is a weird name for the images source <ui> <MAAS:New> <https://launchpad.net/bugs/1729570>
[11:32] <mup> Bug #1729577 opened: [2.3, UI] The sync images toggle can be turned on/off without any warnings <ui> <MAAS:New> <https://launchpad.net/bugs/1729577>
[13:14] <mohankumar_> Hi team , how to  login to maas nodes after commissioning ?
[13:22] <roaksoax> mohankumar_: the nodes after commissioning are in ready state, which means are available for you to deploy
[13:23] <roaksoax> when you deploy a node, you can log in with the ssh key you added for your user
[13:25] <c06> hi all
[13:25] <c06> how i can add my custom iso to maas.
[13:26] <c06> my maas is syncing with 16.04.3 but i want to use 16.04.2. how i can do this one?
[13:32] <mohankumar_> roaksoax : Actually  , in my deployment kvm01 node  got commission failed , but I can't  see any error in  kvm01 console , and kvm01 node reached  login prompt
[13:33] <mohankumar_> roaksoax : So  any default username/password ?
[14:02] <roaksoax> c06: you cannot add custom ISO' to MAAS.
[14:02] <roaksoax> c06: you would need to create a mirror with an older image
[14:02] <roaksoax> c06: unless you grab a root-tgz of ubuntu 16.04.2 and add it to maas as a custom image
[14:04] <roaksoax> mohankumar_: if you want to log into commissioning, you need to enable ssh, have your ssh key improted
[14:04] <roaksoax> and ssh with ubuntu@
[14:40] <mup> Bug #1729127 opened: storage: No available machine matches constraints <juju:Triaged by ecjones> <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1729127>
[14:52] <mup> Bug #1729127 changed: storage: No available machine matches constraints <juju:Triaged by ecjones> <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1729127>
[14:58] <mup> Bug #1729127 opened: storage: No available machine matches constraints <juju:Triaged by ecjones> <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1729127>
[16:09] <mup> Bug #1729633 opened: Cannot return to controllers page from specific controller <MAAS:New> <https://launchpad.net/bugs/1729633>
[16:15] <mup> Bug #1729633 changed: Cannot return to controllers page from specific controller <MAAS:New> <https://launchpad.net/bugs/1729633>
[16:18] <mup> Bug #1729633 opened: Cannot return to controllers page from specific controller <MAAS:New> <https://launchpad.net/bugs/1729633>
[16:27] <mup> Bug #1729633 changed: Cannot return to controllers page from specific controller <MAAS:New> <https://launchpad.net/bugs/1729633>
[16:30] <mup> Bug #1390147 changed: abort_operation doesn't work for releasing, commissioning, deploying. <MAAS:Fix Released> <https://launchpad.net/bugs/1390147>
[16:30] <mup> Bug #1605538 changed: Too many "maas" logger names in use <error-surface> <MAAS:Won't Fix> <https://launchpad.net/bugs/1605538>
[16:30] <mup> Bug #1681322 changed: Architecture filter for New machines <MAAS:Fix Released> <https://launchpad.net/bugs/1681322>
[16:30] <mup> Bug #1729633 opened: Cannot return to controllers page from specific controller <MAAS:New> <https://launchpad.net/bugs/1729633>
[16:30] <mup> Bug #1729638 opened: Allow to keep an unlimited number of test results <MAAS:Triaged> <https://launchpad.net/bugs/1729638>
[16:30] <mup> Bug #1729641 opened: Adding 2.2 Rack controller to 2.3 Cluster causes Power Error on Ready nodes <MAAS:New> <https://launchpad.net/bugs/1729641>
[16:30] <shadoxx> Shot in the dark here. Does anyone have an HPE Support Agreement and would be willing to download an ISO for me?
[17:00] <mup> Bug #1663612 changed: [2.2, rev5710] During commissioning, UI shows 'Error:Node must be connected to a network.' <MAAS:Invalid> <https://launchpad.net/bugs/1663612>
[17:00] <mup> Bug #1667574 changed: default gateway not set when deploying a machine with two interfaces in same network <internal> <sts> <MAAS:Fix Released> <https://launchpad.net/bugs/1667574>
[17:00] <mup> Bug #1669223 changed: [2.2, r5770, UI] Commissioning Results has 'Status' column <MAAS:Invalid> <https://launchpad.net/bugs/1669223>
[17:00] <mup> Bug #1729649 opened: Initial delete of secondary rack controller fails <MAAS:New> <https://launchpad.net/bugs/1729649>
[17:15] <mup> Bug # changed: 1554532, 1630034, 1638262, 1639277, 1660495, 1690919
[17:45] <mup> Bug # changed: 1660593, 1661591, 1666317, 1669183, 1682432, 1688020
[18:28] <[Kid]> is there a way to clone nodes in maas?
[18:43] <mup> Bug #1580279 changed: [2.0] maas-cli 2.0 doesn't find 1.0 api <amd64> <apport-bug> <oil> <xenial> <MAAS:Won't Fix> <maas (Ubuntu):Won't Fix> <https://launchpad.net/bugs/1580279>
[18:44] <mup> Bug #1637246 changed: MaaS should use configured names for VLAN interfaces <MAAS:Fix Released by mpontillo> <MAAS 2.0:Won't Fix> <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1637246>
[18:45] <mup> Bug # changed: 1357086, 1548390, 1557520, 1561494, 1567196, 1572060, 1573033, 1575951, 1580279, 1581609, 1583093, 1584206, 1584562, 1596683, 1602488, 1603477, 1604738, 1604938
[19:15] <mup> Bug # changed: 1294131, 1314571, 1317655, 1317973
[19:24] <mup> Bug # changed: 1239668, 1247755, 1307614, 1308469, 1321313, 1350941, 1402690
[19:42] <mup> Bug # opened: 1239668, 1247755, 1307614, 1308469, 1321313, 1350941, 1402690
[19:45] <mup> Bug # changed: 1054131, 1239668, 1247755, 1307614, 1308469, 1321313, 1350941, 1361426, 1376144, 1390097, 1390411, 1393992, 1401193, 1401644, 1402690, 1405290, 1409946,
[19:45] <mup> 1411009, 1412349, 1413125, 1417925, 1418244, 1418785, 1418959, 1422818, 1423306, 1423663, 1427628, 1428705, 1431721, 1431723, 1431820, 1434664, 1438977, 1447728
[20:15] <mup> Bug # changed: 974039, 1359043, 1367501, 1381191, 1391254, 1412690, 1438885, 1441686, 1447681, 1461462, 1464701, 1464741, 1484204, 1488684, 1495998, 1510489, 1512820, 1513413
[20:24] <mup> Bug #1483193 changed: Time column heading for events on node details page mis-aligned <landscape> <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1483193>
[20:24] <mup> Bug #1501978 changed: Too many logs when posting to the status API <MAAS:Invalid> <https://launchpad.net/bugs/1501978>
[20:24] <mup> Bug #1505378 changed: websocket error on 1.9 alpha 4 <MAAS:Invalid> <https://launchpad.net/bugs/1505378>
[20:48] <mup> Bug #1729691 opened: ubuntu 16.04.3 LTS dvd maas install fails <MAAS:New> <https://launchpad.net/bugs/1729691>
[21:24] <mup> Bug #1491236 changed: How to configure MAAS with virsh is not clear <doc> <MAAS:Invalid> <https://launchpad.net/bugs/1491236>
[21:24] <mup> Bug #1729691 changed: ubuntu 16.04.3 LTS dvd maas install fails <MAAS:New> <https://launchpad.net/bugs/1729691>
[21:36] <mup> Bug # changed: 1376015, 1405288, 1424090, 1427629, 1442112, 1454132, 1496339, 1502333, 1504173, 1506856
[21:45] <mup> Bug # opened: 1376015, 1405288, 1424090, 1427629, 1442112, 1454132, 1496339, 1502333, 1504173, 1506856
[21:54] <mup> Bug # changed: 1376015, 1405288, 1424090, 1427629, 1442112, 1454132, 1496339, 1502333, 1504173, 1506856
[22:06] <mup> Bug # changed: 1307671, 1371796, 1424549, 1459894, 1466162, 1468113, 1468844, 1471249, 1471728, 1494483, 1498221, 1507630, 1508087, 1508696, 1510746, 1511279, 1511689, 1512765, 1515191, 1516229, 1636860, 1651245, 1655165
[22:06] <mup> Bug #1729694 opened: [2.3, UI, regression] With new node details page, no longer able to see devices (lxc's, kvms) that belong to that machine (e.g. juju cases) <MAAS:Triaged> <https://launchpad.net/bugs/1729694>
[22:52] <shadoxx> Anyone know why rescue mode wouldn't boot? Complaining about not being able to make a connection to iscsi on the MaaS controller
[23:06] <mup> Bug #1457555 changed: exceptions.ValueError: No JSON object could be decoded <MAAS:Invalid by mpontillo> <simplestreams:Invalid> <https://launchpad.net/bugs/1457555>