New commit detected on ManageIQ/manageiq/gaprindashvili: https://github.com/ManageIQ/manageiq/commit/7ca3a3086135373e9e9d5562353817083c7fbe3a commit 7ca3a3086135373e9e9d5562353817083c7fbe3a Author: Brandon Dunne <brandondunne> AuthorDate: Mon Apr 30 16:19:12 2018 -0400 Commit: Brandon Dunne <brandondunne> CommitDate: Mon Apr 30 16:19:12 2018 -0400 Merge pull request #17331 from hsong-rh/scanning_profile Fix the issue of defined analyisis profile missed in vm scanning. (cherry picked from commit 792f495c208c4bfd07eb7da2654e294159a6ad95) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1578121 app/models/vm_scan.rb | 1 + 1 file changed, 1 insertion(+)
Hi Hui, My understanding was that with this bug fix, the dependency of the profile name "default" will be removed. That is, the profile can be named other than "default". I tested the VM SSA file collection on CFME-5.9.3, using these instructions, and profile named "test1": https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/assigning_a_custom_analysis_profile_to_a_virtual_machine However, still the files are not collected. Changing the profile name into "default" made the file collection work. Can you please advise? btw, In the above link, 3. Creating a Virtual Machine Control Policy It seems that Action "Assign VM analysis profile..." was replaced with: "Annotate image with scan results..." (See attached screenshot actions.png) Can you please confirm? Shall I open a doc bug on this? Thanks.
Created attachment 1442279 [details] actions.png
Hi Ilanit, Your understanding is correct. The fix should honor the defined profile. In your attached screen shot, you should choose the action you just created, as the doc says. (I made the same mistake as you in the beginning).
Hui, Thanks a lot. With profile named other than "default", along with fixing the action just created, VM scan does collect the files. Thus moving bug to verified.
Filed this bug to prevent the confusion mentioned in comment 5: Bug 1583633 - [Docs] Assign-profile-analysis-task-action confusing documentation.
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/RHSA-2018:2184