Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect cumulus dashboard status #54

Open
frankinspace opened this issue Feb 12, 2025 · 0 comments · Fixed by #57
Open

Incorrect cumulus dashboard status #54

frankinspace opened this issue Feb 12, 2025 · 0 comments · Fixed by #57
Assignees
Labels
bug Something isn't working

Comments

@frankinspace
Copy link
Member

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.

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.

@frankinspace frankinspace added the bug Something isn't working label Feb 12, 2025
@frankinspace frankinspace self-assigned this Feb 12, 2025
@frankinspace frankinspace linked a pull request Feb 12, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant