[tor-bugs] #23605 [Core Tor/Tor]: expired consensus causes guard selection to stall at BOOTSTRAP PROGRESS=80

[Tor Bug Tracker & Wiki]

#23605: expired consensus causes guard selection to stall at BOOTSTRAP PROGRESS=80
-------------------------------------------------+-------------------------
 Reporter:  catalyst                             |          Owner:
                                                 |  catalyst
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.4.0.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  bootstrap, clock-skew, tor-guard,    |  Actual Points:
  usability, ux, s8-errors, 035-roadmap-         |
  subtask, 035-triaged-in-20180711,              |
  s8-bootstrap                                   |
Parent ID:  #28018                               |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor8
-------------------------------------------------+-------------------------

Comment (by teor):

 Replying to [comment:18 catalyst]:
 > Replying to [comment:17 teor]:
 > > catalyst, does your bootstrap stage rewrite cover this ticket?
 > If you mean the part where obtaining "enough" directory info improperly
 reports that we're starting a connection when we might do no such thing,
 I'm pretty sure #27167 fixes that.  (The behavior is an instance of
 #27308, which #27167 partially fixes.)

 So we can close this ticket when #27167 closes?
 (And un-parent any child tickets we still want to do.)

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