Bug 1524481 – remove dependency of redhat-access-insights

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1524481 - remove dependency of redhat-access-insights

Summary:	remove dependency of redhat-access-insights

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libreport (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Martin Kutlak
QA Contact:	Martin Kyral
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1538136
	Show dependency tree / graph

Reported:	2017-12-11 10:28 EST by jjaggars
Modified:	2018-04-10 13:44 EDT (History)
CC List:	14 users (show)

See Also:
Fixed In Version:	libreport-2.1.11-40.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1538136 (view as bug list)
Environment:
Last Closed:	2018-04-10 13:43:42 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0949	None	None	None	2018-04-10 13:44 EDT

Groups: None (edit)

Description jjaggars 2017-12-11 10:28:09 EST

Description of problem:

libreport depends on redhat-access-insights (a client application) for a certificate file that it installs.  The package is going away/will no longer include the certificate and will break libreport. 

libreport should package the cert-api .pem file directly.

Comment 4 Miroslav Suchý 2017-12-21 08:05:49 EST

We do not depend on redhat-access-insights in RHEL6. So this can be done only in RHEL 7.6.

Comment 16 errata-xmlrpc 2018-04-10 13:43:42 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0949

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