How to diagnose a failed stack-Resource Orchestration Service(ROS)-阿里云帮助中心

Resource Orchestration Service (ROS) provides a one-click diagnostics feature that helps you identify the root cause of failed ROS API requests or stack operations. You can use this feature to diagnose a stack creation failure and get actionable suggestions.

Use cases

If a stack fails to create, you can use the Diagnostics feature to analyze the error, identify its root cause, and get suggestions to fix the issue and recreate the stack.

Procedure

Log on to the ROS console.
In the left-side navigation pane, click Stacks.
In the top navigation bar, select the region where the stack is located, such as China (Hangzhou).
On the Stacks page, find the failed stack and click Diagnostics in the Diagnostics column.
The Diagnostics page appears.

Note
The diagnostic process may take some time.
Review the Diagnostics Results and Suggestions, and then follow the suggestions to recreate the stack.

The diagnostics page contains three sections: Basic Information, Diagnostic Results, and Suggestions. Basic Information includes the diagnostic keywords, diagnostic time, stack name, operation type, stack status, and diagnostic status. Diagnostic Results shows Exceptions from ROS API and Exceptions from Cloud Service API Calls, including the service, stack region, exception keywords, API operation name, and exception time. The Suggestions section, generated by a large language model (LLM), provides an error trace, root cause analysis, and a remediation plan. The plan might suggest checking dependent resources, removing associations, or retrying an operation after you delete the dependencies.