Why Did a Task Fail to Execute?
Symptom
When a resource is selected from CMDB to execute a task, message "Access denied, The {ECS Instance/RDS Instance/Workload} does not belong to the current project, {ECS Instance/RDS Instance/Workload} ID is {Instance ID}" is displayed.
Possible Causes
The system will check whether the resource to be operated is under the selected sub-project. If it is not under the sub-project, operations will not be performed on it.
Solution
Ensure that the resource to be operated is under the selected sub-project. If it is not under the sub-project, add it to the current sub-project or select another sub-project. For details about how to view resource information, see Resource Management.
O&M Management (Retiring) FAQs
- How Can I Obtain the OBS Permission for Installing Packages?
- Why Can't Scheduled Tasks Be Triggered?
- Can I Specify Script Parameters and Hosts During Job Execution?
- Why Is a Parameter Error Displayed When I Create a Scheduled Task Using a Cron Expression?
- How Can I Set a Review for an Execution Plan?
- Why Is "delete success:{}" Displayed (Files Cannot Be Deleted) During Disk Clearance?
- What Can I Do If the Execution Plan Is Not Updated After I Modify the Job?
- What Can I Do If "agent not found" Is Displayed?
- Why Are the Hosts Listed in Execution Logs Inconsistent with Those I Configured for a Task?
- Why Did a Task Fail to Execute?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
