Bug 1711305

Summary:	certificate for qpid-stat in katello plugin depends on Satellite/katello version
Product:	Red Hat Enterprise Linux 7	Reporter:	Pavel Moravec <pmoravec>
Component:	sos	Assignee:	Pavel Moravec <pmoravec>
Status:	CLOSED ERRATA	QA Contact:	Jan Hutař <jhutar>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.7	CC:	agk, bmr, gavin, jhutar, mhradile, plambri, sbradley
Target Milestone:	rc	Keywords:	OtherQA, Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sos-3.7-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1719887 (view as bug list)		Environment:
Last Closed:	2019-08-06 13:15: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:	1719887

Description Pavel Moravec 2019-05-17 13:30:13 UTC

Description of problem:
basically cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1710625 :

Since Sat6.6., fresh installations moved cert

/etc/pki/katello/qpid_client_striped.crt 

to

/etc/pki/pulp/qpid/client.crt

such that qpid-stat calls in katello plugin would fail when using old cert.

The plugin has to stat whether file exists, and use that one.

If this wont be fixed in 7.7, there would be regression against Sat 6.6.


Version-Release number of selected component (if applicable):
sos 3.7-2

How reproducible:
100%


Steps to Reproduce:
1. Install fresh Satellite 6.6 and sos 3.7-2
2. run sosreport (optionally with options  -o katello --batch --build  )


Actual results:
qpid-stat fails like in that BZ.


Expected results:
qpid-stat succeeds


Additional info:

Comment 2 Pavel Moravec 2019-05-17 13:30:50 UTC

OtherQA will be provided by jhutar

Comment 14 errata-xmlrpc 2019-08-06 13:15:51 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/RHEA-2019:2295