GB-288: a health publisher a joining site declares has no play in the checkout¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-288 is printed by goatbuilder. The same text offline: goat explain GB-288 or goatbuilder explain GB-288.
What it means¶
join-node deploys each health publisher the end-state model marks present at a joining site (endstate.py model <site>, from the pin table) after the site's data router, by running the publisher's play limited to the node. The model marks a publisher present whose play (ops/ansible/<publisher>-deploy.yml) is not in this checkout, so the plan was refused before any phase ran.
Why it happens¶
- the checkout is an older or partial tree that does not carry the publisher's play
- the pin table declares a publisher at the site that the site does not mean to run
What to do¶
One line per step or alternative:
run join-node from a checkout that carries ops/ansible/<publisher>-deploy.yml
declare the publisher absent at the site in ops/pins/fleet-pins.yaml, with its reason: components: <publisher>: deviations: <site>_hosts: {absent: true}
goatbuilder endstate <env> shows what the model marks present at each site
Read more¶
Exit code¶
goatbuilder exits with 1.