- 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
Show all
Patch Management
Patch Management allows users to manage patches on ECS or Cloud Container Engine (CCE) instances by scanning and repairing patches.
Currently, patch management supports only servers that can access the public network. You can bind an EIP or NAT gateway to implement patch management.
Before managing patches, ensure that the regions where the execution machines are deployed and the operating systems (OSs) of the execution machines are supported by the existing patch management feature, and the second-party package, on which the patch management feature is dependent on, is contained in the execution machine, and the package functions are normal. Otherwise, patches may fail to be managed.
OS |
Product |
---|---|
Huawei Cloud EulerOS |
Huawei Cloud EulerOS 1.1 Huawei Cloud EulerOS 2.0 |
CentOS |
CentOS 7.2 CentOS 7.3 CentOS 7.4 CentOS 7.5 CentOS 7.6 CentOS 7.7 CentOS 7.8 CentOS 7.9 CentOS 8.0 CentOS 8.1 CentOS 8.2 |
EulerOS |
EulerOS 2.2 EulerOS 2.5 EulerOS 2.8 EulerOS 2.9 EulerOS 2.10 |
Type |
Dependency Item |
---|---|
Python environment |
Python (Python2 or Python3) DNF software packages (depended by Huawei Cloud EulerOS 2.0, CentOS 8.0 or later, and EulerOS 2.9 or later) YUM software packages (depended by Huawei Cloud EulerOS 1.1, versions earlier than CentOS 8.0 and EulerOS 2.9) lsb-release software package |
Software package management tool |
RPM |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.