The `analyze-publication` management command shows a warning
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 32/100
Research direction
Start by reproducing the warning with the pulpcore-manager analyze-publication command, both with and without --tabular, using the distribution path from the report. Trace the analyze-publication command's startup checks and tabular dependency handling; done means the command produces no unexpected warning messages and both documented modes behave as expected.
Written by the indexing model from the issue text.
Description
Version
pulpcore 3.18
Describe the bug
Warning messages are printed when using the analyze-publication management command
# 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.
To Reproduce
-
Install a Satellite 6.12 with Organization name RedHat
-
Enable RHEL 7.9 Kickstart repo and sync it with immediate download policy.
-
Find out it's distribution_path
-
Run "pulpcore-manager analyze-publication" against the same with and without --tabular option.
Expected behavior
No warning messages
Additional context
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulpcore
-
Issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Feature
-
upgrading to 3.117.1 fails without saying which Distribution base_paths are violating constraint OpenIssue
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Issue Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100