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.
Bug 1414879 - rebase sos to 3.4 in RHEL7.4
Summary: rebase sos to 3.4 in RHEL7.4
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.4
Hardware: noarch
OS: Linux
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
Lenka Špačková
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-19 16:23 UTC by Pavel Moravec
Modified: 2017-08-14 19:12 UTC (History)
8 users (show)

Fixed In Version: sos-3.4-1.el7
Doc Type: Release Note
Doc Text:
_sos_ rebased to version 3.4 The _sos_ package has been updated to upstream version 3.4, which provides a number of enhancements, new features, and bug fixes, including: * New plug-ins have been added for *ceph_ansible*, *collectd*, *crypto*, *dracut*, *gnocchi*, *jars*, *nfsganesha*, *nodejs*, *npm*, *openstack_ansible*, *openstack_instack*, *openstack_manila*, *salt*, *saltmaster*, and *storageconsole* * API plug-in enhancements * Internationalisation updates * The networking plug-in no longer crashes when a network name contains the single quote character `'` * The *foreman-debug* plug-in is now run with a longer timeout to prevent incomplete *foreman-debug* information collected * Certain private SSL certificate files are no longer collected
Clone Of:
Last Closed: 2017-08-01 23:08:12 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2203 0 normal SHIPPED_LIVE sos bug fix and enhancement update 2017-08-01 19:41:56 UTC

Description Pavel Moravec 2017-01-19 16:23:15 UTC
Description of problem:
I would like to rebase sos package in RHEL7.4 to upstream 3.4 version planned to be released in March this year. Reasons:

- Since sos 3.3 GA, there have been numerous minor updates in upstream sos / sosreport that would be beneficial for CEE to get in RHEL7.4.

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

- Rebasing will simplify downstream work, esp. later on when working on z-stream patches (some 7.2.z patches were needed to be manually rewritten due to the diff between upstream and downstream)

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

How reproducible:

Steps to Reproduce:
1. rpm -q sos

Actual results:

Expected results:

Additional info:

Comment 12 errata-xmlrpc 2017-08-01 23:08:12 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.


Note You need to log in before you can comment on or make changes to this bug.