circpadding: Middle node did not accept our padding request

While trying to get logs for legacy/trac#30992 (moved), my client started emitting those:

[warn] Middle node did not accept our padding request.

The context is that a normal client (git master) is trying to reach a service that is under heavy load as in quite unreachable.

I've managed to catch info logs of this from the bootstrap of the client up to the warning.

changed milestone to %Tor: unspecified in legacy/trac

added 041-backport in Legacy / Trac 041-deferred-20190719 in Legacy / Trac 042-should in Legacy / Trac 044-deferred in Legacy / Trac component::core tor/tor in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac owner::mikeperry in Legacy / Trac priority::medium in Legacy / Trac regression in Legacy / Trac severity::normal in Legacy / Trac status::assigned in Legacy / Trac tor-circpadding in Legacy / Trac type::defect in Legacy / Trac labels

Trac:
info.log

Trac:
Keywords: tor-circpadding deleted, tor-circpadding 041-backport 041-should? 041-regression added

I am tentatively labeling this 041-must?, but we can downgrade it if it turns out not to be a serious bug.

Mike, could you please have a look at this?

Trac:
Owner: N/A to mikeperry
Status: new to assigned
Milestone: Tor: 0.4.2.x-final to Tor: 0.4.1.x-final
Keywords: tor-circpadding 041-backport 041-should? 041-regression deleted, tor-circpadding 041-backport 041-should? 041-must? 041-regression added

Add 041-deferred-20190719 tag to 041-should tickets I am deferring today.

Trac:
Keywords: tor-circpadding 041-backport 041-should? 041-must? 041-regression deleted, 041-backport, 041-regression, 041-must?, 041-should?, 041-deferred-20190719, tor-circpadding added

Trac:
Milestone: Tor: 0.4.1.x-final to Tor: 0.4.2.x-final

Mike took a look at this during PETS and I don't think he considers it a serious bug. The warning has also been downgraded to protocol warn in 041 as part of legacy/trac#30649 (moved).

I leave the ticket open so that Mike can summarize what he found out in case it's a bug that needs to be fixed, but I'm removing it from the 041 milestone.

Trac:
Keywords: 041-regression, 041-must?, 041-should? deleted, N/A added

Add keyword to unmarked regression defects in 0.4.2.

Trac:
Keywords: N/A deleted, regression added

Mark some assigned tickets as 042-should.

Trac:
Keywords: N/A deleted, 042-should added

Trac:
Milestone: Tor: 0.4.2.x-final to Tor: 0.4.4.x-final

Add 044-must to all "regression" tickets in 0.4.4

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Trac:
Keywords: N/A deleted, 044-deferred added
Milestone: Tor: 0.4.4.x-final to Tor: unspecified

moved from legacy/trac#31002 (moved)

added Bug label and removed 1 deleted label

added Deferred Padding Regression labels and removed 1 deleted label

No progress reported for 9 months; unassigning. Please feel free to re-assign if you want to pick this up again.

unassigned @mikeperry

removed milestone

mentioned in issue #40359 (closed)

mentioned in issue torspec#39

@mikeperry, if you get a chance and you remember what you found out about this ticket, please summarize what you found as discussed above? Closing for now.

closed