[06:35] Bug #1453669 was opened: APC PDU AP7xxx models do not allow multiple telnet connections [06:47] Bug #1453669 changed: APC PDU AP7xxx models do not allow multiple telnet connections [06:53] Bug #1453669 was opened: APC PDU AP7xxx models do not allow multiple telnet connections [08:30] Bug #1453481 changed: 1.8b5: have to page down to get to UI in firefox [09:36] Bug #1453730 was opened: Commissioning script contents is shown under page settings [09:48] Bug #1453730 was opened: Commissioning script contents is shown under page settings [09:48] Bug #1453730 changed: Commissioning script contents is shown under page settings [10:42] Bug #1453745 was opened: 1.8b4 move "view more" button to bottom of machine events section [10:42] Bug #1453749 was opened: 1.8b4 events page doesn't display events [11:12] Bug #1453764 was opened: After upgrade from 1.7.4 (to be released) and 1.8.0b5 in Vivid, Unable to connect to: ws://10.55.60.27:5240/MAAS/ws [12:12] Bug #1453726 was opened: MAAS error failed [3/7] (00-maas-03-install-lldpd, 99-maas-01-wait-for-lldpd, 99-maas-02-capture-lldp) === rbanffy_ is now known as rbanffy === jfarschman is now known as MilesDenver === cgseller_is_away is now known as imthewherd === imthewherd is now known as cgseller_is_away [13:24] Bug #1450729 changed: juju should be able to use nodes acquired by the same user in MAAS === cgseller_is_away is now known as imthewherd === jfarschman is now known as MilesDenver === jfarschman is now known as MilesDenver [15:18] Bug #1425340 was opened: Lack of a released hwe-t image for precise prevents Adaptec RAID controller from working in precise [16:19] Bug #1453869 was opened: Deployment failed due to failed to fetch bzip2 [16:19] Bug #1453872 was opened: Prodstack: bootstrap instance started but did not change to Deployed state [16:58] Bug #1453878 was opened: Feature: Add ability to lock Machine status [18:21] Hello all, I have been attempting to deploy maas for a week now and have been having trouble getting nodes to actually commission properly. I have used the backdoor instructions to get a login to a failing node and it seems the error is the apt-get update is hanging and/or going extremely slow, could someone help me debug this further, I'm running out of [18:21] ideas === imthewherd is now known as cgseller_is_away === cgseller_is_away is now known as imthewherd === imthewherd is now known as cgseller_is_away [19:45] It seems what is happening is after I tell it to commission the machine boots into the commissioning os (14.04) it runs apt-get update, this apt-get update takes so long that by the time it is finished maas has already marked the machine as failed commissioning. I am watching a machine now that is making progress in running apt-get update however since it [19:45] has been running for 45 minutes maas has already marked it as failed [20:52] Bug #1453954 was opened: 500 error reported to juju when starting node - "another action is already in progress for that node" === mwhudson_ is now known as mwhudson [21:22] Bug #1453960 was opened: maas 1.8, cannot select ip address of node [21:46] blake_r: around? [22:01] Bug #1453983 was opened: maas import image process blocks installs? [22:13] Bug #1453983 changed: maas import image process blocks installs? [22:28] Bug #1453983 was opened: maas import image process blocks installs? [22:59] Bug #1453983 changed: maas import image process blocks installs? === cgseller_is_away is now known as imthewherd