Missing KeptnAppVersion/KeptnWorkloadVersion span when one of the lifecycle phases fails

[odubajDT]

Description

In the current state, when one of the phases fails (it does not matter whether on KeptnApp or KeptnWorkload level) the KeptnAppVersion span is not ended properly (and missing completely), which leads to a wrong child/parent structure when reviewing the results in Jeager or Grafana. The same problem is present for KeptnWorkloadVersion span, when one of the KeptWorkload phases fail.

Failure on KeptnApp level

Failure on KeptnWorkload level

Expected behavior

The spans should be correctly formatted and the KeptnAppVersion/KeptnWorkloadVersion span should exist even if the deployment of the application fails.

[thisthat]

it is unclear to me what do you mean by "correctly formatted". We do not have client/server types so there is no need for a child to finish before a parent.

[odubajDT]

it is unclear to me what do you mean by "correctly formatted". We do not have client/server types so there is no need for a child to finish before a parent.

True, we can then format the problem that the KeptnAppVersion span is missing.