[tor-bugs] #33407 [Core Tor/Tor]: Make chutney bridge authorities publish bridges in their networkstatus-bridges

[Tor Bug Tracker & Wiki]

#33407: Make chutney bridge authorities publish bridges in their networkstatus-
bridges
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.4.4.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ipv6, prop311, tor-bridge, chutney,  |  Actual Points:
  outreachy-ipv6                                 |
Parent ID:  #33050                               |         Points:  1
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor55-can
-------------------------------------------------+-------------------------

Old description:

> Chutney bridge authorities don't have any bridges in their networkstatus-
> bridges. That's a problem, because we want to check networkstatus-bridges
> for the reachability checks in #33232.
>
> Here's what we need to do:
> * fix bugs in tor or chutney that stop bridges posting their descriptors
> to the bridge authority (#33582)
> * fix bugs in tor or chutney that stop the bridge authority writing
> bridges to the networkstatus (maybe it doesn't respect AssumeReachable?)
> * grep the bridge's logs for its reachability tests
>
> If we end up fixing tor, chutney will need to know which tor versions
> have these fixes (otherwise old branches will fail CI). So we may need
> some kind of environmental variable, tag, or version update. (See
> #33408.)
>
> We don't have to do these fixes, because it should be enough to test
> relay reachability. But we would risk breaking bridge reachability tests,
> and not knowing about it until after a release.

New description:

 This chutney fix is blocked by a tor bridge bootstrap / descriptor upload
 race condition, see #33582.

 (Chutney may need to check for this tor bug fix. One way to do that is to
 modify the tor version EXTRA_INFO so it is sortable, see #33408.)

 Chutney bridge authorities don't have any bridges in their networkstatus-
 bridges. That's a problem, because we want to check networkstatus-bridges
 for the reachability checks in #33232.

 Here's what we need to do:
 * fix bugs in tor or chutney that stop bridges posting their descriptors
 to the bridge authority (#33582)
 * fix bugs in tor or chutney that stop the bridge authority writing
 bridges to the networkstatus (maybe it doesn't respect AssumeReachable?)
 * grep the bridge's logs for its reachability tests

 If we end up fixing tor, chutney will need to know which tor versions have
 these fixes (otherwise old branches will fail CI). So we may need some
 kind of environmental variable, tag, or version update. (See #33408.)

 We don't have to do these fixes, because it should be enough to test relay
 reachability. But we would risk breaking bridge reachability tests, and
 not knowing about it until after a release.

--

Comment (by teor):

 Here's a clearer explanation:

 Currently blocked by a tor bridge bootstrap / descriptor upload race
 condition, see #33582.

 Chutney may need to check for this tor bug fix. One way to do that is to
 modify the tor version EXTRA_INFO so it is sortable, see #33408.

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