Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #34037
Closed
Open
Created Apr 28, 2020 by teor@teor

Make chutney check tor's logs for reachability self-test success

This ticket is an alternative to legacy/trac#33582 (moved) or legacy/trac#33222 (moved).

Instead of fixing bridge descriptor uploads, we can check bridge logs to make sure that reachability self-tests have succeeded.

For consistency, we should also do the same checks for relays.

We can only do these tests on authorities, relays, and bridges that are configured with AssumeReachable 0. Chutney's current defaults are:

  • directory authorities: 1
  • bridge authorities: 1
  • relays: 0
  • bridges: 0
  • clients: clients never perform reachability self-tests

Some custom chutney networks may set AssumeReachable 1 for relays and bridges. So we should make it easy for them to disable these checks.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking