-
Bug
-
Resolution: Not A Defect
-
Major
-
$ anchore-cli system status
Service analyzer (61470748-b796-4901-aded-3a4ca537f8c8, N/A): up
Service analyzer (c32c3eaf-399b-42d8-9b19-58a92aada103, N/A): up
Service analyzer (f3926a02-e166-4698-9b5b-7849a29e47aa, N/A): up
Service analyzer (1870d9d9-9ce0-44dd-b193-4d0ab064d018, N/A): up
Service policy_engine (anchore_core_service, http://anchore-engine-anchore-engine:8087): up
Service kubernetes_webhook (anchore_core_service, http://anchore-engine-anchore-engine:8338): up
Service analyzer (a14c242a-206d-43a4-af61-f325dbdfe0d8, N/A): up
Service catalog (anchore_core_service, http://anchore-engine-anchore-engine:8082): up
Service apiext (anchore_core_service, http://anchore-engine-anchore-engine:8228): up
Service simplequeue (anchore_core_service, http://anchore-engine-anchore-engine:8083): up
Engine DB Version: 0.0.5
Engine Code Version: 0.1.10
Jenkins ver 2.125
Anchore plugin ver 1.0.16$ anchore-cli system status Service analyzer (61470748-b796-4901-aded-3a4ca537f8c8, N/A): up Service analyzer (c32c3eaf-399b-42d8-9b19-58a92aada103, N/A): up Service analyzer (f3926a02-e166-4698-9b5b-7849a29e47aa, N/A): up Service analyzer (1870d9d9-9ce0-44dd-b193-4d0ab064d018, N/A): up Service policy_engine (anchore_core_service, http://anchore-engine-anchore-engine:8087): up Service kubernetes_webhook (anchore_core_service, http://anchore-engine-anchore-engine:8338): up Service analyzer (a14c242a-206d-43a4-af61-f325dbdfe0d8, N/A): up Service catalog (anchore_core_service, http://anchore-engine-anchore-engine:8082): up Service apiext (anchore_core_service, http://anchore-engine-anchore-engine:8228): up Service simplequeue (anchore_core_service, http://anchore-engine-anchore-engine:8083): up Engine DB Version: 0.0.5 Engine Code Version: 0.1.10 Jenkins ver 2.125 Anchore plugin ver 1.0.16
When I run a jenkins job using the anchore plugin, it submits it correctly but fails to load and parse the result.
Attached are logs from the core, and jenkins plugin as well as the json resulting from this curl.
curl -v -u admin:foobar "http://anchore.platform.vivint.com/v1/images/sha256:1e459072023393e9632e98961d84eccdf9ab926ce8e9aa55403fc4ec7610a914/check?tag=tp-registry.vivint.com:5005/test/vivint-base-prod:16.feature-pl-5600-anchore-3268de8&detail=true&policyId=2c53a13c-1765-11e8-82ef-23527761d060"
[JENKINS-52681] Anchore plugin fails with JSON error
Ben Mathews
added a comment - I installed w/ the achore helm chart which at the time specified an older version. The helm chart has since been upgraded and all is working properly. Thanks.
https://github.com/helm/charts/tree/master/stable/anchore-engine
Ben Mathews
added a comment - I installed w/ the achore helm chart which at the time specified an older version. The helm chart has since been upgraded and all is working properly. Thanks.
https://github.com/helm/charts/tree/master/stable/anchore-engine 
benm, looks like your setup has the most updated Jenkins plugin release but a really old version of anchore engine (0.1.10). Current anchore engine release version is 0.2.3. This matters since the Jenkins plugin uses API to interact with anchore engine. "Security" tab of the Anchore build report is a new plugin feature that queries the anchore engine for vulnerabilities and renders the results. In this case the API response to vulnerability listing from the anchore engine is not what the plugin expects and hence the error in anchoreplugin.log. You might want to consider upgrading anchore engine for the Security tab results in the Anchore report.
However, this error should not impact the rendering of the Anchore report for the Jenkins build. The Anchore report should display a "Policy" tab that contains a summary and detailed policy evaluation results. Let us know if this is not the case.