Long-Term Supported Versions

Known Issues

The FIPS boot mode of the kernel has not been fully authenticated. The FIPS boot may be abnormal. I17Z18
When libvirt is used to start the GlusterFS VM, a 300-byte memory leak occurs each time. For details about the discussion, click https://github.com/gluster/glusterfs/issues/818. I185CH
When the libvirt interface is used to continuously perform disk hot swap operations, there is a possibility that the hot remove interface returns a success message, but the disk is not removed and cannot be hot swapped again. You can stop the VM and then restart it. I1C72L
There is a low probability that an unknown installation exception occurs when the x86_64 VM is used for installation. In this case, install the x86_64 VM again. I1C8HS
CVE-2012-0039: When a local application calls the g_str_hash function, the application continuously consumes CPU resources, causing DoS attacks. This issue will not be resolved in the community.
CVE-2015-9541: When Qt attempts to parse the abnormal SVG files which are constructed to launch exponential XML entity extension attacks, the memory may be insufficient. For details about the discussion, click https://codereview.qt-project.org/c/qt/qtbase/+/293909.
Before compiling some open-source packages, you need to install basic software such as GDB, GCC, and make. Otherwise, the compilation fails due to lack of dependency.
AArch64 and x86_64 have different definitions of the character type. As a result, an error is reported during the self-check using Coreutils, Augeas, and Diffutils. You can add the --fsigned-char compilation option to solve the problem.
For 20.03 LTS, if you run the rpm -Uvh XXX command (XXX indicates the version, for example, mysql-8.0.21-1.oe1.aarch64.rpm) to upgrade mysql-8.0.17-3.oe1 to the latest version, the functions are unavailable after the upgrade. You can use either of the following methods to upgrade the version. The following uses the upgrade from mysql-8.0.17-3.oe1 to mysql-8.0.21-1.oe1 as an example:
- Method 1: Run the following upgrade command:
```
# rpm -Uvh mysql-8.0.21-1.oe1.aarch64.rpm --noscripts 
```
- Method 2: Run the following commands to uninstall the MySQL of the earlier version and then install the MySQL of the new version:
```
# rpm -e mysql-8.0.17-3.oe1      
# rpm -ivh mysql-8.0.21-1.oe1.aarch64.rpm
```

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.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

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

Correctness

● 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.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.