You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing @ymchenjpl noticed that the ingest status of workflows that execute the browse image step function do not have their status reported correctly in the Cumulus Dashboard. The dashboard shows the workflow as "Running" even after it completes.
When I compare the Cumulus OPS BrowseImageWorkflow old bignbit v1.0 execution output json for an Opera HLS granule (see attached) with the Cumulus UAT BrowseImageWorkflow new bignbit v2.2 execution output json for an Opera HLS granule (see 2nd attachment), I see the bottom of the new bignbit v2.2 json doesn't have a section for:
| cumulus_meta
|-- execution_name
|-- parentExecutionArn
|-- queueURL
like the old bignbit v1.0 json file has.
During testing @ymchenjpl noticed that the ingest status of workflows that execute the browse image step function do not have their status reported correctly in the Cumulus Dashboard. The dashboard shows the workflow as "Running" even after it completes.
This missing
cumulus_meta
is likely the reason the status on the dashboard is not updating.It looks like in 0.1.2 we were keeping that section in the output:
https://github.com/podaac/bignbit/blob/0.1.2/terraform/state_machine_definition.tpl#L435
But in 0.2.2 it is not being retained:
https://github.com/podaac/bignbit/blob/0.2.2/terraform/state_machine_definition.tpl#L434-L452
The
cumulus_meta
should be kept in order to ensure proper tracking in the cumulus dashboard.The text was updated successfully, but these errors were encountered: