Bug 1700780

Summary: [RFE]: Replace vdsm sos report code with sos plugin
Product: Red Hat Enterprise Linux 8 Reporter: Irit Goihman <igoihman>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Miroslav HradĂ­lek <mhradile>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: agk, bmr, bugs, gavin, isaranov, lsvaty, mgoldboi, mperina, pasik, plambri, pmatyas, pmoravec, sbonazzo, sbradley, snagar, stefw, ybronhei
Target Milestone: rcKeywords: CodeChange, FutureFeature, OtherQA
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sos-3.7-2.el8 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1494970 Environment:
Last Closed: 2019-11-05 22:32:24 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: 1494970, 1680691    
Bug Blocks: 1460625    

Description Irit Goihman 2019-04-17 11:25:10 UTC
vdsm sos plugin was added to sos report, but vdsm sos plugin rpm is still shipped as part of vdsm installation.

The plugin will be removed in vdsm-4.40

sos should mark obsolete/conflicts vdsm versions lower than 4.40.

Comment 1 Pavel Moravec 2019-04-21 06:29:00 UTC
devel_ack+ for 8.1

Comment 2 Pavel Moravec 2019-04-21 14:22:08 UTC
(In reply to Irit Goihman from comment #0)
> sos should mark obsolete/conflicts vdsm versions lower than 4.40.

Just to confirm: you need requirement in sos.spec:

Obsoletes: vdsm <= 4.40

? (it is bit strong obsolete requirement as I expect vdsm package provides much more functionality than just a sos plugin; on the other hand as the sos plugin is shipped directly in vdsm package, there is no better choice)?

Comment 3 Pavel Moravec 2019-04-21 14:26:19 UTC
(In reply to Pavel Moravec from comment #2)
> Obsoletes: vdsm <= 4.40

Correction:

Obsoletes: vdsm < 4.40

(as 4.40 will be the first version without sos plugin)

Comment 4 Irit Goihman 2019-04-24 10:25:14 UTC
Pavel, yes, I need a way to mark the conflict with vdsm < 4.40.

I didn't find other choice rather than obsoletes, if you have a different approach you are welcome to implement it.

Comment 5 Pavel Moravec 2019-04-24 11:50:07 UTC
bmr++ for yet better idea:

Conflicts: vdsm < 4.40

Comment 6 Pavel Moravec 2019-06-12 15:15:40 UTC
I expect you will do OtherQA (as the plugin has been already tested by you), am I right?

Comment 7 Pavel Moravec 2019-06-13 09:13:07 UTC
Irit,
could you pls. verify the BZ against below build (I expect no issues, plugin is present as in PR)? Thanks in advance.


A yum repository for the build of sos-3.7-1.el8 (task 22133742) is available at:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/

You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/sos-3.7-1.el8.repo

RPMs and build logs can be found in the following locations:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/noarch/

The full list of available rpms is:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/noarch/sos-3.7-1.el8.src.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/noarch/sos-audit-3.7-1.el8.noarch.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/noarch/sos-3.7-1.el8.noarch.rpm

Build output will be available for the next 21 days.

Comment 8 Irit Goihman 2019-06-13 09:15:54 UTC
Adding Martin Perina

Comment 10 Martin Perina 2019-06-13 11:55:16 UTC
(In reply to Pavel Moravec from comment #7)
> Irit,
> could you pls. verify the BZ against below build (I expect no issues, plugin
> is present as in PR)? Thanks in advance.
> 
> 
> A yum repository for the build of sos-3.7-1.el8 (task 22133742) is available
> at:
> 
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/
> 
> You can install the rpms locally by putting this .repo file in your
> /etc/yum.repos.d/ directory:
> 
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/sos-3.
> 7-1.el8.repo
> 
> RPMs and build logs can be found in the following locations:
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/
> noarch/
> 
> The full list of available rpms is:
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/
> noarch/sos-3.7-1.el8.src.rpm
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/
> noarch/sos-audit-3.7-1.el8.noarch.rpm
> http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/1.el8/
> noarch/sos-3.7-1.el8.noarch.rpm
> 
> Build output will be available for the next 21 days.

Unfortunately VDSM is not yet available on RHEL 8, we are aiming on 8.1. So the only verification which is possible at the moment is to verify is vdsm plugin exists in sos. Of course RHV team will verify the functionality later, when we will have working VDSM for RHEL 8.

Comment 18 Pavel Moravec 2019-07-09 13:28:15 UTC
Hi,
could you pls. verify the bug against below build? Current upstream plugin should be present there. Thanks in advance.


A yum repository for the build of sos-3.7-2.el8 (task 22574870) is available at:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/

You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/sos-3.7-2.el8.repo

RPMs and build logs can be found in the following locations:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/noarch/

The full list of available rpms is:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/noarch/sos-3.7-2.el8.src.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/noarch/sos-3.7-2.el8.noarch.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el8/noarch/sos-audit-3.7-2.el8.noarch.rpm

Build output will be available for the next 21 days.

Comment 24 errata-xmlrpc 2019-11-05 22:32:24 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