Skip to content

GB-351: a Spock subscription has forward_origins set, which in a mesh replicates in a loop

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

What it means

A Spock subscription, or the setting that creates them, has forward_origins other than empty or 'none'. In a mesh of three or more sites such a subscription passes each change on to the next site, which passes it back, without end, while every subscription still reads replicating and nothing is logged. The spock-forward-origins-check role stopped the run before spock-mesh-peering or ory-narrow-repset changed anything. The message names the setting, or each subscription as <host> <database>.<subscription>.

Why it happens

  • a site's group_vars set spock_mesh_forward_origins or ory_spock_forward_origins
  • a subscription was created by hand with forward_origins := '{all}'

What to do

One line per step or alternative:

remove spock_mesh_forward_origins and ory_spock_forward_origins from the site's group_vars (both default to [])
on the host and database named, run SELECT spock.sub_drop('<subscription>'); then run the playbook again, which creates it with forward_origins empty

Read more

Exit code

goatbuilder exits with 2.