Diagnose a failed request
Resource Orchestration Service (ROS) provides quick diagnostics to help you identify the causes of failed API calls and stack executions. This topic uses a failed stack group deletion as an example to show you how to diagnose a failed request.
Scenario
When an operation fails in the ROS console, you can click Diagnose to identify the failure cause and obtain remediation suggestions. You can then follow the suggestions to resolve the issue and retry the operation.
Procedure
-
Log on to the ROS console.
-
In the left-side navigation pane, click Stack Groups.
-
On the Stack Groups page, find the stack group that you want to delete and click Remove.
-
Click OK.
-
An error message appears.
The error message is
The StackGroup (testes1) is not empty., and the error code isStackGroupNotEmpty. The stack group cannot be deleted because it contains stack instances. Click Close to dismiss the dialog box, or click Submit Diagnostics to troubleshoot the issue. -
Click Submit Diagnosis.
-
After you submit the request, the Diagnostics page appears.
NoteThe diagnostic process may take some time. Wait until it is complete.
-
View the Diagnostics Results and Suggestions. Follow the suggested solution to delete the stack group.
The diagnostics results show a ROS API error. The error keyword is
StackGroupNotEmpty, and the message isThe StackGroup (testes1) is not empty.. The suggestions section explains that the stack group (testes1) cannot be deleted because it still contains stack instances. The recommended solution is to query the stack group details, delete all stack instances, confirm deletion, and then delete the stack group.