Skip to content

Commit f00c5d6

Browse files
authored
Update suse-public-cloud-connectivity-registration-issues.md
Edit review per CI 6640
1 parent e31445a commit f00c5d6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Troubleshoot connectivity and registration for SUSE SLES VMs
2+
title: Troubleshoot Connectivity and Registration for SUSE SLES VMs
33
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.
44
ms.date: 05/12/2025
55
author: rnirek
@@ -200,7 +200,7 @@ sudo tail /var/log/cloudregister
200200
2025-01-29 20:20:06,917 ERROR:No response from: [('23.101.171.119', '2603:1030:603::2e9'), ('23.101.164.199', '2603:1030:603::625'), ('23.96.231.74', '2603:1030:603::2e6')]
201201
```
202202

203-
The output indicates that a connectivity error exists. However, this is not true. This indication occurs because the error handling process in the registration scripts doesn't show the certificate errors from the old libraries.
203+
The output indicates that a connectivity error exists. However, this isn't true. This indication occurs because the error handling process in the registration scripts doesn't show the certificate errors from the old libraries.
204204

205205
The script output might also mistakenly indicate that a certificate for one of the SMT IPs that's displayed in the `sudo tail /var/log/cloudregister` command output can't be found. This is also a library issue, not an issue that affects the CA list on the VM.
206206
@@ -216,7 +216,7 @@ If instances aren't regularly updated, they can become incompatible with our upd
216216
```bash
217217
sudo mkdir -p /root/packages/rpms
218218
```
219-
3. Download the following packages based on SLES versions of the affected virtual machine:
219+
3. Download the following packages based on SLES versions of the affected VM:
220220

221221
SLES 12
222222
```bash

0 commit comments

Comments
 (0)