[tor-bugs] #4011 [Tor Relay]: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has a normal consensus

[Tor Bug Tracker & Wiki]

#4011: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has
a normal consensus
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  major      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:  Tor: 0.2.3.3-alpha
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by arma):

 To be clear, this bug only hits us when we have an up-to-date-enough ns-
 flavor consensus but not microdesc-flavor consensus. This could happen on
 startup if we have a cached-consensus file but no cached-microdesc-
 consensus file. Or it could happen during regular operation if we try to
 fetch both and we successfully get the ns-flavor one but the
 mirror/authority we happen to pick fails to give us a microdesc-flavor
 one. Intended behavior is that we'd retry the microdesc-flavor one
 immediately, but the 'if' would cause us to bail instead.

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