Description of problem: Upstream -> http://talk.manageiq.org/t/problem-with-files-discover/375 VMs scans do not use the VM Sample profile which would seem like the obvious choice. You need to copy the profile and name it as default. In addition, you need to set the files collected to be true. Please note there is a issue using wildcards (/etc/*.conf) which seems to be broken and requires each file to be added individually until it is fixed. Then future scans will start to pick up these files specfied. feedback Thanks, renaming scan profile to 'default' helped. However, this means that there can only be one profile for VMs, which is a restraint for the customer. I've found a bug about wildcards (https://bugzilla.redhat.com/show_bug.cgi?id=1160855), but couldn't find a bug about renaming profile to 'default'. If you have a link to that bug, could you please share it with me so I can keep an eye on it. Version-Release number of selected component (if applicable): 5.3.0 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Josh, there is a misconception with VM scan profiles in the description of the bug. Different scan profiles can be assigned through policy using the "VM Analysis Start" event and the "Assign Profile to Analysis Task" action. If this is not configured then the default scan profile will be used if it exists.
Need to document that a user needs to create a 'default' profile that they can then configure as to what should be collectedd by default. Else the system falls back to a internal default that the user can not see nor edit. In addition, like GM mentions in comment 3, if the user sets up control policies to scan vms, they can select the profile in the triggered actions.
Assigning to Shikha for review.
Moving to NEW to be reviewed as the schedule allows.
Assigning to Deepti for review. Deepti, it looks like we need to add a prerequisite or note based on Comment 3 and Comment 4 to the following procedure: https://access.redhat.com/documentation/en/red-hat-cloudforms/version-4.1-beta/managing-infrastructure-and-inventory/#sect_analyzing_virtual_machines_and_templates We should also confirm whether the same procedure should be applied for analyzing instances and images.
Moving back to the default assignee to be re-triaged as the schedule allows.