In version 1.1.2, during installation, the system architecture was determined after determining the MD5 files

[lipeng186]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

String md5 = FileUtil.readString( Constants.MASTER_MANAGE_PACKAGE_PATH + Constants.SLASH + serviceRoleInfo.getPackageName() + ".md5", Charset.defaultCharset()); installServiceRoleCommand.setPackageMd5(md5); if ("aarch64".equals(hostEntity.getCpuArchitecture()) && FileUtil.exist(Constants.MASTER_MANAGE_PACKAGE_PATH + Constants.SLASH + serviceRoleInfo.getDecompressPackageName() + "-arm.tar.gz")) { installServiceRoleCommand.setPackageName(serviceRoleInfo.getDecompressPackageName() + "-arm.tar.gz"); logger.info("find arm package {}", installServiceRoleCommand.getPackageName()); String armMd5 = FileUtil.readString(Constants.MASTER_MANAGE_PACKAGE_PATH + Constants.SLASH + serviceRoleInfo.getDecompressPackageName() + "-arm.tar.gz.md5", Charset.defaultCharset()); installServiceRoleCommand.setPackageMd5(armMd5); }

What you expected to happen

Adjusting the order of verification

How to reproduce

In version 1.1.2, during installation, the system architecture was determined after determining the MD5 files

Anything else

No response

Version

v1.1.2

Are you willing to submit PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[datasophon]

Please forgive me for not being able to agree with your question. If the system architecture is aarch64 and the component has an arm version package, we will use the arm version package and its md5