Red Hat Bugzilla – Bug 1438601
Handle issues with loading execution_plan
Last modified: 2017-09-14 04:47:01 EDT
There are various reasons that can cause the execution plan for a task not being available. We should still try to not fail completely at those situations and try to show at least the data we have available in foreman_tasks_tasks table. How to reproduce: Follow http://projects.theforeman.org/issues/19146 for reproducer steps and go to the tasks details pages after doing so. Expected results: the tasks page is still showing at least some data, not failing completely. Current results: the tasks page is broken, returning 500 status code
Created from redmine issue http://projects.theforeman.org/issues/19147
Upstream bug assigned to inecas@redhat.com
An example of such an error might be: Oops, we're sorry but something went wrong Value (NilClass) '' is not any of: Dynflow::ExecutionPlan::Steps::Abstract.
*** Bug 1438928 has been marked as a duplicate of this bug. ***
*** Bug 1406168 has been marked as a duplicate of this bug. ***
VERIFIED. @satellite-6.2.10-3.0.el7sat.noarch tfm-rubygem-foreman-tasks-0.7.14.14-1.el7sat.noarch using manual reproducer described in comment#0: 5. Navigate to /foreman_tasks/tasks REPRO: (x) Oops, we're sorry but something went wrong Value (NilClass) '' is not any of: Dynflow::ExecutionPlan::Steps::Abstract. vs. FIX: Actions::Katello::Repository::CapsuleGenerateAndSync N/A Actions::Katello::Repository::Sync N/A Actions::Katello::Repository::Sync N/A >>> Tasks page/detail renders and tasks are listed even if there are invalid tasks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1553
*** Bug 1400688 has been marked as a duplicate of this bug. ***