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.

Description of problem:

sosreport --all-logs 
throws the error - 
 Setting up plugins ... 
caught exception in plugin method "container_log.setup()"
caught exception in plugin method "container_log.setup()"


Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/sos/sosreport.py", line 964, in setup
    plug.setup()
  File "/usr/lib/python3.6/site-packages/sos/plugins/container_log.py", line 24, in setup
    self.add_copy_spec(logdir)
NameError: name 'logdir' is not defined


Version-Release number of selected component (if applicable):
sos version is 3.8
RHEL release is 8.2


How reproducible:
Always


Steps to Reproduce:
1. log into any openstack
2. run sosreport --all-logs
3.

Actual results:


Expected results:


Additional info:

This was fixed via https://github.com/sosreport/sos/commit/e4ece6569221f1833d3fb621c26f19c23662b329, looks like the patch didn't get pulled into the build for sos-3.8-2.el8.noarch

Indeed, like Jake wrote.

This will be fixed in RHEL 8.3 by default, as we rebase sos to 3.9 there that includes the fix.

Approving from CEE side to fix it via z-stream in 8.2.0.z .

Pushed to dist-git of 8.3 (where it will be over-written by rebasing to sos-3.9 that contains the fix, either way).

*** Bug 1840266 has been marked as a duplicate of this bug. ***

Olaf,
could you please verify this bug (not the already verified z-stream clone I asked for by a mistake) against below package? Thanks a lot in advance.



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

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.9.1/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.9.1/2.el8/sos-3.9.1-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.9.1/2.el8/noarch/

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

The repository will be available for the next 55 days. Scratch build output will be deleted
earlier, based on the Brew scratch build retention policy.