Skip to content

GB-274: the two sides derived different acceptance sessions

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-274 is printed by goatbuilder. The same text offline: goat explain GB-274 or goatbuilder explain GB-274.

What it means

Both sides of a peering work out the same acceptance session from the agreement each holds and an attempt number, with no file between them (docs/design/federation-acceptance.md §6.2). The partner's session is not the same as ours: the refusal names the members that differ. Nothing is combined with a partner on another session.

Why it happens

  • the two sides hold different agreements: the digests read aloud at phase 6 differ, or one side composed again since
  • the two sides are on different attempts
  • a session file was edited, so its digest no longer covers its members

What to do

One line per step or alternative:

compare the agreement digest and the attempt number with the partner on the call
run phase 14 again on both sides with the same attempt

Read more

Exit code

goatbuilder exits with 2.