maatuska wrongly reported as missing from the consensus

maatuska changed keys yesterday and has since then been reported as not part of consensus a couple of times.

added component::metrics utilities priority::medium resolution::not a bug status::closed type::defect labels

Looks good to me now? At least, moria1 thinks maatuska is producing signatures.

This warning is not about producing signatures. Everything's working fine there with maatuska. The warning is about maatuska not having the Authority flag for some reason:

r maatuska UUzQQ39D3f+lLcM6LRNq5lB9wlc 4+uI2VVFedIKQxEGYix1ZlJ6NU0 2012-09-29 10:00:38 171.25.193.9 80 443
a [2001:67c:289c::9]:80
s HSDir Running Unnamed V2Dir Valid
v Tor 0.2.4.3-alpha-dev
w Bandwidth=20
p reject 1-65535

Not sure what's the issue there, but I think the consensus-health checker is correct. Closing as not a bug.

Trac:
Resolution: N/A to not a bug
Status: new to closed

Sure enough, maatuska doesn't have the Authority flag.

Also it has the Unnamed flag.

I have some maatuska descriptors at moria1 with the right key:

fingerprint BD6A 8292 55CB 08E6 6FBE 7D37 4836 3586 E46B 3810

and some with a new key!

fingerprint 514C D043 7F43 DDFF A52D C33A 2D13 6AE6 507D C257

Karsten: we might want to make consensus-health scream if an authority has a different relay identity key than expected -- it will mean clients will refuse to talk to it because they'll think they're getting mitmed.

Replying to arma:

Karsten: we might want to make consensus-health scream if an authority has a different relay identity key than expected -- it will mean clients will refuse to talk to it because they'll think they're getting mitmed.

Done. With the current consensus, consensus-health would emit the following error: ERROR: The following relays running on the IP address and dir port of authorities are using different relay identity keys than expected: maatuska

Replying to arma:

Sure enough, maatuska doesn't have the Authority flag.

Thanks! Very helpful service, I must say.

closed