RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

I would like to rebase sos package in RHEL7.7 to upstream 3.7 version planned to be released in Q1 2019 / before 7.7 devel freeze. Reasons:

- several features and adjutments are planned for the release that can be nontrivial to backport one after another (while the features are worth to offer to customers and CEE). So it is much easier to pack a stable upstream version than try to apply patches to downstream.

- there will be smaller "testing distance" between upstream and RHEL

- rebasing will simplify future downstream work, esp. later on when working on z-stream patches


Version-Release number of selected component (if applicable):
sos-3.6-*


How reproducible:
100%


Steps to Reproduce:
1. rpm -q sos


Actual results:
sos-3.6-*


Expected results:
sos-3.7-*


Additional info:

technically, FailedQA since:

# rpm -q sos
sos-3.7-1.el7.noarch
# sosreport 

sosreport (version 3.6)

..


Trivial fix (just the 2nd part applies to downstream):

diff --git a/sos.spec b/sos.spec
index 95249670..68aedcfd 100644
--- a/sos.spec
+++ b/sos.spec
@@ -2,7 +2,7 @@
 
 Summary: A set of tools to gather troubleshooting information from a system
 Name: sos
-Version: 3.6
+Version: 3.7
 Release: 1%{?dist}
 Group: Applications/System
 Source0: http://people.redhat.com/breeves/sos/releases/sos-%{version}.tar.gz
diff --git a/sos/__init__.py b/sos/__init__.py
index c436bd20..dfc7ed5f 100644
--- a/sos/__init__.py
+++ b/sos/__init__.py
@@ -25,7 +25,7 @@ if six.PY3:
 else:
     from ConfigParser import ConfigParser, ParsingError, Error
 
-__version__ = "3.6"
+__version__ = "3.7"
 
 gettext_dir = "/usr/share/locale"
 gettext_app = "sos"


will fix in a day or two

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