Skip to content

GB-307: an environment declares converger pull-agent, and the pull converger is not built

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

What it means

goatbuilder.yaml declares converger: pull-agent for this environment, one of its sites or one of their classes. No pull converger is built: no agent on a machine fetches and applies its class's release. The only converger on real hosts is push, and pushing to machines declared to pull would change what the declaration means once pull is built. So doctor refuses the environment, and deploy (its dry run too), release's deploy rungs, fastlane's deploy and rollback refuse it before any step. deploy --verify-only reads and is not refused; validate accepts the value, and --mock converges it on a fixture.

Why it happens

  • the environment, a site or a class was declared pull-agent ahead of the pull converger

What to do

One line per step or alternative:

declare converger: push-ansible for these machines in ops/goatbuilder/goatbuilder.yaml until the pull converger is built
goatbuilder doctor --env <environment> (the env:<name>:converger row names each place pull-agent is declared)

Read more

Exit code

goatbuilder exits with 2.