[00:06] pmatulis: the MAAS machine can access to archive.u.c, hence the proxy software can resolve just fine a.u.c. So when uses the proxy, the proxy knows how to reach a.u.c [02:37] i have a maas setup that is using wake on lan to start nodes. however "stop node" doesn't do anything [02:37] maas also doesn't seem to be aware of nodes that have been powered on outside of the system. in general it doesn't seem to monitor the power state of machines [02:38] are such features only available when using IPMI or similar [02:38] ? [03:00] oh seems to be answered here: http://askubuntu.com/questions/583635/maas-check-power-state-error-unknown-power-type-ether-wake [03:00] nevermind [04:29] Bug #1459088 was opened: Internal Server Error during commissioning [04:59] Bug #1445482 changed: Nodes in "New" state cannot be powered off === cyberjacob is now known as zz_cyberjacob [09:44] Bug #1459168 was opened: Start-up stacktrace: IntegrityError: duplicate key value violates unique constraint "maasserver_config_name_uniq" DETAIL: Key (name)=(rpc_shared_secret) already exists. [10:32] Bug #1457879 changed: UnknownRemoteError: Code: Unknown Error raised when calling update_host_maps [10:33] Bug #1459088 changed: UnknownRemoteError: Code: Unknown Error when calling delete_host_maps === _ is now known as Guest38326 [13:48] Bug #1294711 changed: power management broken after upgrade from saucy [13:48] Bug #1294711 changed: power management broken after upgrade from saucy [13:48] Bug #1457191 changed: Fresh install (from trunk or ppa:maas-maintainers/experimental) results in /var/log/maas/clusterd.log being owned by root === imthewhe` is now known as cgseller_is_away === lifeless_ is now known as lifeless [16:18] Bug #1459331 was opened: exceptions.AttributeError: 'ServiceParsingError' object has no attribute 'output_as_unicode' [16:18] Bug #1459338 was opened: Service checking on utopic wrongly assumes the system is using systemd. === zz_cyberjacob is now known as CyberJacob [18:25] Bug #1459380 was opened: MAAS logs 503 spurious errors when the region service isn't yet online [18:31] Bug #1459380 changed: MAAS logs 503 spurious errors when the region service isn't yet online [18:37] Bug #1459380 was opened: MAAS logs 503 spurious errors when the region service isn't yet online [19:52] Bug #1459405 was opened: Systems can't be recommissioned as part of releasing [21:04] Bug #1459432 was opened: "could not serialize access due to concurrent update" errors in PostgreSQL logs [21:16] Bug #1459432 changed: "could not serialize access due to concurrent update" errors in PostgreSQL logs [21:22] Bug #1459432 was opened: "could not serialize access due to concurrent update" errors in PostgreSQL logs [21:22] Bug #1459441 was opened: Add Interface is in the lowest left corner of the Network section [21:28] Bug #1459441 changed: Add Interface is in the lowest left corner of the Network section [21:34] Bug #1459441 was opened: Add Interface is in the lowest left corner of the Network section [22:04] Bug #1459444 was opened: Info for the PXE NIC available in MAAS UI but there is no API to get this info [22:44] Can MAAS be installed on a VM? === CyberJacob is now known as zz_CyberJacob === menn0_ is now known as menn0