Tony has reported that in some rare occurences, RefreshPeer creates
authorThierry Parmentelat <thierry.parmentelat@sophia.inria.fr>
Tue, 12 Apr 2011 15:26:47 +0000 (17:26 +0200)
committerThierry Parmentelat <thierry.parmentelat@sophia.inria.fr>
Tue, 12 Apr 2011 15:26:47 +0000 (17:26 +0200)
commit83fe6b6b3571d190b525e46d30b0df05e552d76e
tree054cd73faee64d2df89735a71b635dc717b7dcbb
parent391429f2ea44117ee1c6c8699018aca26140a603
Tony has reported that in some rare occurences, RefreshPeer creates
nodes that should be remote but remain local
protect the fragment that sets host's hrn
in the case reported by Tony, this fails with, apparently,
the peer's 'hrn_root' being None
this change does not fix the first cause for that, but at least should
let RefreshPeer finish its job cleanly (but with a missing hrn though)
PLC/Peers.py