Known Issues

No.	Issue Ticket Number	Issue Description	Severity Level	Impact Analysis	Workaround Measure
1	I5LZXD	openldap build problem in openEuler:22.09	Minor	The case fails to be executed during the build. This problem is caused by the case design. The impact is controllable. Switch to the sleep mode and wait until the operation is complete. The operation occasionally fails in high-load scenarios.	Skip related case. Track the upstream community to solve the problem.
2	I5NLZI	[openEuler 22.09 rc2] Some application icons in the initiator are improperly displayed.	Minor	Only the initiator icon of the DDE desktop is improperly displayed. This issue does not affect functions. The overall impact on usability is controllable.	Switch the theme to avoid this problem.
3	I5P5HM	[22.09_RC3_EPOL][arm/x86] Failed to stop afterburn-sshkeys@.service is displayed when uninstalling the afterburn.	Minor
4	I5PQ3O	[openEuler-22.09-RC3] An error is reported when the ompi-clean -v -d parameter is executed.	Major	This package is used by the NestOS and has a limited application scope. By default, this package is enabled by the core user in the NestOS. This package has little impact on the server version.	No workaround is provided by the SIG.
5	I5Q2FE	udisks2 build problem in openEuler:22.09	Minor	The case fails to be executed during the build. The environment is not retained, and the problem does not recur during long-term local build.	Keep tracking the build success rate in the community.
6	I5SJ0R	[22.09RC5 arm/x86] An error is reported when executing podman create --blkio-weight-device /dev/loop0:123:15 fedora ls.	Minor	blkio-weight is a kernel feature of version 4.xx. Not supported in version 5.10	Upgrade the podman component.

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.