Bug 1341143

Summary:	Please don't ship docker and docker advisory under different cpes
Product:	Red Hat Enterprise Linux 7	Reporter:	Lubos Kocman <lkocman>
Component:	distribution	Assignee:	Brian Gollaher <nobody+bgollahe>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	jfrancin, lsmid, sgraf, snagar, ssampat, thoger, vpavlin
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1341147 (view as bug list)		Environment:
Last Closed:	2020-12-15 07:41:51 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:
Bug Depends On:
Bug Blocks:	1341147

Description Lubos Kocman 2016-05-31 11:09:32 UTC

Description of problem:

We do ship "RHEL" content under RHEL Extras CPE tag as far as Errata notification goes.
This is wrong for following reason:

The CPE tag that we use for RHEL Extras advisories is following:

cpe:/a:redhat:rhel_extras_other:7

while it should be shipped with followint CPE.
This CPE is also present in /etc/system/release-cpe file within docker container
 
cpe:/o:redhat:enterprise_linux:7::server

I was always told that we do ship docker image in extras since we do ship docker binary "aka technology" in RHEL Extras channel.

Which is a wrong way of looking at the problem. The content of image should define CPEs that are going to be used in the advisory. Which is enterprise_linux:7 in our case.

Please ship container images in errata for product which container represents (This means RHEL-7 and not Extras for RHEL-7).

Comment 7 RHEL Program Management 2020-12-15 07:41:51 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.