GB-237: admission cannot write the partner into the role core's zenoh_sovereign_peerings¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-237 is printed by goatbuilder. The same text offline: goat explain GB-237 or goatbuilder explain GB-237.
What it means¶
On a goat-zenoh role core, phase 10's admission writes the partner's zenoh_sovereign_peerings entry (sovereign, and the CN of the agreement's access-control fragment subject) into ops/ansible/group_vars/<core router group>/peerings.yml, the role's own declaration, beside the fragment. It could not: the fragment names no subject CN or several, another of the group's group_vars files already sets zenoh_sovereign_peerings (two owners), an entry's sovereign is a template (it contains {{, {% or {#, so no literal id matches it and the partner would be added a second time), peerings.yml cannot be rewritten without changing something else (admission replaces only the zenoh_sovereign_peerings block and keeps every other line of the file byte for byte, so it refuses a comment inside that list, a flow-style top level it cannot split into variables, or an anchor shared between the list and another variable), or peerings.yml is not YAML or not a mapping of variables. Nothing on the core changed.
Why it happens¶
- a comment inside the zenoh_sovereign_peerings list of peerings.yml, a flow-style top level, or an anchor in the list that another variable aliases
- zenoh_sovereign_peerings is set by hand in another file of the core router group's group_vars
- an entry of zenoh_sovereign_peerings writes its sovereign as a Jinja template, or is not a mapping with a literal sovereign
- zenoh_sovereign_peerings itself is a template, a mapping or a scalar, not a literal list: read as empty, it would be written back holding this partner alone
- the fragment phase 9 rendered names no subject, or several
What to do¶
One line per step or alternative:
move a comment out of the zenoh_sovereign_peerings list (above it, or elsewhere in the file), write the file one `variable: value` block per variable, and keep anchors out of the list
move the zenoh_sovereign_peerings entries into group_vars/<core router group>/peerings.yml and remove the variable from the other file
write zenoh_sovereign_peerings as a literal list, and each entry's sovereign literally, as the partner's sovereign id
run phase 9 again, then make a new plan and deploy
Read more¶
Exit code¶
goatbuilder exits with 2.