Based on our research, we encountered the following:
Failed communication with SUSE servers, where outdated systems are incompatible with updated SUSE infrastructure. Communication failures can also result from network or firewall restrictions, expired security certificates, misconfigured system clocks, and misconfigured proxy settings.
Post-update boot failure (SLES 15 SP3) where a specific security package crashes after an unsuccessful or incomplete update.
To resolve communication failures, we first reset the system configurations and re-registered it with SUSE Servers. To ensure there are no connectivity issues, we fixed time clock issues and verified network access. Finally, we manually created a fresh instance in the cloud platform from an updated version of the same instance that was causing the problem.
We solved the boot failure by first locking the problematic package as a preventive measure against further failures. Then, we migrated to an updated Service Pack (SP6), unlocked the package, and updated it so that it is compatible with the new environment.
For a more detailed, step-by-step description of how we solved this problem, read this
blog.