GB-187: the plan is not the one approved¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-187 is printed by goatbuilder. The same text offline: goat explain GB-187 or goatbuilder explain GB-187.
What it means¶
The plan deploy was given is for another peering, or its hash changed between approval and execution (it is read again under the peering's lock, just before anything changes). Nothing changed. A plan that does not match its own hash is GB-201.
Why it happens¶
- no plan has been made yet (<work>/plan.json is missing)
- the plan was made again, or edited, after it was approved
- --plan names another peering's plan
What to do¶
One line per step or alternative:
goatbuilder federate plan <partner> (then read it and approve its hash)
Read more¶
Exit code¶
goatbuilder exits with 1.