[04:27] <mup> Bug #1660617 changed: [2.1.3] curtin_userdata fails to render <MAAS:Expired> <https://launchpad.net/bugs/1660617>
[11:38] <dakj> Hello guys, I've a problem with last MAAS service, it not complete il download of ubuntu 16.04 image, arrives at 98% then stop it. I've tried also the other image and it works
[11:42] <dakj> Anyone can help me?
[12:36] <dakj> Hello guys, I've a problem with last MAAS service, it not complete il download of ubuntu 16.04 image, arrives at 98% then stop it. I've tried also the other image and it works. Anyone can help me please?
[13:00] <pmatulis> dakj, disk space?
[13:01] <dakj> 500GB available!!!
[13:03] <pmatulis> dakj, checked logs (regiond and rackd)?
[13:04] <dakj> Pmatulis, if I make the download of ubuntu 14.04lts it's complete the task with 16.04 no
[13:05] <dakj> Pmatulis, I've opened also a post here http://askubuntu.com/questions/899073/maas-dont-make-the-download-of-ubuntu-16-04-lts-image
[13:28] <pmatulis> dakj, can you get some info from the CLI? begin by logging in to the API server
[13:29] <pmatulis> dakj, we should first confirm the "image source"
[13:29] <pmatulis> see https://docs.ubuntu.com/maas/2.1/en/manage-cli-images
[14:01] <dakj> Pmatulis, lets me test that
[14:34] <dakj> pamtulis, how do I show you the result?
[14:35] <dakj> :maas richardsith boot-sources read
[14:35] <dakj> Success.
[14:35] <dakj> Machine-readable output follows:
[14:35] <dakj> [
[14:35] <dakj>     {
[14:35] <dakj>         "url": "http://images.maas.io/ephemeral-v3/daily/",
[14:35] <dakj>         "keyring_data": "",
[14:35] <dakj>         "resource_uri": "/MAAS/api/2.0/boot-sources/1/",
[14:35] <dakj>         "id": 1,
[14:35] <dakj>         "updated": "2017-04-03T17:14:09.518",
[14:35] <dakj>         "created": "2017-04-01T00:01:49.492",
[14:35] <dakj>         "keyring_filename": "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg"
[14:35] <dakj>     }
[14:35] <dakj> :maas richardsith boot-sources read
[14:35] <dakj> Success.
[14:35] <dakj> Machine-readable output follows:
[14:35] <dakj> [
[14:35] <dakj>     {
[14:35] <dakj>         "url": "http://images.maas.io/ephemeral-v3/daily/",
[14:35] <dakj>         "keyring_data": "",
[14:35] <dakj>         "resource_uri": "/MAAS/api/2.0/boot-sources/1/",
[14:35] <dakj>         "id": 1,
[14:35] <dakj>         "updated": "2017-04-03T17:14:09.518",
[14:35] <dakj>         "created": "2017-04-01T00:01:49.492",
[14:35] <dakj>         "keyring_filename": "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg"
[14:35] <dakj>     }
[14:35] <dakj> ]
[14:37] <dakj> Pmatulis, sorry
[14:42] <pmatulis> dakj, use a pastebin next time
[14:43] <pmatulis> dakj, what version of maas?
[14:43] <dakj> Pmatulis, I was making that!!
[14:43] <dakj> Pmatulis, MAAS Version 2.1.5+bzr5596-0ubuntu1
[15:06] <mup> Bug #1679206 opened: [2.1.5] Maas fails to deploy hardware-ibm-power8-S822LC system with USB drive plugged in <cdo-qa-blocker> <oil> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1679206>
[15:09] <dakj> Pantelis, any idea?
[15:13] <cnf> anyone deploy esx nodes with maas?
[15:15] <dakj> Pmatulis, any suggests?
[15:53] <pmatulis> dak...
[16:12] <mup> Bug #1679222 opened: ISCSI target validation fails when target name includes a ':' <iscsi> <rsd> <curtin:Triaged by nacc> <MAAS:Triaged> <MAAS RSD :Triaged> <https://launchpad.net/bugs/1679222>
[16:21] <mup> Bug #1679222 changed: ISCSI target validation fails when target name includes a ':' <iscsi> <rsd> <curtin:Triaged by nacc> <MAAS:Triaged> <MAAS RSD :Triaged> <https://launchpad.net/bugs/1679222>
[16:27] <mup> Bug #1679222 opened: ISCSI target validation fails when target name includes a ':' <iscsi> <rsd> <curtin:Triaged by nacc> <MAAS:Triaged> <MAAS RSD :Triaged> <https://launchpad.net/bugs/1679222>
[16:51] <mup> Bug #1679231 opened: Machine MACs do not show when MAC is the selected column <MAAS:In Progress by lamont> <https://launchpad.net/bugs/1679231>
[17:51] <mup> Bug #1679247 opened: [2.2] Random unit test failure in TestListClusterNodesPowerParameters.test__returns_checked_nodes_in_last_checked_order <unit-tests> <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1679247>
[17:51] <mup> Bug #1679249 opened: [2.2b5] Machines table occasionally shows javascript trace in the console log <MAAS:Triaged> <https://launchpad.net/bugs/1679249>
[21:10] <cmd_pancakes> mpontillo: not sure if my last question went through, had connection issues...is there anyway to stop creating the mdadm disk groups in the initial pxe image of MAAS? i have a host connected to a large storage array via SAS and the pxe image is dropping to the busybox shell because it can't connect to the rack controller
[21:10] <cmd_pancakes> i only want the head node under MAAS control, i can configure the disk array later on
[21:10] <cmd_pancakes> tgtd seems to be working fine on the rack controller, no firewall between the hosts
[21:31] <mup> Bug #1679312 opened: [maas 2.2 beta5] Connection refused after juju (2.2 beta1) deploy ESXi VM  - Juju Agent pending <oil> <oil-2.0> <juju:New> <MAAS:New> <https://launchpad.net/bugs/1679312>
[21:31] <mup> Bug #1679315 opened: [2.0] Updating the name of a domain only changes one machine in the web ui <MAAS:In Progress by lamont> <https://launchpad.net/bugs/1679315>
[21:32] <mpontillo> cmd_pancakes: hm, sorry, I don't really have a good understanding of the problem. is this because the default gateway is being set from a different interface (such as the storage interface) and the machine can't reach the rack? you can try using the API to set the gateways
[21:35] <mpontillo> cmd_pancakes: for example, "maas $PROFILE interfaces read $SYSTEM_ID" followed by "maas admin interface set-default-gateway $SYSTEM_ID $IFNAME id=$LINK_ID"
[21:35] <mpontillo> cmd_pancakes: that is, make sure the default gateway is set to a link on the interface which can reach the rack controller.
[21:58] <mup> Bug #1679322 opened: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1679322>
[23:07] <mup> Bug #1679427 opened: [2.2] Commissioning support script should withhold ephemeral keys <MAAS:Triaged> <https://launchpad.net/bugs/1679427>
[23:37] <mup> Bug #1679431 opened: [2.2] If a single commissioning script times out, all scripts will enter "Timed out" state. <MAAS:New> <https://launchpad.net/bugs/1679431>
[23:43] <mup> Bug #1679431 changed: [2.2] If a single commissioning script times out, all scripts will enter "Timed out" state. <MAAS:New> <https://launchpad.net/bugs/1679431>
[23:55] <mup> Bug #1679431 opened: [2.2] If a single commissioning script times out, all scripts will enter "Timed out" state. <MAAS:New> <https://launchpad.net/bugs/1679431>