View execution details of a standard operation and maintenance process

This topic describes how to view the execution details of a Standard Operation and Maintenance Process (SOP) task and perform operation and maintenance operations on an ongoing task.

Prerequisites

• The current OCP user has any of the Cluster Management, Tenant Management, or Host Management resource permissions (for operating the target resource).
• The Update permission on the cluster/tenant/host (for operations such as starting, proceeding to the next step, or retrying steps).
• SOP permissions are automatically determined by the system based on the logged-in user's identity. For details, see Overview of Standard Operation and Maintenance Processes.

View execution details

1. Log in to OCP.

2. In the left navigation bar, click O&M > Standard workflow.

3. On the Standard workflow page, locate the target task and click the task name or Execution Details to go to the execution details page.

The execution details page displays the following information:

Basic Information

Displays the basic information about the task, including the task name, task type, execution object, creation time, creator, start time, end time, and current status.

Execution Progress

Displays the overall execution progress of the task, including the number of completed steps and the total number of enabled steps (for example, 7/7), as well as the execution status of each step.

Step List

Displays detailed execution information for all steps:

Perform operation and maintenance operations

Depending on the task status, you can perform the following operations:

Start a task

For a task in the Pending state, click Start to create an execution instance and start the first step.

• When the first step is automatically executed, the return status depends on the immediate processing result.
• When the first step requires manual execution, the return status is Pending Confirmation.

Proceed to Next Step

When the task status is Pending Confirmation or Executing, and there are ready steps with autoRun=false, you can click Proceed to Next Step to advance the manual steps.

• If multiple steps can be advanced, you need to select the step number to proceed.
• Explicit confirmation is required when proceeding to the next step; advancement is not allowed without confirmation.

Retry Failed Steps

When a step fails, the following retry options are supported:

• Retry All Failed Steps: When the overall execution instance status is FAILED, you can retry all failed steps at once.

• Retry Specified Failed Step: Retry a single step that has a status of FAILED. The overall execution instance does not necessarily need to be in a FAILED state, but the specified step must be FAILED.

Update Step Configuration

You can update the configuration of a step that is in the PENDING state in a started task:

• Modify Auto Execution Switch: Only steps marked as editable (editable=true) in the template allow modification.
• Set Step Parameters: You can save step-level parameters before a step is executed. The configurable parameters vary by SOP type/step:
  • For the Add OBServer step in Data Reconstruction After OBServer Failure: You can set the replacement host ID (replacementHostId) and replacement host IP (replacementHostIp).
  • For the Create Standby Tenant step in Rebuild Standby Tenant: You can set the complete parameters (createStandbyTenantParamJson) for creating a new standby tenant, including the tenant name, compatibility mode, primary tenant ID, standby cluster ID, primary-standby synchronization method, Zone replica configuration, tenant parameters, etc.

Edit Task

For a task in the Pending state, click Edit to modify the task's name, target parameters, step configuration, and remarks. The task type cannot be modified; the server always retains the original task type.

Delete Task

• Tasks in the Pending state can be deleted directly.
• Tasks in the Ended or Failed state can be deleted.
• Tasks in the Waiting for Confirmation or In Progress state cannot be deleted.

Deleting a task will cascade clean up the execution instances, step execution records, and step-associated task records.

Step Identifier Description

The step identifiers for different SOP types are as follows. When creating or editing a task, only identifiers of the corresponding type can be used in the step array.