Red Hat Bugzilla – Bug 1340902
There is no limit on container images concurrent SSAs
Last modified: 2018-04-17 04:02:39 EDT
Description of problem: vm SSA implements several different load factors based on resource e.g concurrent_per_ems, concurrent_per_host Container Image scanning currently does not have this behavior and when a user defines a scheduled provider scan all images, what ever their number might be, are scanned simultaneously. A large number of images will potentially cause a load issue on both the containers provider and the ems Version-Release number of selected component (if applicable): darga-1-rc1.1 How reproducible: 100% Steps to Reproduce: 1. Select all images in the UI => Perform Smart State Analysis 2. Go to task => all vm & container analysis tasks Actual results: All jobs are started at once Expected results: The user should be able to define a load_factor. No more then load_factor ssa per on provider should be allowed to run simultaneously. Additional info:
Fix suggested upstream: https://github.com/ManageIQ/manageiq/pull/8760
To verify this change on qe, two things must be verified: 1. The new limit on parallel execution of container image scans works as expected. At most 3 scans run together (run all and check out "All vm and container analysis tasks"). The number can be changed in the configuration through container_scanning -> concurrent_per_ems 2. The scanning and concurrency of vms was not effected.
Verified. Steps to verify: Modified configuration in: container_scanning -> concurrent_per_ems (default was =3, changed it to =2) Added 4 new apps in Openshift (each app used a new image) Viewed Settings --> Tasks. Two new images were scanned at any one time. Once scan was completed, two new images were scanned.
Hi Einat, did you test vm scanning concurrency as well? (See my previous comment) that would probably reuire some help
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-2016:1348