Known Issues for Fleet Application Management
Known issues have been identified in Fleet Application Management.
Context-Sensitive Help isn't Available
Context-sensitive help isn't available in this release of Fleet Application Management.
- Details
- When navigating through the Fleet Application Management screens, some help links might not work when you select them.
- Workaround
- Navigate to the OCI documentation for Fleet Application Management to get information about the service.
Verifying Fleet Schedule Conflicts isn't Available
The option to verify conflicts between fleets added to the schedule in Fleet Application Management isn't functioning as intended.
- Details
- When you navigate to the Schedules list page in Fleet Application Management and select a schedule, the Check Fleet Schedule Conflicts option is no longer available.
- Workaround
- To find information about the conflicts related to any fleet, go to the Executions screen in Fleet Application Management. This screen details the list of executions, their schedules, and the associated fleets.
Unsupported APIs
The following APIs aren't supported in Fleet Application Management.
- Details
-
- ScriptBasedExecutionDetails Reference
When creating a task, the automatic execution of a script file by the
isExecutableContentattribute isn't supported.As a workaround, use the
commandattribute to execute the script file. - ScriptBasedExecutionDetails Reference
When creating a task, the provision to lock the script to stop its changes in Object Storage by the
isLockedattribute isn't supported. - SelfHostedInstanceRunOnDetails Reference
When creating a task from a runbook, you can't use this API for a discovery runbook.
- RunOnDetails Reference
When creating a task from a runbook, the run on enum value (
SCHEDULED_INSTANCES) isn't supported.As a workaround, use the enum value:
SCHEDULE_INSTANCES. See ScheduleInstanceRunOnDetails Reference .
- ScriptBasedExecutionDetails Reference