[tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-----------------------------------------------+---------------------------
 Reporter:  asn                                |          Owner:  asn
     Type:  defect                             |         Status:
                                               |  needs_information
 Priority:  Immediate                          |      Milestone:  Tor:
                                               |  0.3.2.x-final
Component:  Core Tor/Tor                       |        Version:  Tor:
                                               |  0.3.0.6
 Severity:  Blocker                            |     Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID:                                     |         Points:  1.5
 Reviewer:                                     |        Sponsor:  SponsorV
-----------------------------------------------+---------------------------

Comment (by s7r):

 Tested this more again, on latest git master `0.3.3.0-alpha-dev (git-
 332d6bf9010fff1c)`. Things are a lot better:

 1. If I manually edit the state file and substitute the guard with
 `confirmed_idx=0` with a fingerprint that is not even in the current
 consensus, it will mark it as `unlisted_since` and proceed normally by
 moving to guard with `confirmed_idx=1` and successfully build circuits,
 without any complaints in the log file. This is the expected behavior, and
 it works in both scenarios:
 a) when DataDirectory folder contains current consensus and microdescs;
 b) when DataDirectory folder only contains the state file (cached
 consensus and microdescs deleted on purpose)

 2. If I manually edit the state file and substitute all 3 confirmed guards
 with fingerprints that do not exist, Tor will mark them as
 `unlisted_since` and move on with other listed guards that are available,
 without any complaints in the log file. This also works as expected in
 both scenarios described above.

 On previous tests, this was enough to get in the state where it never
 stops complaining about missing descriptor for some of our primary guards
 and not being able to build circuits.

 Now I need to find a way to somehow test with a guard that appears in the
 consensus but for which a valid descriptor can't be found.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21969#comment:54>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online