이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. Executing remediation playbooks
After you create a remediation playbook, you can download and run the playbook using your organization’s Ansible workflow, or execute the playbook on remote systems from the Insights for Red Hat Enterprise Linux application.
4.1. Executing remediation playbooks from the Insights User Interface
After installing the rhc client on systems in your infrastructure, you can execute remediation playbooks on remote RHEL systems, directly from the Insights for Red Hat Enterprise Linux application.
Prerequisites
- You must be logged in to the Red Hat Hybrid Cloud Console.
- You must be a member of a User Access group with the Remediations administrator role.
Procedure
- Navigate to Automation Toolkit > Remediations.
- Select a remediation playbook to run and click on the playbook name.
- Click the Execute playbook button.
- On the popup, click on the Execute playbook on systems button. The playbook runs on those systems.
4.2. Executing remediations from the Satellite User Interface
You can also remediate using the Satellite User Interface.
Prerequisites
- You are a Cloud Administrator.
- You are a Remediations Administrator.
- You have completed Host registration using the Insights client.
For specific instructions, see Creating an Insights Remediation Plan for Hosts in the Satellite Managing Hosts documentation.
When you introduce a new host into your Satellite inventory, by means of provisioning or registration, two automatic background tasks will initiate. It will take 24 hours for these tasks to complete. This is a typical time frame for the automatic synchronization.
If you identify security issues or another scenario that warrants not waiting 24 hours for the automatic sync, you can manually synchronize by clicking the sync button in the UI. This manual sync will complete in a few minutes.
To see the procedures for enabling automatic and manual synchronization, see the Configuring Synchronization of Insights Recommendations for Hosts in the Satellite documentation.
