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.

Description of problem:
API warning messages are not being printed for API calls that should be so the user knows to use a different API call.

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

Katello 3.14
Katello 3.15
Satellite 6.6
Satellite 6.7

Additional info:

We are using the following warnings in the Katello controller code:

https://github.com/Katello/katello/blob/master/app/controllers/katello/api/v2/repositories_controller.rb#L222-L224

This commit looks like it silenced it:

https://github.com/theforeman/foreman/commit/0fd467c844fd200b5da72a0c670a5ac2bd4a61d6

This issue looks to log the warning to Rails for the API calls we care about and ignore the deprecated Rails calls we do not care about.

Verified with sat 6.7, Katello version 3.14

Production log shows the deprecation warnings. 

Verified. I ran hammer commands to create a custom repo(puppet, ostree and yum content type) and I watched the log when post request was sent from UI. 

Api deprecation message works for puppet and ostree repository types as expected. (look at code changes in Links) 


hammer command which I use for puppet:
hammer repository create --content-type puppet --name <repo_name> --product-id <product_id>  --verify-ssl-on-sync true --upstream-username <username> --upstream-password <password> --publish-via-http true

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, 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-2020:1454