Bug 1715417

Summary:	Applicable Errata do not report CVEs values
Product:	Red Hat Satellite	Reporter:	Andrea Perotti <aperotti>
Component:	Reporting	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	inecas, mhulan, mshira, oprazak, wpinheir
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-26 10:43:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrea Perotti 2019-05-30 10:02:15 UTC

Description of problem:

"Applicable Errata" template for reporting engine report an incorrect value for CVEs. was expecting something like "CVE-2018-12126 , CVE-2018-12127" , etc but instead I got something like an index: 4168, "4156,4157" .

Version-Release number of selected component (if applicable):
satellite-6.5.0-11.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Generate "applicable errata", no filter

Actual results:

Host,Operating System,Environment,Erratum,Type,Published,Applicable since,Severity,Packages,CVEs,Reboot suggested
bugs.example.local,RedHat 7.6,Library,RHSA-2019:0818,security,2019-04-23,2019-04-23 23:54:12 +0200,Important,"bpftool,kernel,kernel-abi-whitelists,kernel-debug,kernel-debug-devel,kernel-devel,kernel-doc,kernel-headers,kernel-tools,kernel-tools-libs,kernel-tools-libs-devel,perf,python-perf","4156,4157",true
bugs.example.local,RedHat 7.6,Library,RHSA-2019:1022,security,2019-05-07,2019-05-08 00:06:29 +0200,Important,python-jinja2,4168,false

Expected results:

To have CVE-2018-xxxx CVE-2019-yyyy rather than what looks like an index

Comment 3 Shira Maximov 2020-05-26 10:43:25 UTC


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