Troubleshoot ZStack Cloud upgrade dependency and license issues

Issue/Introduction

This article applies to abnormal qemu or libvirt binaries or dependencies after an upgrade, abnormal repositories, third-party authentication synchronization failures, management service startup failures caused by licensing, a mismatched UKEY or localized-platform license, and abnormal CPU license recognition. For an upgrade or license issue, check the release branch, ISO or local repository, RPM history, license file, machine fingerprint, service dependencies, and product compatibility boundary together.

Symptoms

• After qemu is upgraded, a binary reports an error, a library function is missing, or retrieving the qemu version is abnormal.
• After an upgrade, a host is disconnected, a dependency package cannot be found, or a repository is abnormal.
• After an upgrade, third-party authentication, LDAP, or SSO synchronization fails and the logs contain SSLHandshakeException.
• After a management node restart, the management service fails to start and reports a license or authorization issue.