Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2124637

Summary: [Pulp 3] The `pulpcore-manager analyze-publication` shows a WARNING in Satellite 6.12
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.12.0CC: dalley, dkliban, ggainey, rchan
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:30:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2022-09-06 16:45:27 UTC
Description of problem:

A long-awaited feature has landed in the pulp of satellite 6.12 i.e. https://github.com/pulp/pulpcore/pull/2149.

Using "pulpcore-manager analyze-publication" we are now able to see filename, artifact location and pulp href of the artifact for any given publication id or distribution path. 

But EVEn if it works, it displays a WARNING and it's not possible to use "--tabular" option as well.


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

Satellite 6.12
python39-pulpcore-3.18.6-2.el8pc.noarch


How reproducible:

Always


Steps to Reproduce:
1. Install a Satellite 6.12 with Organization name RedHat

2. Enable RHEL 7.9 Kickstart repo and sync it with immediate download policy.

3. Find out it's distribution_path:

# echo "select relative_path from katello_repositories where relative_path like '%7.9/x86_64/kickstart%' ;" | su - postgres -c "psql foreman"

4. Run "pulpcore-manager analyze-publication" against the same with and without --tabular option.



Actual results:

# echo "select relative_path from katello_repositories where relative_path like '%7.9/x86_64/kickstart%' ;" | su - postgres -c "psql foreman"
                                        relative_path                                        
---------------------------------------------------------------------------------------------
 RedHat/Library/content/dist/rhel/server/7/7.9/x86_64/kickstart


# PULP_SETTINGS=/etc/pulp/settings.py pulpcore-manager analyze-publication --distribution-base-path 'RedHat/Library/content/dist/rhel/server/7/7.9/x86_64/kickstart' | grep vmlinuz -A2
System check identified some issues:

WARNINGS:
?: (guardian.W001) Guardian authentication backend is not hooked. You can add this in settings as eg: `AUTHENTICATION_BACKENDS = ('django.contrib.auth.backends.ModelBackend', 'guardian.backends.ObjectPermissionBackend')`.
images/pxeboot/vmlinuz
└─ Storage path: /var/lib/pulp/media/artifact/9f/67343147f945a5e75f14e9012315d8300d78fb67b1a35db1e561b0b261c06c
└─ Artifact href: /pulp/api/v3/artifacts/6a5c1151-ebd2-485e-a718-66c119f17a10


# PULP_SETTINGS=/etc/pulp/settings.py pulpcore-manager analyze-publication --distribution-base-path 'RedHat/Library/content/dist/rhel/server/7/7.9/x86_64/kickstart' --tabular
System check identified some issues:

WARNINGS:
?: (guardian.W001) Guardian authentication backend is not hooked. You can add this in settings as eg: `AUTHENTICATION_BACKENDS = ('django.contrib.auth.backends.ModelBackend', 'guardian.backends.ObjectPermissionBackend')`.
CommandError: 'prettytable' package must be installed.



Expected results:


* No such WARNINGS about AUTHENTICATION_BACKENDS

* --tabular should work on RHEL 8.6 as well ( as it's the latest baseos of satellite 6.12 )


Additional info:


* This is the default config that comes with Sat 6.12 and it indeed does not have those AUTHENTICATION_BACKENDS that pulp is asking:

# grep AUTHENTICATION_BACKENDS /etc/pulp/settings.py 
AUTHENTICATION_BACKENDS = ['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend']



* RHEL 8 ships python3-prettytable-0.7.2-14.el8.noarch but the prettytable module that comes along with it is for python 3.6 and pulp uses python 3.9. That's why the error.

Comment 1 Sayan Das 2022-09-06 16:49:11 UTC
CC dalley 

If needed I can open a new BZ for the prettytable concern. ( i noticed we ship python3-prettytable-0.7.2-27.el9.noarch.rpm with RHEL 9 and that has the Python 3.9 based prettytable module ).

Comment 2 Dennis Kliban 2022-09-13 15:47:59 UTC
@saydas Let's keep this BZ about the WARNING only. Please open a separate issue for --tabular issue.

Comment 3 Sayan Das 2022-09-13 15:57:55 UTC
Sure, Dennis. No problem.. 

I was also thinking the same and have opened https://bugzilla.redhat.com/show_bug.cgi?id=2126502

Comment 5 Brad Buckingham 2023-10-04 21:43:14 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Brad Buckingham 2023-11-02 17:22:44 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 7 Daniel Alley 2023-11-03 01:31:33 UTC
Missed this one, reopening.

Comment 8 Brad Buckingham 2023-12-01 18:41:30 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 9 Brad Buckingham 2024-01-09 19:52:34 UTC
Based upon comment 7, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Comment 10 Eric Helms 2024-06-06 12:30:45 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.