Opened 13 months ago

Last modified 2 months ago

#27448 assigned defect

router_have_consensus_path() logs an incorrect "no exits in consensus"

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: fast-fix, teor-backlog-fast-fix
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Instead, it should distinguish between:

  • exit flags, but no (usable) exit descriptors, and
  • no exit flags

Child Tickets

Change History (6)

comment:1 Changed 10 months ago by teor

Parent ID: #27402

Does #27402 fix this issue as well?

comment:2 Changed 9 months ago by teor

Parent ID: #27402

It does not, but we should backport #27402 before backporting this patch.

comment:3 Changed 7 months ago by teor

Keywords: fast-fix added

We need to fix "The current consensus has no exit nodes" and "no exits in consensus, using mid".

comment:4 Changed 7 months ago by teor

Milestone: Tor: 0.3.4.x-finalTor: unspecified

comment:5 Changed 3 months ago by teor

If there are Exit flags in the consensus, we should say: "waiting for Exit descriptors"
If not, we should say: "no Exits in consensus"

comment:6 Changed 2 months ago by teor

Keywords: teor-backlog-fast-fix added
Owner: teor deleted

This ticket is not on our roadmap, but I could fix it quickly.

Note: See TracTickets for help on using tickets.