Cloud Operations Center
Cloud Operations Center
- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Resources
- Resource Management
-
Application Management
- Overview
- Creating an Application
- Modifying an Application
- Deleting an Application
- Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating with Resources
- Automatically Associating with Resources
- Transferring Resources
- Disassociating Resources from an Application Group
- Viewing Resource Details
- Viewing Capacity Details
- Resource O&M
- Automated O&M
-
Faults
- Diagnosis Tools
- Alarms
-
Incident Management
- Incidents
- Creating an Incident
- Rejecting an Incident
- Resubmitting an Incident After Rejection
- Forwarding Incidents
- Handling Incidents
- Upgrading/Downgrading an Incident
- Adding Remarks
- Starting a War Room
- Handling an Incident
- Verifying Incident
- Creating an Improvement Ticket For An Incident
- Incident History
- WarRoom
- Improvement Management
- Issue Management
- Forwarding Rules
- Data Source Integration Management
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
Help Center/
Cloud Operations Center/
User Guide/
Automated O&M/
Patch Management/
Repairing Patches
Repairing Patches
Updated on 2025-03-17 GMT+08:00
The patch repair feature allows users to repair non-compliant ECS, CCE, or BMS instances scanned by patches. The patch repair feature upgrades or installs non-compliant patches on ECS or CCE instances.
Scenarios
Repair patches on COC.
Procedure
- Log in to COC.
- In the navigation pane on the left, choose Resource O&M > Automated O&M. Click Patch management. On the displayed page, click Patch Scanning.
- Select the instance whose patch needs to be repaired and click Repair.
Figure 1 Select the target instances
- Set the batch policy.
Batch policy
- Automatic: The selected hosts are automatically divided into multiple batches based on the preset rule.
- Manual: You can manually create multiple batches and add instances to each batch as required.
- No batch: All hosts to be executed are in the same batch.
Figure 2 Selecting the batch policy - Set a suspension policy.
Suspension threshold: You can set the execution success rate. When the number of failed hosts reaches the pre-set suspension threshold figure, the service ticket status becomes abnormal and the service ticket stops being executed.Figure 3 Suspension policy
- Set whether to allow restart.
NOTE:
If you select No, you need to restart the system at another time due to some patches only taking effect after the system is restarted.
- Confirm the execution information. If the information is correct, click OK.
Figure 4 Execution information page
Parent topic: Patch Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.