GitLab

On moria1, my v3 cert was going to expire soon, so I made a new one. At the same time, I decided to upgrade to git master (0.2.8.0-alpha-dev (git-d939a83f5bc8ccf3)).

Now, each hour when moria1 tries to vote, it instead says

Nov 24 01:55:01.628 [notice] Time to compute a consensus.
Nov 24 01:55:01.687 [info] networkstatus_compute_consensus(): Generating consensus using method 20.
Nov 24 01:55:01.807 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=20194094 M=3719276 E=1504624 D=7084460 T=32502454
Nov 24 01:55:01.849 [warn] ID on signature on network-status vote does not match any declared directory source.
Nov 24 01:55:01.853 [info] dump_desc(): Unable to parse descriptor of type v3 networkstatus. See file unparseable-desc in data directory for details.
Nov 24 01:55:01.853 [err] networkstatus_compute_consensus(): Bug: Generated a networkstatus consensus we couldn't parse. (on Tor 0.2.8.0-alpha-dev d939a83f5bc8ccf3)
Nov 24 01:55:01.857 [warn] Couldn't generate a ns consensus at all!
Nov 24 01:55:01.858 [info] networkstatus_compute_consensus(): Generating consensus using method 20.
Nov 24 01:55:01.970 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=20194094 M=3719276 E=1504624 D=7084460 T=32502454
Nov 24 01:55:02.020 [warn] ID on signature on network-status vote does not match any declared directory source.
Nov 24 01:55:02.021 [err] networkstatus_compute_consensus(): Bug: Generated a networkstatus consensus we couldn't parse. (on Tor 0.2.8.0-alpha-dev d939a83f5bc8ccf3)
Nov 24 01:55:02.027 [warn] Couldn't generate a microdesc consensus at all!
Nov 24 01:55:02.027 [warn] Couldn't generate any consensus flavors at all.

Now I have one of these v3 consensus documents sitting in my $datadir/unparseable-desc. It looks pretty normal.

I wonder if we broke "moving to a new certificate" somewhere in there?