Skip to main content

Retry secrets a key rotation failed to move

On the Migrate step of a key rotation, secrets that aren't in NodeVault yet move straight onto the new key. A secret that fails to move is listed with the reason, and each one has its own Retry. Retry them before you close the rotation.

Who can do this: an Org Owner or Org Admin, on a plan that includes NodeVault.

Retry a failed move​

  1. In the sidebar, select Settings, then Features, then NodeVault. A rotation still open shows Rotate key and its steps.
  2. If the rotation is on Migrate, tick the secrets to move and select Move with their count, such as Move 3. Select Skip instead to move none. While they move, the step shows Moving credentials and a progress bar.
  3. Read the counts on Migrate, or later on Result: Moved to NodeVault, Skipped and Failed to move. Failed to move turns red when it is above 0.
  4. Find the Failed list under the counts. Each secret shows its name and why it failed. Without a reason it reads The move failed. Retry.
  5. Fix what the reason names first. If the screen says Waiting for a node that holds the key to come online., start one of your nodes.
  6. Select Retry beside the secret. The counts update when it moves.
  7. Repeat for each secret in the list.
  8. When the rotation has finished, select Done.

Once Done is selected, the result closes and its Retry buttons go with it. To move a secret that is still left out, see Move a secret into NodeVault. If the screen says Couldn’t retry. Try again., select Retry again. If the whole rotation failed, the list has no Retry: start the rotation again, as in Rotate the NodeVault key.

Secrets under Not rekeyed​

Not rekeyed is a different list. It holds NodeVault secrets that no node could re-seal under the new key. These have no Retry. Each one reads Re-enter the secret to move it to the current key., or a reason. Open the secret and type its value again, as in Replace or delete a secret. Saving it seals it under the current key.