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:
puppet4 has config files under /etc/puppetlabs that downstream sosreport does not collect (yet). This makes issues to diagnose issues especially but not only in Satellite and its managed systems where Satellite6.4 newly forces to use puppet4.

This is a backport request of sos upstream commit

https://github.com/sosreport/sos/commit/2535fd316558ecd79bc391bc5bd9212c7e9cd53a

to RHEL7.6. Other RHEL releases (RHEL6 or RHEL7.(<6)) are not required as the business justification does not meet EUS criteria for those releases.

The fix will appear in RHEL7.7 automatically (fix already present in sos-3.7-1 which is current release candidate, atm).


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


How reproducible:
100%


Steps to Reproduce:
1. Call sosreport on a system with puppet4 installed
2. Check if it collects /etc/puppetlabs/puppet/*conf files.


Actual results:
2. No such file collected.


Expected results:
2. All the files collected.


Additional info:

After evaluating pending requests to 7.6.z stream for sosreport, their business justifications, requested changes and amount of affected customers/systems, I decided to release a hotfix for bz1702802 and bz1703330. My plan is to:

- deliver the HF in a week manner (no strict commitment, though)
- do not create extra 7.6.z errata for these two BZs
- include the changes in 7.7 and 8.1 (this is an obvious requirement from the nature of any HF)
  - in case 7.6.z errata would be needed, include the BZs there as well

Please raise your concerns against this plan until Wed 1st May EOB.

HF for RHEL7.6 is available at http://people.redhat.com/pmoravec/sos-3.6-17.el7_6.bz1702802_bz1703330/  (noarch rpm is sufficient, src rpm for FOSS reasons). Worth sharing to customers.

re rhel7.7.0? denied: technically the fix will be delivered in 7.7 due to rebase of sos to 3.7 there, where sos-3.7 contains the fix

This is supposed to be fixed in RHEL7.7 via errata:

https://access.redhat.com/errata/RHEA-2019:2295