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.
Description of problem:
In Satellite 6.7 a customer will get the warning message "Katello-agent is deprecated and will be removed in Katello 4.0. Consider migrating to Remote Execution.".
The messaging here might be confusing for customers using the Satellite product and not Katello.
Version-Release number of selected component (if applicable):
Satellite 6.7.0
How reproducible:
Every time
Steps to Reproduce:
1. Select a content host in Hosts=>Content Hosts
2. Then select the Errata tab for the content host
Actual results:
A message that says:
"Katello-agent is deprecated and will be removed in Katello 4.0. Consider migrating to Remote Execution."
is shown.
Expected results:
If Satellite needs to show a message at all, it should either reference a specific Satellite version or if that is not possible it should reference "a future version of Satellite".
Being non-specific here may result in more cases where customer may ask for the specific version tho.
Additional info: