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

Task execustion view report wrong status #5183

Closed
michael-wirth opened this issue Jan 13, 2023 · 5 comments
Closed

Task execustion view report wrong status #5183

michael-wirth opened this issue Jan 13, 2023 · 5 comments
Assignees
Labels
introduced-in: 2.10.0 status/need-triage Team needs to triage and take a first look
Milestone

Comments

@michael-wirth
Copy link
Contributor

michael-wirth commented Jan 13, 2023

Description:
The "Task executions" view shows the wrong status for RUNNING tasks. They are reported as "ERROR"/
The detail view shows the correct status as "RUNNING". The tasks run fine. No, errors in the logs.

Release versions:
Fails in 2.10.0
Was ok in 2.9.6

Screenshots:
2023-01-13_13-17

image

@github-actions github-actions bot added the status/need-triage Team needs to triage and take a first look label Jan 13, 2023
@markpollack markpollack added this to the 2.10.1 milestone Jan 17, 2023
@cppwfs
Copy link
Contributor

cppwfs commented Jan 17, 2023

@claudiahub Will verify that the UI is refreshing the state of the task execution list first.

@claudiahub
Copy link

claudiahub commented Jan 18, 2023

On the UI we're reading the status property which seems to be not aligned to the model defined for the Task Executions list.
This should be TaskExecutionStatus as I dig into the TaskDefinitionResource class.
@cppwfs Can you please confirm this property TaskExecutionStatus is the correct one for the list on this page ?

@cppwfs
Copy link
Contributor

cppwfs commented Jan 19, 2023

@michael-wirth Has paymentorderloader been launched multiple times? If so has any of the executions errored?

@michael-wirth
Copy link
Contributor Author

michael-wirth commented Jan 19, 2023

@cppwfs
Yes, the loader was started twice (because it reported the status as ERROR). Both tasks were running in parallel and succeeded without error.

The same behavior is observed with only 1 task running. I wonder where the ERROR status is coming from.
It is not set in the backend response, but the status is set to ERROR in the frontend model.

2023-01-19_09-03

2023-01-19_09-05

@michael-wirth
Copy link
Contributor Author

michael-wirth commented Jan 19, 2023

The UI seems to set status code to ERROR if the exitCode is not 0, but the task is running and the exitCode is not yet set. I would expect the STATUS should be RUNNING or at least UNKNOWN.

2023-01-19_09-17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
introduced-in: 2.10.0 status/need-triage Team needs to triage and take a first look
Projects
None yet
Development

No branches or pull requests

5 participants