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 2043126 - Non-enabled repository types make it into the apipie help-text
Summary: Non-enabled repository types make it into the apipie help-text
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: Ian Ballou
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 16:49 UTC by Ian Ballou
Modified: 2022-11-16 13:33 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-katello-4.5.0.12-1
Doc Type: Known Issue
Doc Text:
*Non-enabled repository types might appear in `apipie help-text`* Because the apipie cache is generated statically rather than with a running Satellite, non-enabled repository types such as `deb` and `python` might appear in the apipie help-text. This will be patched in a future release.
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35459 0 Normal New Non-enabled repository types make it into the apipie help-text 2022-08-30 18:43:21 UTC
Red Hat Issue Tracker SAT-11629 0 None None None 2022-08-30 18:48:26 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:44 UTC

Description Ian Ballou 2022-01-20 16:49:20 UTC 
Description of problem:
Non-enabled repository types make it into the apipie help-text, such as "deb" or "python".

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

How reproducible:
Always.


Steps to Reproduce:
1.  hammer repository create --help

Actual results:
 --content-type ENUM                            Type of repo
                                                Possible value(s): 'ansible_collection', 'deb', 'docker', 'file', 'ostree',
                                                'python', 'yum'

Expected results:
Don't include types not supported by the smart proxy.


Additional info:
For Satellite 7.0, this will likely need to be fixed temporarily with a patch to the rubygem-katello.spec file to `rm` the non-Satellite repository type files.

The issue is due to how the apipie cache is generated statically.  Since it's not generated with a running Satellite, we cannot use the enabled repository types.

For a medium-term fix, we could remove the repo types completely from the apipie definition and add in an endpoint to check the enabled content types.

For a longer-term fix, we could switch to having the apipie cache generating dynamically in Foreman.  That will require more consideration.
Comment 6 sabuchan 2022-06-14 16:37:35 UTC 
RN draft:

Because the apipie cache is generated statically rather than with a running Satellite, non-enabled repository types such as `deb` and `python` can appear in the apipie help-text. This will be patched in a future release.

Doc: https://docs.google.com/document/d/1xMkjPbkwF9ZJ95tEcWYmRRqVdusIZENHZsL3-B3YvJw/edit

Tagged @iballou in the doc for review.
Comment 7 Ian Ballou 2022-06-14 19:18:16 UTC 
The doc text looks good to me!
Comment 8 sabuchan 2022-06-15 20:41:22 UTC 
Final RN:

*Non-enabled repository types might appear in `apipie help-text`*

Because the apipie cache is generated statically rather than with a running Satellite, non-enabled repository types such as `deb` and `python` might appear in the apipie help-text. 
This will be patched in a future release.
Comment 10 Ian Ballou 2022-08-30 18:43:21 UTC 
Created redmine issue https://projects.theforeman.org/issues/35459 from this bug
Comment 12 Bryan Kearney 2022-09-07 16:03:50 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35459 has been resolved.
Comment 14 Partha Aji 2022-09-29 17:26:33 UTC 
Verified

#  hammer repository create --help |grep content-type
 --content-type VALUE                           Type of repository to create. View available types with "hammer repository types"


#  hammer repository list --help |grep content-type
 --content-type VALUE                           Limit the repository type to return. View available types with "hammer repository types"


#  hammer repository upload-content --help |grep content-type
--content-type VALUE                           The type of content unit to upload (srpm, file, etc.). View uploadable types
                                                with "hammer repository types"
# hammer repository remove-content --help |grep content-type
 --content-type VALUE             The type of content unit to remove (srpm, docker_manifest, etc.). View removable
                                  types with "hammer repository types"
Comment 18 errata-xmlrpc 2022-11-16 13:33:25 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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506
Note You need to log in before you can comment on or make changes to this bug.