[BUG-NOK]: Unable to Install Observability Extension Package – "AlreadyExists" Error

[sangeer2310]

Bug Description

While attempting to install the Observability Extension package from the Intel Orchestrator UI, the installation fails with the following error:
"message": "rpc error: code = AlreadyExists desc = confused the target Deployment: the deployment package forbids multiple deployment package but there are multiple deployments for the deployment package"

Software Version

v2026.0

Operating System

Ubuntu 22.04 (LTS)

System Setup

Hardware: AlderLake (13th Gen Intel(R) Core(TM) i9-13900E)
OS: Ubuntu 22.04.5 LTS
Kernel: 6.8.0-52-generic

K3s Configuration:
Kubernetes: K3s v1.33.5+k3s1
topology-manager-policy: best-effort
cpu-manager-policy: static
reserved-cpus: "1"

Reproducible Steps

Navigate to the Extension Packages
Select the Observability Extension package.
Deploy and proceed with the default deployment configuration.

Expected Result:
The Observability Extension package should be installed successfully

Investigation Performed

• Verified that there is no existing reference for the Observability package in the database.
• Verified that there is no existing reference on the device.
• Checked the events and relevant Kubernetes resources.
• Verified the observability-related pods, namespaces, storage resources, and CRDs.
• No existing Observability deployment/package instances were found.

[sys-emf]

Thank you for your contribution! Please make sure to review our Contributing Guide.

[jgespino]

Hi @sangeer2310

I tried to reproduce the issue but wasn’t able to. I also successfully deployed the observability extension package on two clusters across different EMF instances.

Could you please help confirm the following details?

• Does this behavior happen only on this edge node/cluster, or have you seen it on others as well?
• Which cluster template are you using? I tested with the privileged-k3s template, version v0.0.10.
• Under Deployments, do you see any deployments using the package name "observability"?
• Under Deployment Packages > Extensions, do you see observability marked as in use?

Regards,
Jesus

[sangeer2310]

Hi @jgespino
Thanks for checking

• I used the privileged-k3s template, version v0.0.10
• I checked the environment and none of the deployments are using the observability package
• Under Deployment Packages > Extensions, the observability package is not marked as "In Use"

Additionally, we created a new project and were able to deploy the observability extension package successfully there. The issue appears to persist only for this specific project. Based on this behavior, we suspect there may be some stale data that was not cleaned up properly in the database or cache for the affected project.