Description of problem: When working with Tracer, it has to be on an individual host basis. For large environments, this is not efficient. Version-Release number of selected component (if applicable): Satellite 6.6 How reproducible: Every time. Steps to Reproduce: 1. Patch large number of servers 2. Use tracer to restart applications as needed Actual results: Have to manage this individually on each host Expected results: Some method to do bulk tracer remediation.
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29516 has been resolved.
Verified. All traces that were selected in the "Content Host Traces Management" modal window got resolved correctly. BZs BZ1867193, BZ1867159, BZ1867176 are a side outcome of this verification.
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.8 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-2020:4366