Bug #20002
closedISE on /foreman_tasks/dynflow/ when some invalid plans are in place
Description
How reproducible:
under special circumstances
Steps to Reproduce:
1. trigger a task
2. force kill the dynflow executor process
3. while the task is runnint, delete data from dynflow manually (CAUTION: THIS IS BY NO MEANS A RECOMMENDED WAY OF DEALING WITH TASKS - FOR REPRODUCER PURPOSES ONLY):
psql foreman
delete from foreman_tasks_locks;
delete from dynflow_steps;
delete from dynflow_actions;
exit
note we are not deleting dynflow_execution_plans and foreman_tasks_tasks
4. restart the foreman-tasks service
5. go to /foreman_tasks/dynflow
Actual results:
internal server error
Excpeted results:
the rows with invalid tasks are shown, not internal server error appears
Updated by Lukas Pramuk over 7 years ago
- Copied from Bug #19146: World invalidation can fail, when execution plans are invalid added
Updated by Lukas Pramuk over 7 years ago
We need to get this fixed also for execution plans index - /foreman_tasks/dynflow/
After creating invalid worlds (see description) the page is throwing "Internal Server Error"
#19146 missed to fix it
Updated by Ivan Necas over 7 years ago
- Subject changed from World invalidation can fail, when execution plans are invalid to ISE on /foreman_tasks/dynflow/ when some invalid plans are in place
- Description updated (diff)
- Status changed from Closed to New
Updated by Ivan Necas over 7 years ago
- Target version deleted (
1.12.4) - Translation missing: en.field_release deleted (
261)
Updated by Ivan Necas over 7 years ago
- Bugzilla link changed from 1390931 to 1343617
Updated by Adam Ruzicka about 7 years ago
- Status changed from New to Closed
Closing since the issue should not be present anymore.