Long-Term Supported Versions

    Resolved Issues

    For details about the complete issue list, click https://gitee.com/organizations/src-openeuler/issues.

    For details about the complete kernel submission records, click https://gitee.com/openeuler/kernel/commits/openEuler-1.0-LTS.

    Table 1 lists the resolved issues.

    Table 1 Resolved issues




    [Kernel bug] The lscpu command on the ARM server cannot be used to display the CPU dominant frequency, and the CPU cache is incorrect.


    Failed to pull an image using the isula pull or curl pull command.


    Delete redundant gpg sig file for shadow-4.6.


    The unbuffer command is unavailable.


    The arping -w parameter is invalid.


    The oops error occurs when the latest LTP pty03 test case is executed.


    500 scheduled tasks are started. After 4 to 5 minutes, the tasks cannot be processed and the system stops responding.


    The warning information captured when the Kata container fails to be started is insufficient for fault locating. More errors need to be printed.


    In kata-runtime remote mode, the kata-runtime kill is not called when the isula rm -f command is executed. As a result, residual data exists.


    The soft lockup is found when the open function is triggered in the ext4 file system.


    Isulad breaks down when a pod is created using kubectl.

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份