helm: rendered manifests contain a resource that already exists

Not specified by the original author.

TL;DR

Helm refuses to create a resource that exists outside its release: someone created it manually or another release owns it. Either adopt it into the release with the Helm ownership annotations, or delete the stray resource. The install proceeds once ownership is unambiguous.

Error

helm: rendered manifests contain a resource that already exists

Steps

1. Identify the conflicting resource: the error names its kind, name, and namespace. Expected: you know exactly which object collides.
2. Check who owns it: look for Helm release annotations on the object. Expected: either no annotations (manually created) or another release's annotations.
3. Adopt it: add the Helm release name and namespace annotations (and the managed-by label) to the existing object so Helm takes ownership. Expected: Helm recognizes it as part of the release.
4. Or delete the stray: if the object is genuinely unwanted, delete it and let Helm create it fresh. Expected: no conflict on the next install.
5. Re-run the helm install or upgrade. Expected: the release deploys without the conflict.

When to use

• Helm install fails with "already exists"
• Resources created manually before Helm adoption
• Migrating to Helm from kubectl-applied manifests

When not to use

• Chart template rendering errors (different phase)
• A different release legitimately owning the resource (coordinate, don't steal)

Tool compatibility

• Helm release ownership annotations; helm install, helm upgrade

Variant phrasings

helm adopt existing resource

Annotate it with the release identity; Helm then manages it going forward.

resource already exists helm install

Decide: adopt or delete. Helm will not silently take over unowned objects.

Why it happens

Helm tracks ownership per object via annotations. An object created outside Helm has no owner, and Helm's default is to fail rather than adopt implicitly, because silently taking over someone else's resource would be dangerous.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthYiOKU9FA6CWXnQVQRywQ

Resolved from the public thread: https://vectle.com/posts/psthYiOKU9FA6CWXnQVQRywQ

Thread query: helm: rendered manifests contain a resource that already exists

TL;DR: Helm refuses to create a resource that exists outside its release: someone created it manually or another release owns it. Either adopt it into the release with the Helm ownership annotations, or delete the stray resource. The install proceeds once ownership is unambiguous.

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

Use this when

• You see this exact message or symptom in Grafana: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Resolved from the public thread: https://vectle.com/posts/pstk-eRC4Bu0As5Te-8FolyQ

Thread query: Grafana provisioning error: dashboard with the same uid already exists folder mismatch on startup

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

Use this when

• You see this exact message or symptom in Metabase: Metabase serialization import failed: dashboard entity already exists with different collection on site export load
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Metabase fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Metabase admin panel, the question page, and the serialization export log and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the saved question SQL or query builder definition, the dashboard parameter mapping, the database connection, and the collection the entity belongs to, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Metabase itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the card from the dashboard, run its question alone, fix the query or mapping, then reload the dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the card returning rows on the dashboard and the parameter filtering the connected cards as expected. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Metabase serialization import failed: dashboard entity already exists with different collection on site export load

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Metabase version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does metabase serialization import failed: dashboard entity already exists with different collection on site export load keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Metabase 49 or later (open source or Pro), dashboard subscriptions and serialization, native SQL questions. The steps assume you can read the job or build log and change the named object in Metabase.

Why it happens

In Metabase, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kn1ZXtXx8LskBM75NOnIBA

Resolved from the public thread: https://vectle.com/posts/pst_kn1ZXtXx8LskBM75NOnIBA

Thread query: Metabase serialization import failed: dashboard entity already exists with different collection on site export load

TL;DR: Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.