Bug 1745017

Summary: [sos] openvswitch plugin does not catch openvswitch2.* package
Product: Red Hat Enterprise Linux 8 Reporter: David Marchand <dmarchan>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: qding
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0CC: agk, amuller, atragler, blc, bmr, ctrautma, fbaudin, fhallal, gavin, mhradile, plambri, pmoravec, sbradley
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sos-3.7-4.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:32:48 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 David Marchand 2019-08-23 13:32:35 UTC 
Starting with the release of openvswitch 2.10, the FDP channel maintains multiple packages for openvswitch.

FDP channel provides openvswitch 2.11 for RHEL 8 but the openvswitch plugin in sos only catches "openvswitch" and "openvswitch-dpdk" package names.
Comment 1 David Marchand 2019-08-23 13:36:54 UTC 
Sent a pull request upstream:
https://github.com/sosreport/sos/pull/1768
Comment 3 Pavel Moravec 2019-09-06 13:41:43 UTC 
(In reply to Franck Baudin from comment #2)
> This is mandatory for the cloud BU products (RHOSP is the first in line) to
> get SOS report to ship OVS 2.11: when can we get tis fixed? Thanks!

By default, it will occur in RHEL8.2.

8.1 is too late, 8.1.z is possible - esp. if you can do OtherQE. Let me know if you request the 8.1.z.
Comment 19 errata-xmlrpc 2019-11-05 22:32:48 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:3640