Description of problem: In both scan jobs (vm scan / container scan) started_on is always empty Version-Release number of selected component (if applicable): 5.5 How reproducible: 100% As far as I can tell Steps to Reproduce: 1. execute a vm scan job / container scan job 2. go to configure -> tasks -> 'all vm analysis tasks' OR check the DB table 'jobs' Actual results: - Started ui column is always displayed empty - DB:jobs.started_on is always empty Expected results: started_on should container job start time. Additional info: github issue: https://github.com/ManageIQ/manageiq/issues/5659
Sorry for not responding sooner. I tried to reproduce every now and then but was unable to run a vm scan. Following input from Hui this might be relevant only to container scan
Mooli, now that we use the dispatcher, is this fixed? do_dispatch and assign_proxy_to_job should set started_on.
Yes it is resolved on master. Moving to on qa since I beleive they should have the fix already. Please correct if that is wrong.
Created attachment 1186005 [details] Start time showing in Tasks. Verified. When running Perform Smart State analysis" then, Tasks -- All VM Analysis Tasks shows start time.