GB-188: the plan no longer holds¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-188 is printed by goatbuilder. The same text offline: goat explain GB-188 or goatbuilder explain GB-188.
What it means¶
Immediately before anything changes, deploy runs the planner's live recheck: every live prerequisite is checked again and every input section is compared with a plan built now. Something did not hold (a section changed, a check was not PASS or NOT APPLICABLE or was not answered, or the plan was not READY), so the approved plan no longer describes the change, and a saved plan is not proof the environment stayed the same. Nothing changed.
Why it happens¶
- the agreement was composed again (a new package from either side)
- apply rendered the files again, or one was edited by hand
- the plan recorded a SKIP of a check deploy does not run again (host-allocation): the inventory names no host for this peering, or a value of another peering on a machine this peering shares does not resolve. The message says which, and what clears it
- a SKIP the plan accepted (plan --accept) reads differently now: the message names what it reads now and what was accepted
What to do¶
One line per step or alternative:
goatbuilder federate plan <partner> (a new plan from what is there now; approve its hash)
for a host-allocation SKIP, do what its line says first (goatbuilder federate allocate <partner>, or name the hosts in ops/ansible/inventory/peering-edges.ini, or set the named value in group_vars), then make a new plan: a new plan alone records the same SKIP
goatbuilder federate plan <partner> --accept host-allocation (when you have judged that SKIP: it is recorded with its exact detail, and deploy goes ahead only while it reads the same)
Read more¶
Exit code¶
goatbuilder exits with 1.