Fixing a Fleet to Be Compliant

Configure runbook tasks and parameters for noncompliant fleets in Fleet Application Management.

• Console
• CLI
• API

• On the Fleets list page, select the fleet that you want to work with. If you need help finding the list page or the fleet, see Listing Fleets.

  On the details page for the fleet, select Fix now under the Compliance status section of the General information tab.

  Fixing a fleet to be compliant consists of the following pages:

  • 1. Select runbooks

  • 2. Runbook parameters

  • 3. Review

  Run each of the following workflows in order. You can return to a previous page by selecting Previous.

  1. Select runbooks

  The Select runbooks page is where you add the required runbooks for the noncomplaint fleet.

  1. For the Name, enter a name for the compliance fix. By default, a hyphenated alphanumeric information comprising lifecycle operation with date and time of execution is set.
  2. Select Add runbook.
  3. In the Add runbook panel, select the runbooks that you want to include in the fleet.
     Note
     
     Only active runbooks are displayed for selection.
  4. Select a runbook version.
     All runbooks specific to patching, discovery, and custom lifecycle operations are available.
  5. Select Add.
  6. To add runbooks from another compartment, select that compartment and repeat the preceding steps.

  After you add runbooks to the fleet, they appear in the Add runbook table. The runbooks are executed based on the execution order displayed on the table. You can perform the following actions:

  • Select the runbook name to get more details.
  • From the Actions menu () in the row for that runbook, select an appropriate order to alter the execution order.

  Select Next to proceed to the next step.

  2. Runbook parameters

  The Runbook parameters page is where you enter one or more arguments for the runbook task if arguments were defined.

  • Argument name: Select the argument name associated with the runbook task if there were parameters associated with the runbook.
  • Argument value: To change the default argument value, enter an argument value.
  • Apply same value wherever applicable in a runbook: To apply the same argument value across runbook tasks, turn on this toggle. If you don't turn on the toggle, enter an argument name and value under Patch OS.

  Select Next to proceed to the next step.

  3. Review

  Review the contents of the Review page. Select Edit basic information to change settings.

  Select Edit runbooks to modify the runbook settings. For field descriptions, see Creating a Runbook.

  Select Edit parameters to modify the input and output variables of a task. For field descriptions, see Creating a Task.

  When the settings are fully verified, select Create.

  A compliance fix job is created and you can find its progress from the Executions tab. See Listing Executions. You can also find the compliance fix job by selecting the Jobs tab under Schedules.

• Use the oci fleet-apps-management fleet-apps-management-operations scheduler-definition create command and required parameters to fix a noncompliant fleet:

  oci fleet-apps-management fleet-apps-management-operations scheduler-definition create --action-groups <json_file_or_string> --compartment-id <compartment_OCID> --schedule <json_file_or_string> [OPTIONS]

  For a complete list of flags and variable options for Fleet Application Management CLI commands, see the CLI for Fleet Application Management.

• Run the CreateSchedulerDefinition operation to fix a noncompliant fleet.