[04:40] <james> Hi
[04:41] <Guest79467> when i do the following command,  I am getting null value as o/p sudo virsh list --all
[04:42] <Guest79467> root@maasserver:/home/vagrant# sudo virsh list --all
[04:42] <Guest79467>  Id Name State
[04:42] <Guest79467>  ----------------------------------------------------
[04:42] <Guest79467>  root@maasserver:/home/vagrant#
[09:23] <mup> Bug #1491742 opened: Unable to modify static address pool when no machines exist <MAAS:New> <https://launchpad.net/bugs/1491742>
[09:26] <mup> Bug #1491742 changed: Unable to modify static address pool when no machines exist <MAAS:New> <https://launchpad.net/bugs/1491742>
[09:35] <mup> Bug #1491742 opened: Unable to modify static address pool when no machines exist <MAAS:New> <https://launchpad.net/bugs/1491742>
[12:47] <mup> Bug #1491822 opened: openstack-install crashes on juju bootstrap <MAAS:New> <https://launchpad.net/bugs/1491822>
[12:59] <mup> Bug #1491822 changed: openstack-install crashes on juju bootstrap <MAAS:New> <https://launchpad.net/bugs/1491822>
[13:05] <mup> Bug #1491822 opened: UnicodeDecodeError in _get_systemd_service_status <MAAS:Triaged> <https://launchpad.net/bugs/1491822>
[13:05] <mup> Bug #1491831 opened: maas-cli should allow to specify a cluster controller for a new node <MAAS:New> <https://launchpad.net/bugs/1491831>
[13:14] <mup> Bug #1491831 changed: maas-cli should allow to specify a cluster controller for a new node <MAAS:New> <https://launchpad.net/bugs/1491831>
[13:17] <mup> Bug #1491831 opened: maas-cli should allow to specify a cluster controller for a new node <MAAS:New> <https://launchpad.net/bugs/1491831>
[13:47] <mup> Bug #1491843 opened: maas web interface should display cluster names in the "Add a new node" cluster dropdown, not their DNS zone names <ux> <MAAS:Triaged> <https://launchpad.net/bugs/1491843>
[14:02] <bino> hi
[14:03] <bino> is anybody knows about virsh with maas
[14:03] <bino> ?
[14:17] <mup> Bug # changed: 1391612, 1482784, 1483305, 1491843
[14:28] <bino> ERROR Thu, 03 Sep. 2015 14:26:10 Failed to power on node — Node could not be powered on: virsh failed with return code 1: Failed to login to virsh console.
[14:28] <bino> have any idea regarding this
[14:48] <mup> Bug #1491887 opened: cannot create hostmaps when dhcpd server is down <MAAS:New> <https://launchpad.net/bugs/1491887>
[15:18] <mup> Bug #1491898 opened: update drivers.yaml with hpdsa driver entry <MAAS:New> <https://launchpad.net/bugs/1491898>
[15:48] <mup> Bug #1376483 changed:  AttributeError: 'Port' object has no attribute 'socket' <tech-debt> <MAAS:Invalid> <MAAS 1.8:Triaged> <https://launchpad.net/bugs/1376483>
[15:48] <mup> Bug #1378993 changed: Let administrators see the region secret in the MAAS UI, and provide instructions on how to register clusters. <MAAS:Won't Fix> <https://launchpad.net/bugs/1378993>
[16:09] <mup> Bug #1491924 opened: Deploying a node via the API with an incorrect HWE kernel succeeds <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1491924>
[16:09] <mup> Bug #1491927 opened: No way to tell what caused a node to be released <oil> <MAAS:New> <https://launchpad.net/bugs/1491927>
[16:39] <mup> Bug #1491927 changed: No way to tell what caused a node to be released <log> <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1491927>
[17:15] <mup> Bug #1491947 opened: ARM64 and ARMhf nodes report only 1 core on systems with 2 - 8 cores <MAAS:New> <https://launchpad.net/bugs/1491947>