Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Preparations

Updated on 2024-08-28 GMT+08:00

RPM packages can be updated manually (using osmt update) or automatically (using the background osmt-agent service). You need to perform the following operations for both manual and automatic updates.

  1. Confirm that the repository is configured correctly.

    Check whether the parameters in the /etc/yum.repos.d/hce.repo file are configured correctly. The correct configuration is as follows:

    [base]
    name=HCE $releasever base
    baseurl=https://repo.huaweicloud.com/hce/$releasever/os/$basearch/
    enabled=1
    gpgcheck=1
    gpgkey=https://repo.huaweicloud.com/hce/$releasever/os/RPM-GPG-KEY-HCE-2
    
    [updates]
    name=HCE $releasever updates
    baseurl=https://repo.huaweicloud.com/hce/$releasever/updates/$basearch/
    ......
    NOTE:

    Incorrect configuration may result in OSMT upgrade failures or unexpected upgrades.

  2. Run dnf update osmt -y to update OSMT.
  3. Configure the /etc/osmt/osmt.conf file.

    OSMT updates RPM packages based on the osmt.conf file. Configure the file as required.

    [auto]
    #if auto_upgrade is True, the osmt-agent will auto upgrade rpms use osmt.conf and reboot between time interval we specified
    #the value of cycle_time means the  osmt-agent will check upgrade every cycle_time seconds, default 86400s(1 day)
    #When a configuration item has a line break, you need to leave a space or tab at the beginning of the line
    auto_upgrade = False
    cycle_time = 3600
    minimal_interval = 3600
    auto_upgrade_window = "22:00-05:00"
    auto_upgrade_interval = 1
    
    [Package]
    There are three rules of filters, all enabled by default. Severity will be effect only when the types contain security, it is the subtype of security.
    # The following are the three rules:
    #    1. whitelist has the highest priority, if whitelist is configured then ignore other rules and filter out the whitelist packages from the full list of packages to be upgrade
    #    2. Filter the update range by types, when the types contain security, further filter the severity of security updates severity, only upgrade the severity level of security.
    #    3. Filter blacklist to remove packages in blacklist from types filter results, and packages which depend on packages in blacklist will also be removed.
    # filters must contain at least one types rule, if the types rule is empty, the -a option will not upgrade any packages (by default all 3 filters are enabled).
    
    filters = "types, blacklist"
    whitelist = ""
    
    # types include: security, bugfix, enhancement, newpackage, unknown
    # if types is empty, no package will be upgrade
    # types = security, bugfix, enhancement, newpackage, unknown
    types = "security"
    # severity is the subtype of security, include: low, moderate, important, critical
    severity = "important, critical"
    blacklist = ""
    # The rpm package that requires a system reboot to take effect after the upgrade
    need_reboot_rpms = "kernel,kernel-debug,kernel-debuginfo,kernel-debuginfo-common,kernel-devel,kernel-headers,kernel-ori,kernel-tools,kernel-tools-libs,glibc,glibc-utils,glibc-static,glibc-headers,glibc-devel,glibc-common,dbus,dbus-python,dbus-libs,dbus-glib-devel,dbus-glib,dbus-devel,systemd,systemd-devel,systemd-libs,systemd-python,systemd-sysv,grub2,grub2-efi,grub2-tools,openssl,openssl-devel,openssl-libs,gnutls,gnutls-dane,gnutls-devel,gnutls-utils,linux-firmware,openssh,openssh-server,openssh-clients,openssh-keycat,openssh-askpass,python-libs,python,grub2-pc,grub2-common,grub2-tools-minimal,grub2-pc-modules,grub2-tools-extra,grub2-efi-x64,grub2-efi-x64-cdboot,kernel-cross-headers,kernel-source,glibc-all-langpacks,dbus-common,dbus-daemon,dbus-tools,systemd-container,systemd-pam,systemd-udev,grub2-efi-aa64,grub2-efi-aa64-cdboot,grub2-efi-aa64-modules,openssl-perl,openssl-pkcs,kernel-tools-libs-devel,glibc-debugutils,glibc-locale-source,systemd-help,grub2-efi-ia32-modules,grub2-efi-x64-modules,grub2-tools-efi,grub2-help,openssl-pkcs11,grub2-efi-ia32-cdboot,osmt"
    preinstalled_only = False
    
    [backup]
    store_path = /var/log
    backup_dir = /etc,/usr,/boot,/var,/run
    exclude_dir =
    recover_service =
    
    #the minimum resources required(MB)
    [resource_needed]
    #min_req_boot_space = 100
    #min_req_backup_space = 8192
    #min_req_root_space = 1536
    #min_req_memory = 512
    
    [cmdline]
    cmdline_value =
    
    [conflict]
    #conflict_rpm = test1,test2
    
    [strategy]
    timeout_action = "stop"
    timeout_action_before = 0
    
    [check]
    daemon_whitelist = "sysstat-collect.service, sysstat-summary.service, systemd-tmpfiles-clean.service"
    check_systemd_running_jobs = True
    # the timeout of query systemd services
    query_timeout = 30
    check_rpm_packages = True
    Table 1 Major configuration items in osmt.conf

    Configuration Item

    Description

    [auto]

    • auto_upgrade: specifies the RPM package update method. The default value is False.
      • True: RPM packages can be updated either manually or automatically.
      • False: RPM packages can only be updated manually.
    • If auto_upgrade is set to True, the following parameters are available:
      • cycle_time: defines the interval of checking for available updates, in seconds. The default value is 3600.
      • minimal_interval: defines the minimum interval (in seconds) between the start time and end time specified using osmt update -b. The default value is 3600.
      • auto_upgrade_window: defines the start time and end time of automatic updates using the osmt-agent service. The value is in the format of "HH:MM-HH:MM".

        If the end time is smaller than the start time, the update period covers two dates. For example, 22:00-05:00 indicates an update period from 22:00 on the current day to 05:00 on the next day.

      • auto_upgrade_interval: defines the minimum interval between two automatic updates, in days.
    • If auto_upgrade is set to False, only the following parameters are available, and any other [auto] parameter configured will not take effect.
      • cycle_time: defines the interval of checking for available updates, in seconds. The default value is 3600.
      • minimal_interval: defines the minimum interval (in seconds) between the start time and end time specified using osmt update -b. The default value is 3600.
    • motd_setup: specifies whether to enable the login prompt. The default value is True.
      • True: Enable the login prompt.
      • False: Disable the login prompt. After the setting, the login prompt is deleted immediately and will not be generated again. If the option is enabled again, you need to run the osmt update -s command or any upgrade command to trigger the generation again.

    [Package]

    • filters: specifies the update scope. The value can be types, blacklist, or whitelist.

      For example, specifying blacklist will not update the RPM packages in the blacklist.

      • types: the type of RPM packages to be updated.
      • blacklist: the RPM package blacklist.

        Packages added to the blacklist will not be updated. If an RPM package depends on a package in the blacklist, this RPM package will also not be updated.

      • whitelist: the RPM package whitelist.

        If the whitelist and blacklist are not configured, all RPM packages will be updated.

        The whitelist has a higher priority than the blacklist, meaning that if an RPM package is added to both lists, it will be updated.

        NOTE:

        The blacklist and whitelist specified in the command are applied, and those defined in the configuration file will not.

    • need_reboot_rpms: lists the RPM packages that need an OS restart.

      Automatic updates using osmt-agent will not update packages in need_reboot_rpms. To update these packages during automatic updates, you must run osmt update --auto --reboot_config always or osmt update --auto --reboot_config "Restart time".

    • preinstalled_only: If this parameter is set to True, only the RPM packages in /etc/osmt/preinstalled.list are required to be upgraded.

    [backup]

    • store_path: the directory under which the backup directory is created.

      During the upgrade, OSMT creates the .osbak directory under store_path. If .osbak already exists, run the osmt remove command to delete it first.

    • backup_dir: the directories that need to be backed up. Directories /etc, /usr, /boot, /var, and /run are backed up by default during an update and cannot be removed.
    • recover_service: OSMT checks whether the status of each service in the list is the same before and after the upgrade. If the status of a service is changed, OSMT will restore the service status.
      NOTE:

      The path in [backup] must be an absolute path.

    [cmdline]

    cmdline_value: determines the startup items after an upgrade. Configure correct startup items to ensure that the OS can be started properly. By default, the default startup items of Huawei Cloud EulerOS are used.

    [conflict]

    conflict_rpm: specifies the RPM packages that will be deleted if there is a conflict during the upgrade.

    [check]

    • check_systemd_running_jobs: specifies whether to check for services that are being started or stopped in the system before the upgrade.
      • True (default): Any services that are being started or stopped in the system will be checked before the upgrade.
      • False: Any services that are being started or stopped in the system will not be checked before the upgrade.
    • check_rpm_packages: specifies whether to check the status of RPM packages in the system before the upgrade, including missing package dependencies and whether duplicate packages.
      • True (default): The status of the RPM packages will be checked before the upgrade.
      • False: The status of the RPM packages will not be checked before the upgrade.
    NOTE:

    You are advised not to modify other configuration items. For details, see Description of the /etc/osmt/osmt.conf File.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback