Skip to content

GB-269: a secret for the node still holds a secret store's reference

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

What it means

A value join-node hands to a node, such as the first-login password phase 2 seeds the SSH key with, still begins with a secret store's reference (op://, bao://, bw:// or the declared ref_prefix) after the secrets injector ran. Sent as it is, the node would take the reference as the secret. Nothing was sent to the node. The message names the variable and the scheme, never the reference.

Why it happens

  • the store's tool is not signed in, so with-secrets could not resolve the reference
  • the variable was set to a reference under a store that resolves none (env, env-file)

What to do

One line per step or alternative:

sign in to the declared store's tool (for 1password: op signin), then re-run: goatbuilder join-node <environment> --site <site> --node <node> --class <class> --address <address> --from 2
or export the value itself in the variable the message names

Read more

Exit code

goatbuilder exits with 1.