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 1956672 - Add pulpcore plugin to RHEL7.9.z
Summary: Add pulpcore plugin to RHEL7.9.z
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.9
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jan Jansky
QA Contact: Maros Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 08:15 UTC by Pavel Moravec
Modified: 2021-07-21 01:06 UTC (History)
10 users (show)

Fixed In Version: sos-3.9-5.el7_9.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-21 01:06:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 2520 0 None open [pulpcore] add plugin for pulp-3 2021-05-04 08:46:13 UTC

Description Pavel Moravec 2021-05-04 08:15:17 UTC 
Description of problem:
Backport https://github.com/sosreport/sos/pull/2512 (pulpcore plugin for pulp-3) to RHEL7.9.z, ideally before Sat6.10 GA.

Once Satellite6.10 with pulp-3 will be available, sos report should collect pulpcore/pulp-3 debugging info for it.


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


How reproducible:
100%


Steps to Reproduce:
1. Install Sat6.10 or Sat7 (once available) on RHEL7 (once available/possible)
2. Run sosreport
3. Check if it contains pulpcore/pulp-3 specific data per sos upstream #2512


Actual results:
3. nothing collected / no pulpcore plugin


Expected results:
3. functionality from #2512 present


Additional info:
We can ensure OtherQE
Comment 5 Pavel Moravec 2021-06-15 10:44:54 UTC 
Testing the plugin on Sat6.9 with pulp-3 enabled and also on some pre-pre-release of 6.10 (with pulp-3 as the default):

- it is enabled by default when pulp-3 is present
- plugin collects all required data properly
- it does NOT obfuscate two passwords:

sos_commands/pulpcore/dynaconf_list :
SECRET_KEY<str> 'MWb9n5emP8BdgM9ugqMwAysWMf35FYq9YoD34a8ZPtBQJPsJHA'
..
DATABASES<dict> {'default': {'ENGINE': 'django.db.backends.postgresql',
             'HOST': 'localhost',
             'NAME': 'pulpcore',
             'PASSWORD': 'PyDJ9y4XP9nKsBmeuwy7uJouXBHvH4aT',

that comes from /etc/pulp/settings.py where we do obfuscate both properly:

SECRET_KEY = ********
        'PASSWORD': ********


SECRET_KEY is from Django: https://docs.djangoproject.com/en/2.2/ref/settings/#secret-key
PASSWORD is the postgres DB password

Without an access to the Satellite system, leaking the passwords isnt a crucial problem. But I would recommend to fix this (ideally now or in the next z-stream (but when it will happen?)
Comment 6 Pavel Moravec 2021-06-15 11:37:16 UTC 
https://github.com/sosreport/sos/pull/2583 raised for the dynaconf_list
Comment 11 errata-xmlrpc 2021-07-21 01:06:48 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 (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/RHBA-2021:2804
Note You need to log in before you can comment on or make changes to this bug.