Skip to content

[bug] A replace of another deployment's backup says to reconnect AI providers it keeps #4813

Open

Description

@Quick104

What happened

A full restore (silo backup restore, replacing the live database) of another deployment's backup tells the operator that the AI providers were cleared and must be entered again. A few steps later, the same restore keeps the live server's own AI providers and job bindings. The operator is told to reconnect providers that still work.

This follows PR #4800. That PR adds one more input that prints the line: a backup with another SECRET_KEY whose AI job bindings survive. For that input, main already lists ai.providers in the "Cleared N encrypted settings this SECRET_KEY cannot read; enter them again" line.

Steps to reproduce

  1. Take a backup on server A with an AI provider connected.
  2. On server B, which has its own AI provider connected, run silo backup restore --from <A's backup> --accept-lost-credentials (replace mode; a backup from another server needs the flag).
  3. Read the output. It includes "Cleared the backup's credentials for outside services this server does not have, and turned them off; enter them again to use them: AI providers."
  4. Start Silo and open AI Services. Server B's provider and job bindings are still there.

Expected behavior

The output lists only what the restored server will actually be missing. In this case that excludes the AI providers, which come from the live server.

Silo version / commit

main at dec9d15

Deployment

Not deployment-specific.

Area

Backups and restore

Clients affected

  • Other/not client-specific

Relevant logs

No logs available. A Postgres-backed scratch run of the replace with another key printed the outbound line on the #4800 branch and kept the live provider and text binding.

Technical notes

  • In carryLiveState (internal/backup/swap.go), a backup from another deployment carries with carryFrom = "". CarryOutboundSettings (internal/backup/settings_outbound.go) then clears the AI providers' bundle and reports it as cleared.
  • carryServerSpecificSettings runs next and copies the live server's ai.providers, ai.text_provider_id, ai.speech_provider_id, recommendations.embedding_provider_id, ai.auth_mode, and ai.chatgpt.*. These keys are SettingKindServerSpecific in internal/backup/settings_classes.go.
  • Possible repair: don't report a bundle as cleared when every key the report is about will come from the live server, or build the report after the server-specific carry.

Source: found in review of #4800

AI harness

Claude Code in T3 Code

AI tool(s)

Claude Code; T3 Code delegated review task (Codex)

AI model(s)

claude-opus-5-5; gpt-6.2-sol (review)

AI involvement

Fully AI-generated. Traced in source by the agent, with a scratch test run by the reviewer; not verified by a person.

Independent or adversarial review

Found by the background review of #4800 (gpt-6.2-sol); the agent checked it against the source on main.

Confirmations

  • I searched open and recently closed issues and pull requests, and this is not already reported
  • I reproduced this myself on a real deployment
  • Any logs provided are raw apart from marked redactions and are not AI-summarized; if none were available, I said so above

Activity

  1. added
    impact: polishAnnoyance, cosmetic, or nice-to-have
    priority: P2Limited scope, workaround exists, or polish
    triagedHigh-confidence review completed; does not mean fixed, validated, or accepted for release.
    on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingimpact: polishAnnoyance, cosmetic, or nice-to-havepriority: P2Limited scope, workaround exists, or polishtriagedHigh-confidence review completed; does not mean fixed, validated, or accepted for release.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions