Merge pull request #8312 from rnirek/patch-15

AB#4166: Update suse-public-cloud-connectivity-registration-issues.md

Author: AmandaAZ

support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot connectivity and registration for SUSE SLES VMs
 description: Troubleshoot scenarios in which an Azure VM that has a SUSE Linux Enterprise Server image can't connect to the SUSE Subscription Management Tool (SMT) repository.
-ms.date: 02/04/2025
+ms.date: 02/26/2025
 author: rnirek
 ms.author: hokamath
 ms.reviewer: adelgadohell, mahuss, esanchezvela, scotro, v-weizhu, divargas
@@ -221,29 +221,15 @@ If instances aren't regularly updated, they can become incompatible with our upd
     ```bash
     sudo zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin libsuseconnect suseconnect-ruby-bindings docker libcontainers-common
     ```
-
-    > [!IMPORTANT]
-    > The latest `cloud-regionsrv-client-10.3.11-150300.13.19.1` introduces new dependencies (`libcontainers-common` and `docker`). This causes dependency errors. When [cloud instance repos fail because of outdated packages](https://www.suse.com/support/kb/doc/?id=000021552), the latest packages are installed:
-    >```ouput
-    >cloud-regionsrv-client 10.3.11-150300.13.19.1
-    >cloud-regionsrv-client-plugin-azure 2.0.0-150300.13.19.1
-    >```
-
-4. If there are dependency errors from the latest package, `cloud-regionsrv-client-10.3.11-150300.13.19.1`, you must downgrade `cloud-regionsrv-client` and `cloud-regionsrv-client-plugin-azure`. Otherwise, skip this step.
-
-    ```bash
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-10.3.7-150300.13.14.1.noarch.rpm
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-plugin-azure-2.0.0-150300.13.14.1.noarch.rpm
-    ```
-5. Run the following commands:
+4. Run the following commands:
 
     ```bash
     sudo find /root/packages/ -type f -name "*.rpm" -exec cp {} /root/packages/rpms/ \;
     sudo cd /root/packages
     sudo tar -czvf suse-public-registration.tgz rpms
     ```
 
-6. Transfer `suse-public-registration.tgz` to the broken instance:
+5. Transfer `suse-public-registration.tgz` to the broken instance:
 
     ```bash
     sudo scp /root/packages/suse-public-registration.tgz user@targetip:/tmp
@@ -252,7 +238,7 @@ If instances aren't regularly updated, they can become incompatible with our upd
     > [!NOTE]
     > Replace `user` and `targetip` as appropriate.
 
-7. Sign in to the broken instance to extract and install the packages:
+6. Sign in to the broken instance to extract and install the packages:
 
     ```bash
     sudo cd tmp
@@ -261,11 +247,12 @@ If instances aren't regularly updated, they can become incompatible with our upd
     sudo zypper --no-refresh --no-remote --non-interactive install --force *.rpm
     ```
 
-8. Register the VM again:
+7. Register the VM again:
 
     ```bash
     sudo registercloudguest --force-new
     ```
+For more information, see [Cloud instance repos fail due to outdated packages](https://www.suse.com/support/kb/doc/?id=000021552).
 
 ## Scenario 3: General registration issues