[BUG-NOK] Orchestrator - Discrepancy in "Deployed" / "Status" between "Deployment Packages" / "Deployments"

[ss5829]

Bug Description

When a deployment package is deployed to a cluster / host, sometimes the deployments errors out due to various reasons / setup issues.
It is during these times a discrepancy can be observed between the "Deployments" & "Deployment Packages" sections.

which is, the "Deployed" field in the "Deployment Packages" section shows "Yes" with a green icon,

whereas the "Status" field in "Deployments" section shows error related to the deployment issue along with "Running Instances" as "0/0"

ideally both should show the actual status of the deployment.

System Setup

Open Edge Orchestrator v3.1.2

Reproducible Steps

create a deployment package.
perform deploy operation & make it error out. (introduce an error during the deployment)
wait for the deployment error to show in the "Status" of "Deployments" section, "Running Instances"
cross-verify it with the "Deployed" field of "Deployment Packages" section

Root Cause Analysis

No response

[scottmbaker]

We discussed this and we feel the status is working as expected, but the header in the table is misleading. the "Deployed" bit is used to flag Deployment Packages that are in use, so that they cannot be modified while they are deployed. This includes when the deployment is in error, and even deployments that are sent to edge nodes that might not be online and/or automated deployments to edge that might not exist yet.

We feel changing the field header from "Deployed" to "In Use" will clarify this, and it can be done as a straightforward task in the GUI and the CLI (if necessary). API changes would be disruptive, so I am not suggesting any API changes.

[soniabha-intc]

@ss5829 Do you agree with the analysis above?