Bug 1395632 - Cannot analyze non docker images
Summary: Cannot analyze non docker images
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.8.0
Assignee: Erez Freiberger
QA Contact: Einat Pacifici
URL:
Whiteboard: container:smartstate
: 1396141 1408981 (view as bug list)
Depends On:
Blocks: 1348610 1400615 1403354
TreeView+ depends on / blocked
 
Reported: 2016-11-16 10:22 UTC by Pavel Zagalsky
Modified: 2020-03-11 15:23 UTC (History)
14 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1400615 1403354 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:26:08 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1348610 0 medium CLOSED Docker Image Scanning is not working with proxy to access Image Registry 2021-02-22 00:41:40 UTC

Internal Links: 1348610

Description Pavel Zagalsky 2016-11-16 10:22:50 UTC
Description of problem:
After initiating SmartScan Analysis on a docker image the scan concludes with:
"cannot analyze non docker images" message

Version-Release number of selected component (if applicable):
5.7.0.10

How reproducible:
Always

Steps to Reproduce:
1. Add a docker.io image to a pod in OpenShift
2. Go to that container image and initiate a SmartScan Analysis
3.

Actual results:
The user will see the following message in Tasks menu:
"cannot analyze non docker images"

Expected results:
The scan should run successfully

Additional info:
The log shows the following information:

[----] E, [2016-11-16T04:41:39.731551 #2871:899144] ERROR -- : Q-task_id([d34c1cc2-abe0-11e6-a2c0-001a4a1697bb]) MIQ(ManageIQ::Providers::Kubernetes::ContainerManager::Scanning::Job#process_abort) job aborting, cannot analyze non docker images
[----] E, [2016-11-16T04:41:39.756713 #2871:899144] ERROR -- : Q-task_id([d34c1cc2-abe0-11e6-a2c0-001a4a1697bb]) MIQ(MiqQueue#deliver) Message id: [24904], Error: [undefined method `[]' for nil:NilClass]
[----] E, [2016-11-16T04:41:39.756921 #2871:899144] ERROR -- : Q-task_id([d34c1cc2-abe0-11e6-a2c0-001a4a1697bb]) [NoMethodError]: undefined method `[]' for nil:NilClass  Method:[rescue in deliver]
[----] E, [2016-11-16T04:41:39.757103 #2871:899144] ERROR -- : Q-task_id([d34c1cc2-abe0-11e6-a2c0-001a4a1697bb]) /var/www/miq/vmdb/app/models/manageiq/providers/kubernetes/container_manager/scanning/job.rb:195:in `cleanup'

Comment 3 Jaroslav Henner 2016-11-23 14:16:28 UTC
I have set this as a blocker to make sure we won't let out the CFME which would fail with the new docker. We surely don't want this to happen.

Comment 5 Erez Freiberger 2016-12-04 09:25:37 UTC
*** Bug 1396141 has been marked as a duplicate of this bug. ***

Comment 7 Federico Simoncelli 2017-06-08 16:31:49 UTC
*** Bug 1408981 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.