[2.0b5] request to http://192.168.10.27:5240/MAAS/metadata/status/4y3he8/latest failed

Connecting a rack controller with a region controller succeeds, however, there are errors in the logs that never go away:

==> /var/log/maas/rackd.log <==
2016-05-14 04:36:12+0000 [-] updated clock skew to -41
2016-05-14 04:36:12+0000 [-] request to http://192.168.10.27:5240/MAAS/metadata/status/4y3he8/latest failed. sleeping 16.: HTTP Error 401: OK

==> /var/log/syslog <==
May 14 04:36:12 ubuntu sh[6722]: 2016-05-14 04:36:12+0000 [-] updated clock skew to -41
May 14 04:36:12 ubuntu sh[6722]: 2016-05-14 04:36:12+0000 [-] request to http://192.168.10.27:5240/MAAS/metadata/status/4y3he8/latest failed. s$eeping 16.: HTTP Error 401: OK
May 14 04:36:12 ubuntu sh[6722]: 2016-05-14 04:36:12+0000 [-] updated clock skew to -41

IN the region controller:

2016-05-14 12:35:35 [-] 127.0.0.1 - - [14/May/2016:04:35:35 +0000] "GET /MAAS/rpc/ HTTP/1.0" 200 436 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"
2016-05-14 12:35:47 [-] 192.168.10.3 - - [14/May/2016:04:35:47 +0000] "POST /MAAS/metadata/status/4y3he8/latest HTTP/1.1" 401 37 "-" "Python-urllib/3.5"
2016-05-14 12:35:47 [-] 192.168.10.3 - - [14/May/2016:04:35:47 +0000] "POST /MAAS/metadata/status/4y3he8/latest HTTP/1.1" 401 37 "-" "Python-urllib/3.5"

How to reproduce:

1. deploy a machine with MAAS
2. configure the deployed machine to:
2.1 install shared secret echo <secret> | maas-rack install-shared-secret
2.2 point to MAAS (maas-rack config --region-url http://<maas-ip>:5240/MAAS
3. watch logs:
on rack tail -f /var/log/rackd.log /var/log/syslog
on region /var/log/regiond.log

4. Note that the rack is successfully connected, it successfully downloaded images, and successfully configured services.