Bug 1396141 - Smart State Analysis fails on containers
Summary: Smart State Analysis fails on containers
Keywords:
Status: CLOSED DUPLICATE of bug 1395632
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
: cfme-future
Assignee: Erez Freiberger
QA Contact: Pavel Zagalsky
URL:
Whiteboard: container:smartstate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-17 14:33 UTC by Victor Estival
Modified: 2017-05-08 10:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-04 09:25:37 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log (6.45 MB, application/zip)
2016-11-17 14:33 UTC, Victor Estival
no flags Details
New 5.7.0.11 log with the errors (177.98 KB, application/zip)
2016-11-18 06:27 UTC, Victor Estival
no flags Details

Description Victor Estival 2016-11-17 14:33:20 UTC
Created attachment 1221591 [details]
log

Description of problem: I cannot scan any container in OCP


Version-Release number of selected component (if applicable): 5.6.2.2 , but it happens the same in other environment I have with 5.7.0.5


How reproducible: Deploy CF and link it to OCP


Steps to Reproduce:
1.
2.
3.

Actual results: No container is 


Expected results:


Additional info:
I verified I´m not affected by https://bugzilla.redhat.com/show_bug.cgi?id=1336183. This environment can be accessed from the Red Hat VPN

Comment 2 Victor Estival 2016-11-17 14:44:50 UTC
Hello, sorry I didn´t mention: I tried with two different OCP + CF environments (both OCP are 3.3 though) with the same results

Comment 3 Victor Estival 2016-11-17 14:53:25 UTC
Sorry I click publish too early

Description of problem: I cannot scan any container in OCP from CFME. I tried in two different environments with the same results. 


Version-Release number of selected component (if applicable): 5.6.2.2 , but it happens the same in other environment I have with 5.7.0.5. OCP version is 3.3. 


How reproducible: Deploy CF and link it to OCP


Steps to Reproduce:
1.
2.
3.

Actual results: No image is scanned by CFME


Expected results: Imaged to be scanned by CFME


Additional info:
I verified I´m not affected by https://bugzilla.redhat.com/show_bug.cgi?id=1336183. This environment can be accessed from the Red Hat VPN

Comment 4 Federico Simoncelli 2016-11-17 15:15:45 UTC
Erez, this may be a duplicate.

Comment 5 Dave Johnson 2016-11-17 21:02:56 UTC
This should be fixed in 5.7.0.10... please retest.  There was an issue in RH SCL rpms, the latest ones should resolve this, please reopen if not.

Comment 6 Victor Estival 2016-11-18 06:27:00 UTC
I just deployed 5.7.0.11 and it still fails. I cannot attach the new log

Comment 7 Victor Estival 2016-11-18 06:27:20 UTC
I just deployed 5.7.0.11 and it still fails. I cannot attach the new log

Comment 8 Victor Estival 2016-11-18 06:27:52 UTC
Created attachment 1221743 [details]
New 5.7.0.11 log with the errors

Comment 9 Erez Freiberger 2016-11-18 09:31:44 UTC
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1395632

Please try this fix: https://github.com/ManageIQ/manageiq/pull/12711

Comment 11 Satoe Imaishi 2016-11-18 15:36:14 UTC
If this is a duplicate, can we close this BZ?

Comment 12 Victor Estival 2016-11-18 15:46:22 UTC
IMHO we should verify this is a duplicate before we close it, because I'm not 100% sure it is

Comment 13 Erez Freiberger 2016-11-18 15:57:41 UTC
I think that they are duplicated because they both fail on "cannot analyze non docker images" and they are both with docker version docker-common-1.10.3-57.el7.x86_64 (please correct me if i am wrong) which has the new 'docker-pullable://' image id prefix.

Comment 14 Erez Freiberger 2016-12-04 09:25:37 UTC

*** This bug has been marked as a duplicate of bug 1395632 ***


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