Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug was initially created as a copy of Bug #2018228
I am copying this bug because:
Description of problem:
When executing the sosreport command on a RHEL 8 (and RHEL 7) machine, it does not capture the /etc/unbound hierarchy, which contains unbound.conf and a conf.d which could affect its operation. This makes troubleshooting unbound problems more difficult in support cases.
# tar -tJf /var/tmp/sosreport-rhel83-001-9999-2021-10-28-lghfima.tar.xz | grep -i unbound
sosreport-rhel83-001-9999-2021-10-28-lghfima/sos_commands/insights/insights-client-dump/data/usr/lib/tmpfiles.d/unbound.conf
sosreport-rhel83-001-9999-2021-10-28-lghfima/etc/sysconfig/unbound
sosreport-rhel83-001-9999-2021-10-28-lghfima/etc/systemd/system/timers.target.wants/unbound-anchor.timer
sosreport-rhel83-001-9999-2021-10-28-lghfima/usr/lib/systemd/system/unbound-anchor.timer
sosreport-rhel83-001-9999-2021-10-28-lghfima/usr/lib/systemd/system/unbound.service
sosreport-rhel83-001-9999-2021-10-28-lghfima/usr/lib/systemd/system/unbound-anchor.service
sosreport-rhel83-001-9999-2021-10-28-lghfima/usr/lib/systemd/system/unbound-keygen.service
Version-Release number of selected component (if applicable):
sos-4.0-12.el8_4.noarch (sos-3.9-5.el7_9.7.noarch in RHEL 7)
Additional info:
I'm listing RHEL 7 info here just to make people aware of that version being affected. Due to where RHEL 7 currently is in its life cycle, I don't see the point in making a Bugzilla ticket for it since it would most assuredly be closed as WONT_FIX. Still, if others think differently, I can create such a Bugzilla ticket.
Hello,
(same applies here on cloned 9.1 bug)
as our QE might not have available systems for testing the fix, would you be able to verify the fix once available (as a candidate package for 9.1)?
(In reply to Pavel Moravec from comment #1)
===
> (same applies here on cloned 9.1 bug)
===
Yes, I'd be happy to test RHEL 9.1's package when it is available.
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 (sos bug fix and enhancement update), 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-2022:8275