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:
The Traces feature seems to have made its way into 6.3 without much formal review.
Currently, one of the primary issues I see is that it is reporting items that affect host status, that the user might or might not care about. There does not seem to be any way to disable the feature and still use katello-agent for errata reporting.
In my opinion we should maybe consider removing the feature, or maybe find some way for the user to optionally enable its reporting.
(In reply to Perry Gagne from comment #0)
> Description of problem:
>
> The Traces feature seems to have made its way into 6.3 without much formal
> review.
>
> Currently, one of the primary issues I see is that it is reporting items
> that affect host status, that the user might or might not care about.
Please file a BZ for that.
> There
> does not seem to be any way to disable the feature and still use
> katello-agent for errata reporting.
>
> In my opinion we should maybe consider removing the feature, or maybe find
> some way for the user to optionally enable its reporting.
Its a yum plugin and can be disabled editing /etc/yum/pluginconf.d/tracer_upload.conf
Is it just a case of properly documenting this?
Based on discussion with Justin, the plan was to split tracer out in the RPM so that it is not installed by default. This would make it optional on the client. The code would remain enabled on the satellite server; however, there would be no effect, since the client is not using it.
There is another bug that was created to request the rpm change; therefore, I am going to close this one as a duplicate of it, since it is aligned with the plan.
*** This bug has been marked as a duplicate of bug 1510141 ***