[02:27] <mup> Bug #1679882 opened: [2.1] rackd status is stuck at "NN% connected to region controllers" with Active-Active regiond <MAAS:New> <https://launchpad.net/bugs/1679882>
[02:45] <mup> Bug #1662404 changed: "No rack controllers can access the BMC of node: <node name>" when using OpenStack nova power driver  <MAAS:Fix Released> <MAAS 2.1:Triaged> <https://launchpad.net/bugs/1662404>
[02:45] <mup> Bug #1679887 opened: [2.1] regiond should not rely on maas-rack command <MAAS:New> <https://launchpad.net/bugs/1679887>
[03:39] <mup> Bug #1679887 changed: [2.1] regiond should not rely on maas-rack command <MAAS:New> <https://launchpad.net/bugs/1679887>
[06:57] <hrz_jlu> Hello everybody out there using MaaS,
[06:58] <hrz_jlu> Chicken-egg problem in maas-cli? Or did i miss a point? -- Can not format logical volume
[06:58] <hrz_jlu> I can create a VG: SYS_VG=$(maas ${PROFILE} volume-groups create ${HOST_ID} name="system-vg" partitions=$(echo ${SYS_VG_PARTITION} | jq '. | .id'))
[06:58] <hrz_jlu> I can create a LV: ROOT_LV=$(maas ${PROFILE} volume-group create-logical-volume ${HOST_ID} $(echo ${SYS_VG} | jq '. | .id') name="system-root" size=100G)
[06:58] <hrz_jlu> But how can i format this LV?
[06:58] <hrz_jlu> fail #1: creating a partition returns with: {"block_device": ["Cannot create a partition table on a logical volume."]}
[06:58] <hrz_jlu> fail #2: to format the volume I need system_id, device_id, id. I have system_id and id, but what is the device_id?
[06:58] <hrz_jlu> -->   echo ${ROOT_LV} | jq {   "system_id": "eq6fr7",   "size": 99996401664,   "available_size": 99996401664,   "name": "system-vg-system-root",   "resource_uri": "/MAAS/api/2.0/nodes/eq6fr7/blockdevices/9/",   "uuid": "fff3f729-7811-4426-ba48-2ce74427eb58",   "used_size": 0,   "id": 9 }
[07:39] <zeestrat> hrz_jlu: Not sure if helpful but, after creating LV's, we read them with "maas PROFILE volume-groups read" to get their id, then format with "maas PROFILE block-device format SYSTEM_ID, LV_ID fstype=ext4"
[08:32] <dakj> Pmatulis, hi any suggest?
[11:28] <dakj> pmatulis, I've used tcpdump but the file is too big, I just saw the line "images-maas-io.sawo.canonical.com.http" but I can't see the error
[11:30] <brendand> dakj, you probably want to confirm that the image was entirely downloaded at the time when it freezes
[11:33] <brendand> dakj, you can find the downloaded artifacts in /var/lib/maas/boot-resources
[11:34] <jlu-hrz> Hello everybody out there using MaaS
[11:34] <jlu-hrz> 2nd try (sorry browser has crashed)
[11:34] <jlu-hrz> Chicken-egg problem in maas-cli? Or did i miss a point? -- Can not format logical volume
[11:34] <jlu-hrz> I can create a VG: SYS_VG=$(maas ${PROFILE} volume-groups create ${HOST_ID} name="system-vg" partitions=$(echo ${SYS_VG_PARTITION} | jq '. | .id'))
[11:34] <jlu-hrz> I can create a LV: ROOT_LV=$(maas ${PROFILE} volume-group create-logical-volume ${HOST_ID} $(echo ${SYS_VG} | jq '. | .id') name="system-root" size=100G)
[11:35] <jlu-hrz> But how can i format this LV?
[11:35] <jlu-hrz> fail #1: creating a partition returns with: {"block_device": ["Cannot create a partition table on a logical volume."]}
[11:35] <zeestrat> jlu-hrz: Not sure if helpful but, after creating LV's, we read them with "maas PROFILE volume-groups read" to get their id, then format with "maas PROFILE block-device format SYSTEM_ID, LV_ID fstype=ext4
[11:35] <jlu-hrz> fail #2: to format the volume I need system_id, device_id, id. I have system_id and id, but what is the device_id?
[11:35] <jlu-hrz> -->   echo ${ROOT_LV} | jq {   "system_id": "eq6fr7",   "size": 99996401664,   "available_size": 99996401664,   "name": "system-vg-system-root",   "resource_uri": "/MAAS/api/2.0/nodes/eq6fr7/blockdevices/9/",   "uuid": "fff3f729-7811-4426-ba48-2ce74427eb58",   "used_size": 0,   "id": 9 }
[11:36] <jlu-hrz> @zeestrat: thanks I will try it...
[11:37] <zeestrat> jlu-hrz: Same goes for mounting. "maas PROFILE block-device mount SYSTEM_ID LV_ID mount_point=/your/mount/point"
[11:43] <jlu-hrz> maas ${PROFILE}  volume-groups read ${HOST_ID}
[11:43] <jlu-hrz>         "logical_volumes": [             {                 "block_size": 4096,                 "size": 99996401664,                 "available_size": 99996401664,                 "path": "/dev/disk/by-dname/system-vg-system-root",                 "model": null,                 "name": "system-vg-system-root",                 "filesystem": null,                 "used_size": 0,                 "type": "virtual",                 "id_path":
[11:43] <jlu-hrz>  maas test-ech167 partition format eq6fr7 4 fstype=ext4
[11:43] <jlu-hrz> --> Not Found
[11:44] <jlu-hrz> @zeestrat: doesn't work :-(
[11:47] <jlu-hrz> again (stripped...)
[11:47] <jlu-hrz> "logical_volumes": [ { "available_size": 99996401664, "system_id": "eq6fr7", "partition_table_type": null, "tags": [], "used_for": "Unused", "partitions": [], "resource_uri": "/MAAS/api/2.0/nodes/eq6fr7/blockdevices/9/", "id": 9 } ],
[11:47] <jlu-hrz>  maas test-ech167 partition format eq6fr7 9 fstype=ext4
[11:47] <jlu-hrz> --> Not Found
[11:48] <jlu-hrz> (looks better) but doesn't works as espected...
[12:01] <just_> hello to everyone
[12:01] <just_> is there any guy who can help me?
[12:02] <just_> hello???
[12:03] <jlu-hrz> @just_: we can help you. Please tess us your problem...
[12:03] <jlu-hrz> tell
[12:03] <Guest21969> Hi All, I have Asus hardware with SolarFlare NIC cards. PXE is able to assign IP address via DHCP server, but during deployment ipconfig does not work and hence iscsistart command fails. Any idea how can I configure MAAS to use custom drivers during OS install?
[12:05] <just_> Okay
[12:05] <just_> I have an installation of maas with version 1.95, we had restarted manually one hipervisor and now cloud-init cant give the ip to the node
[12:06] <just_> and its printing a lot of errors like this one
[12:06] <just_> handlers.py[WARNING]: failed posting event: start: modules-final/config-power-state-change: running config-power-state-change with frequency once-per-instance
[12:07] <just_> we cant reach the hipervisor and we cant connect, if we connect thought kvm i can reach the server
[12:07] <just_> but i cant ssh
[12:07] <just_> i have ubuntu 14
[12:08] <Guest21969> issue observed by me is similar to that reported in https://bugs.launchpad.net/maas/+bug/1442112
[12:08] <Guest21969> we are running MAAS version 2.1
[12:08] <Guest21969> any thoughts on what could be the possible issue?
[12:09] <just_> i've found this
[12:09] <just_> https://bugs.launchpad.net/maas/+bug/1663686
[12:10] <just_> wich OS do u have?
[12:11] <jlu-hrz> @Guest21969: Maybe this ist helpful.. http://stackoverflow.com/questions/35087666/how-to-upload-custom-boot-image-to-maas ?
[12:11] <Guest21969> jlu-hrz: I don't want to upload custom boot image, just want to use specific drivers for SolarFlare NICs
[12:13] <Guest21969> I am a little confused with the current situation, during commissioning ... network card gets detected and IP address is assigned to the commissioning OS, but drivers are not available during installation of OS
[12:13] <jlu-hrz> without drivers inside your initramfs you won't be able to start your nic's, right?
[12:13] <just_> @jlu-hrz do you have any advice for our problem?
[12:14] <Guest21969> I thought in settings there are options available to pass on special drivers for the h/w
[12:14] <just_> why we cant install maas 2.2 in ubuntu 14 tho?
[12:14] <jlu-hrz> you are not able to load any driver via network without your NICs .
[12:15] <jlu-hrz> right?
[12:15] <Guest21969> yes
[12:16] <Guest21969> everytime it fails during iscsi lun configuration, so I assume it is because of unable to connect to tgt server running on my MAAS server
[12:17] <jlu-hrz> are you able to install (temporary) an other NIC? (eg. USB-NIC)
[12:22] <just_> No one can help me?....
[12:22] <Guest21969> jlu-hrz: I don't have a USB NIC
[12:22] <Guest21969> server is located in the DC
[12:24] <jlu-hrz> are you able to connect to the server via SSH(KVM)-console?
[12:27] <just_> yes i am
[12:27] <just_> i can reach the machine with KVM
[12:27] <just_> interfaces are up too...
[12:29] <Guest21969> jlu-hrz: yes, I am able to connect to server via console
[12:31] <jlu-hrz> zeestrat: I got it: maas test-ech167 block-device format eq6fr7 9 fstype=ext4
[12:31] <jlu-hrz> thanks
[12:31] <just_> :(
[12:35] <jlu-hrz> Guest21969: are you able to switch to a rescue-console after error occured?
[12:36] <Guest21969> jlu-hrz: it takes me to initramfs prompt
[12:39] <Guest21969> is there any quick start on how to build custom MAAS images with custom drivers?
[12:41] <dakj> brendand, the directory is empty
[12:41] <brendand> dakj, really? even as maas says it's downloading?
[12:42] <brendand> dakj, with ls -a as well?
[12:43] <dakj> brendand, if I try to download 14.04 image the proceed is fine, 16.04 starts that and around 96% it stops.
[12:43] <dakj> brendand, sorry I saw the wrong path,
[12:43] <brendand> dakj, ok but i'm trying to find if it's fully downloaded on the region
[12:44] <dakj> brendand, there is that "snapshot-20170404-204225"
[12:45] <dakj> Brendan, have a look to my post (http://askubuntu.com/questions/899073/maas-dont-make-the-download-of-ubuntu-16-04-lts-image).
[12:47] <brendand> dakj, is the final status what's shown in the second screen?
[12:47] <brendand> dakj, i.e. 14.04 is synced and 16.04 is 'selected for download'?
[12:57] <zeestrat> jlu-hrz: Glad to hear.
[12:58] <Guest21969> any thoughts on how to build custom MAAS images?
[13:00] <jlu-hrz> Guest21969: Which OS?
[13:00] <dakj> Brendan, yes it's
[13:02] <jlu-hrz> ubuntu: https://ubuntuforums.org/showthread.php?t=1412132
[13:02] <dakj> Brendand, I've also to re-install all but same issue. I receive that when Canonical has published Openstack Autopilot in 16.04 with conjure-up. Before I never had issue like that
[13:03] <brendand> dakj, can you answer my question though?
[13:04] <Guest21969> jlu-hrz: thanks for the info. How can we push custom drivers within the image? Do you have any thoughts?
[13:05] <dakj> brendand, sure, yes  the second screen is the final status, and 14.04 is synced the 16.04 no
[13:05] <jlu-hrz> Guest21969: maybe this is a good starting point: https://cptyesterday.wordpress.com/2012/06/11/adding-non-free-drivers-to-a-debian-netboot-initrd/
[13:06] <brendand> dakj, did you try just restarting the image import?
[13:06] <brendand> i.e. click 'Save selection'?
[13:06] <dakj> brendand, yes I did that, and I try also to re-install all but nothing same problem
[13:08] <dakj> brendand, yes, I tried to make two test, first one selected only 16.04, and second one with 14.04. with 14.04 the procedure is completed with 16.04 no
[13:09] <dakj> brendand, if you want I can share my desktop with you via teamviewer!
[13:11] <jlu-hrz> Guest21969: have you tried different kernels? hwe etc.?
[13:12] <jlu-hrz> AFAIF "hwe" means hardware enhanced
[13:13] <brendand> jlu-hrz, no it means hardware enablement
[13:14] <jlu-hrz> brendand: Thanks. do you know if SolarFlare NICs are supported?
[13:14] <Guest21969> not tried with all, but can check
[13:14] <jlu-hrz> brendand: Thanks. Do you know if SolarFlare NICs are supported?
[13:15] <brendand> jlu-hrz, no i don't, but as you say, trying with a newer kernel may help
[13:17] <Guest21969> jlu-hrz: default seems to be hwe-t, what do you recommend?
[13:25] <mup> Bug #1680086 opened: [2.2, trunk] Discovery of machines in a Pod can have hostnames that colide <rsd> <MAAS:Triaged> <https://launchpad.net/bugs/1680086>
[13:27] <dakj> brendand, now I try to download the 14.04 and it results is in synced status, 16.04 continues to stay in "Selected for download"
[13:45] <cnf> has anyone deployed ESX nodes with MaaS ?
[13:57] <David_Orange> hello maas experts, i am facing something anoying on maas2.1.4. I am using MAAS to install a machine on a management network, then manually change its network configuration and change its vlan config in the switch, with a network not manage by maas. All those steps works fine, but at the reboot, the server is looping trying to reach maas with pxe. The only solution i found for now is to switch to management vlan, wait for pxe boot, then switch back to 
[14:00] <cnf> David_Orange: why would you do that?
[14:01] <mup> Bug #1667141 opened: [FFe] Standing FFe for MAAS 2.2 <maas (Ubuntu):New> <https://launchpad.net/bugs/1667141>
[14:01] <cnf> David_Orange: changing the network config, that is
[14:01] <pmatulis> dakj, can you elaborate on the connection with autopilot/conjure-up? are you using these things in any way?
[14:01] <cnf> David_Orange: just set the right config in maas
[14:03] <David_Orange> cnf: i want to do that to split networks for security reason. This new server shall also hosts a pxe server (maas or other), so i have to split networks
[14:03] <cnf> so why use maas on it, at all?
[14:04] <David_Orange> cnf: "on it" = on what ?
[14:04] <cnf> just install it manually
[14:04] <dakj> Pmatulis, at moment no, but my intention is to try that. if I can't download image of 16.04 I can deploy it to my node
[14:05] <David_Orange> cnf: this server is a remote server in a DC, i can not go there each time i need to install a new server
[14:05] <cnf> David_Orange: that is what IPMI is for
[14:06] <cnf> David_Orange: you are _already_ manually messing with switch configs and the likes, so it's mostly manually anyway
[14:06] <just_> hello to everyone....can someone help me?
[14:06] <just_> https://bugs.launchpad.net/maas/+bug/1663686
[14:06] <just_> im having this problem
[14:06] <just_> handlers.py failed posting event cloud-init maas
[14:07] <just_> i had restarted one hipervisor and now cloud-init cant give to him their IP
[14:07] <dakj> Pmatulis, I'm running a my old lab with a host where I installed 16.04 and MAAS, before the published of Autopilot, and the download and the sync of 16.04 is correct.
[14:07] <just_> and im unable to login into machine
[14:07] <cnf> David_Orange: maas kind of expects to be able to control the server, manually moving things around will break it
[14:08] <David_Orange> cnf: for the context, i works with narinder gupta on OPNFV, and i need to manage several pods. this is a need. and changing switch config is not something tricky in a SDN context
[14:08] <dakj> Pmatulis, in that host I don't run the last update
[14:08] <David_Orange> cnf: so maas is required at each boot ?
[14:08] <just_> no one can help me? :S
[14:09] <cnf> David_Orange: changing things manually isn't SDN :P
[14:09] <David_Orange> cnf: maas is forcing the boot routing to pxe only ?
[14:09] <cnf> but it sounds like you just want a PXE installer
[14:09] <cnf> not Metal as a Service
[14:10] <dakj> Pmatulis, this one is my old lab (http://pasteboard.co/Er1GuAYT.png) that one is new one (http://pasteboard.co/ErQvNtZ6.png), both are in the same network.
[14:11] <David_Orange> cnf: ok, it answers my question, MAAS is required at each start, thanks for your answer
[14:12] <cnf> i didn't say that, but i guess you have your answer
[14:12] <narinder> #topic MANO and various VNF use cases
[14:13] <David_Orange> cnf: so is there any configuration on maas for my need ?
[14:13] <cnf> depends on your need, like i said it sounds like you just want a PXE installer
[14:15] <David_Orange> cnf: lets say i just want to have a pxe installer for some nodes, and maas for others, MAAS2 can do it or not ?
[14:16] <cnf> you can hammer in a nail with a wrench, doesn't mean you should
[14:16] <cnf> i don't like "lets say"s
[14:16] <cnf> but just change your boot order, and be done with it
[14:17] <cnf> but imo, what you are doing is the wrong way about it
[14:17] <dakj> Pmatulis, why in the second lab the size of 16.04 is 468.1 MB while first one is 656.6 MB?
[14:20] <cnf> David_Orange: i would just leave the damn network settings, and put the MaaS / pxe network in port isolation
[14:20] <cnf> and stop all manual intervention
[14:24] <David_Orange> cnf: if it were only a problem of boot order, the failure of pxe would go to the disk after... and it does not, it loop on requesting pxe to maas
[14:26] <David_Orange> cnf: and "put the MaaS / pxe network in port isolation" will requires that the node will have an access to my maas network and my other network, thing that i do not want
[14:26] <cnf> it would boot from disk
[14:26] <cnf> David_Orange: no, it doesn't...
[14:27] <cnf> it would have access to your MaaS controller
[14:27] <cnf> nothing else
[14:27] <cnf> that's what port isolation is for
[14:29] <David_Orange> cnf: i need to bring access to this node without give access to all this network node
[14:29] <cnf> yes
[14:29] <cnf> that's what port isolation is for :P
[14:29] <cnf> https://en.wikipedia.org/wiki/Private_VLAN
[14:33] <David_Orange> cnf: thanks, i will see if that can fit our needs
[14:34] <cnf> gl
[15:01] <mup> Bug #1680119 opened: maas should enable netconsole during commissioning <MAAS:Triaged> <https://launchpad.net/bugs/1680119>
[15:45] <dakj> Pmatulis, third installation on another Host in a different network.....same issue with 16.04
[15:47] <pmatulis> dakj, the thing is that if there was a systematic problem of downloading 16.04 images with maas then there would be a large outcry. it seems this is due to a local network problem. i'll ping you when i do my own tests on 2.1
[16:16] <mup> Bug # changed: 1575631, 1633696, 1639839, 1642728, 1661581, 1662948, 1670429, 1670444, 1672718, 1674720, 1674807, 1675095, 1675427, 1675432, 1675468, 1675823, 1675838, 1675844, 1675953, 1676619, 1676921, 1676969, 1676978, 1677029, 1677333, 1677350, 1677573, 1677631, 1677658, 1677713, 1677741,
[16:16] <mup> 1678038, 1678188, 1678236, 1678298, 1678333, 1679231, 1679247, 1679249, 1679315, 1679427
[16:22] <sarah__> Hello Im testing MaaS on some virtual machines  with virtualbox and I just couldnt figure out the power type I should be using
[16:22] <tychicus> when commissioning new nodes I am seeing a few minutes worth of these errors: [  148.510201] cloud-init[2197]: request to http://10.10.10.12/MAAS/metadata//2012-01-01/ failed sleeping 1.: <urlopen error[Errno 111] Connection refused>
[16:23] <sarah__> the nodes are all marked ready and when I try to commission them it asks me for a power type
[16:23] <sarah__> I tried manual but it doesnt work
[16:24] <dakj> Pmatulis, so 12.04 is fine 14.04 is fine, 16.04, 16.10 and 17.04 no. Are they any different repo to make the download?
[16:28] <tychicus> the node eventually finishes commissioning successfully, but it add a few minutes to the total commissioning time of each machine
[16:30] <tychicus> looks like it may be a similar issue to https://bugs.launchpad.net/maas/+bug/1354309
[16:41] <tychicus> also looks similar to this https://bugs.launchpad.net/maas/+bug/1321417
[16:41] <tychicus> I running 2.1.3+bzr5573-0ubun
[17:02] <tychicus> looks like the issue was related to how the network cards were configured for the machine in MaaS
[17:04] <tychicus> this was a machine that had been previously commissioned, then marked as broken, then re-commissioned, even though one of the networks was marked as disconnected it was still getting an IP address, disabling DHCP on my "maas-external" fabric resolved the issue
[17:09] <pmatulis> dak...
[17:18] <dakj> pmatulis, I've resolved that, I don't know why for 14.04 yes and 16.04 no (I've to investigate), our Palo Alto Firewalls stopped that using the "Anti-spyware Protection Profile" identified that as a spyware.....removed the profile the download of 16.04 went fine!!!!
[17:19] <pmatulis> dakj, well there you go! a local network problem!
[17:20] <pmatulis> dakj, i'm glad you got it resolved
[17:20] <dakj> pmatulis, yes but it's strange that a firewall identify that as spyware, before that Canonical publi
[17:21] <dakj> Published that the firewall didn't block that
[17:21] <pmatulis> dakj, it would be good if you could get more info on that. are there detailed logs of some kind?
[17:22] <dakj> pmatulis, yes it's a promise......1 week ago I could to download via MAAS the 16.04 from this week no!!!!
[17:23] <dakj> pmatulis, I've to know why the image has been identified as spyware, and last week no!!!
[17:25] <dakj> pmatulis, anyway, thanks a lot for your support I hope to return you with a favour. See you soon with th upgrade
[17:53] <mup> Bug #1680175 opened: Traceback during upgrade from maas 2.1.3 to 2.2.0~rc1 <landscape> <MAAS:New> <https://launchpad.net/bugs/1680175>
[18:20] <mup> Bug #1677382 changed: [2.1.5] Failure to PXE boot Cavium crb-1s Servers - PXE-E99: Unexpected network error. Checkpoint D9 ERROR: Boot option loading failed Checkpoint AD <cdo-qa-blocker> <oil> <MAAS:Invalid> <MAAS 2.1:New> <https://launchpad.net/bugs/1677382>
[18:47] <mup> Bug #1679206 changed: [2.1.5] Maas fails to deploy hardware-ibm-power8-S822LC system with USB drive plugged in <cdo-qa-blocker> <oil> <curtin:Incomplete> <MAAS:Invalid> <https://launchpad.net/bugs/1679206>
[18:47] <mup> Bug #1680175 changed: Traceback during upgrade from maas 2.1.3 to 2.2.0~rc1 <landscape> <MAAS:Fix Released> <https://launchpad.net/bugs/1680175>
[19:25] <mup> Bug #1667141 changed: [FFe] Standing FFe for MAAS 2.2 <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1667141>
[20:11] <cmd_pancakes> Is it possible to deploy a node with a custom preseed config? or would i have to make a custom image for that
[20:44] <roaksoax> cmd_pancakes: custom preseed, yes
[20:44] <roaksoax> cmd_pancakes: /etc/maas/preseeds/curtin_userdata
[20:44] <roaksoax> would be for ubuntu
[20:44] <roaksoax> /etc/maas/preseeds/curtin_userdata_centos for cento,s etc
[20:51] <cmd_pancakes> roaksoax: ok great, thanks! i'll take a look
[20:52] <tychicus> I'm sure I am missing something in the docs, but how do you assign a fabric to particular network interface on a machine using the cli, I would think it is something like "maas $PROFILE interface update system_id id fabric=5"
[20:54] <tychicus> that command will return "Success" but not actually change anything
[20:54] <roaksoax> tychicus: maas <profile> interface update <syustem_id> <nic_id> vlan=<vlan id>
[20:54] <roaksoax> tychicus: 16:54 < tychicus> that command will return "Success" but not actually change anything -> can you file a bug for that ?
[21:00] <tychicus> roaksoax: thanks, that did the trick, it looks like as long as the system_id and nic_id are correct you can put in any arguments and it will always return "success"
[21:01] <tychicus> I'll get the bug filed
[21:03] <roaksoax> tychicus: thanks!
[22:23] <mup> Bug #1680266 opened: interface update will return successful with invalid params <maas (Ubuntu):New> <https://launchpad.net/bugs/1680266>
[23:17] <mup> Bug #1677382 opened: [2.1.5] Failure to PXE boot Cavium crb-1s Servers - PXE-E99: Unexpected network error. Checkpoint D9 ERROR: Boot option loading failed Checkpoint AD <cdo-qa-blocker> <oil> <MAAS:Triaged> <MAAS 2.1:New> <maas-images:New> <https://launchpad.net/bugs/1677382>
[23:17] <mup> Bug #1680266 opened: interface update will return successful with invalid params <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1680266>
[23:47] <mup> Bug #1680277 opened: [2.2rc1]  rackd — 75% connected to region controllers. <MAAS:New> <https://launchpad.net/bugs/1680277>
[23:47] <mup> Bug #1680278 opened: [2.2rc1] Failed to process message for node <MAAS:New> <https://launchpad.net/bugs/1680278>