Troubleshooting Fleet Application Management

Use troubleshooting information to identify and address common issues that can occur while working with Fleet Application Management.

Applying Patches to Resources Fail or Skip

Troubleshoot Fleet Application Management that's failing to apply patches to resources that are modified.

Information about modified Fleet resources isn't available with the lifecycle operations schedules.

Cause: Modifications by Fleet Application Management aren't available in the schedule

When a fleet's topology changes, for example, an update in resource targets or the addition or deletion of resources after you create a schedule, these modifications might not be available in the schedule.

Remedy: Update existing fleets

Ensure your fleet is in an active state by confirming targets or setting autoconfirm as Enabled so that resource updates propagate to the schedule.

Cause: Correct patches aren't available

The Oracle WebLogic Server and JDK patches aren't uploaded to an Object Storage bucket, or the platform configuration under metadata management that stores the Object Storage bucket isn't updated with relevant details.

Remedy: Update the patch information

Upload Oracle WebLogic Server and JDK patches. See Working with Oracle Patches. Use the correct bucket name for the platform configuration property, Patch Bucket Name (Platform Config).

Stopped or Terminated OCI Compute and Oracle Database Resources Remain Part of the Lifecycle Operation Schedule

Troubleshoot Fleet Application Management where stopped or terminated OCI Compute and Oracle Database resources still appear in the lifecycle operation schedule.

Although the status of OCI Compute and Oracle Database resources are in a canceled state, they're part of the lifecycle operation schedule.

Cause: Stopped or terminated OCI Compute and Oracle Database resources remain part of the lifecycle operation schedule

When the state of resources changes to stop or terminate, these modifications might not appear in the schedule.

Remedy: Delete stopped or terminated resources and confirm targets

Restart the stopped resources and get them to a running state where applicable, or remove terminated resources from the fleet and confirm targets.

Lifecycle Operation Job Fails

Troubleshoot Fleet Application Management where a lifecycle operation job didn't run at the stipulated time.

Sometimes, Fleet Application Management can be delayed by a few minutes (about 15 minutes) to decide the lifecycle operation job.

Cause: Heavy load conditions

Fleet Application Management can be delayed by a few minutes (about 15 minutes) to decide the job because of heavy load.

Remedy: Contact support

If the job isn't run after the 15-minute threshold, contact support. See Getting Help and Contacting Support.

API Request Fails

Troubleshoot Fleet Application Management when an API request fails with a "Not Allowed Exception."

The API request fails with a "Not Allowed Exception."

Cause: Resources are tenancy-specific

The API request fails because the Fleet Application Management resources are tenancy-specific.

Remedy: Use tenancy root compartment ID

When making API requests, use tenancy root compartment ID for compartment ID value in the request payload query parameter.

Identifying Oracle WebLogic Server targets fail

Troubleshoot Fleet Application Management where it can't identify the Oracle WebLogic Server targets.

Although a fleet is active, Fleet Application Management can't identify the Oracle WebLogic Server targets.

Cause: The Oracle WebLogic Server version isn't supported by Fleet Application Management

Fleet Application Management can identify targets only if the required version of the Oracle WebLogic Server is supported.

Remedy: Use the supported version of Oracle WebLogic Server

Ensure you use only the supported versions of Oracle WebLogic Server. For supported versions, see Supported Products.

Oracle Cloud Infrastructure Documentation