Bug 1698945

Summary:	[6.5.1 REQUIRED] Update libsolv to >= 0.6.35
Product:	Red Hat Satellite	Reporter:	Patrick Creech <pcreech>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Brian Herring <bherring>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	bherring, bkearney, dvoss, egolov, mmccune, pondrejk, sghai, zhunting
Target Milestone:	6.5.2	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libsolv-0.6.35-1.el7sat	Doc Type:	Known Issue
Doc Text:	This has been fixed upstream, and will be delivered in a future release.	Story Points:	---
Clone Of:
Clones:	1726812 (view as bug list)		Environment:
Last Closed:	2019-08-06 14:37:33 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:	1702415

Description Patrick Creech 2019-04-11 13:19:17 UTC

Pulp upstream used a patched libsolv 0.6.34 from fedora that backported a critical code flow for pulp from 0.6.35.

Confidence is low that el7 distributions will backport this patch when releasing superseding 0.6.34 updates that will override the current one used in satellite's pulp, therefore breaking pulp's modular workflow.

To avoid this, we need to update our libsolv to 0.6.35.

Comment 5 Evgeni Golov 2019-05-21 12:07:50 UTC

*** Bug 1712360 has been marked as a duplicate of this bug. ***

Comment 7 Brian Herring 2019-07-16 12:38:15 UTC

Verified Version of RPM on the 6.5.2 Snap 1 contains the correct version of libsolv:

[root@kvm-01-guest18 ~]# rpm -qa | grep -i satellite-6.5.2
satellite-6.5.2-1.el7sat.noarch
[root@kvm-01-guest18 ~]# rpm -qa | grep -i libsolv
libsolv-0.6.35-1.el7sat.x86_64
[root@kvm-01-guest18 ~]# 


Limited scope of change. No other verification specified no carried out relative to this specific BZ.

Comment 9 errata-xmlrpc 2019-08-06 14:37:33 UTC

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-2019:2363