Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start a smartstate analysis of a container image
2. Go to Config > Tasks > All Other Tasks
No container image SSA task is present.
Container image SSA task is present.
The smartstate analysis task of a container image is displayed under "All VM Analysis Tasks" (Config > Tasks > All VM Analysis Tasks).
IMHO, that's the right place to present these tasks since afaik they fall under 'analysis' tasks category, rather than 'ui' jobs (displayed in "All Other Tasks").
Looked at Tasks screen, on My/All VM Analysis Tasks screen data comes from 'jobs' table that i think only has Smartstate Analysis records only. My/All UI Tasks tabs are populated with data from 'miq_tasks' table that has all other UI tasks that are queued. So Container Image Smartstate Analysis tasks should show up on Analysis Tasks tabs. Let me know if you have any further questions.
Thanks for the clarification Harpreet.
So, as I wrote in my last comment, I don't think this should be considered a bug since the tasks are shown in Analysis tab.
Does anyone thinks otherwise?
I think we should change the tab title to "My/All SmartState Analysis Tasks" since this would also solve the click-through problem described in https://bugzilla.redhat.com/show_bug.cgi?id=1274375.
(In reply to Thom Carlin from comment #5)
> I think we should change the tab title to "My/All SmartState Analysis Tasks"
> since this would also solve the click-through problem described in
Thom, in case nobody else already addressed this, we'll handle the renaming of "My SmartState Analysis Tasks" => "All SmartState Analysis Tasks" in this BZ.
Fixed with: https://github.com/ManageIQ/manageiq/pull/5880
Container image task now shows up in tab that has been renamed to:"All VM Analysis Tasks"
It appears that this bug should no longer be documented as a known issue. Removing doc text and resetting requires_doc_text flag.
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.