From 44670e672da6d8c29d47ac3716c52d431b2d4bf0 Mon Sep 17 00:00:00 2001
From: Tahlia Richardson <3069029+tahliar@users.noreply.github.com>
Date: Wed, 13 Mar 2024 14:32:58 +1000
Subject: [PATCH] Replace SMT troubleshooting with RMT troubleshooting

---
 xml/art-quickstart.xml | 113 +++++++++++++++++++++++++++--------------
 1 file changed, 74 insertions(+), 39 deletions(-)

diff --git a/xml/art-quickstart.xml b/xml/art-quickstart.xml
index d183071..c7dec06 100644
--- a/xml/art-quickstart.xml
+++ b/xml/art-quickstart.xml
@@ -167,47 +167,82 @@
  <section xml:id="troubleshoot-quickstart">
   <title>Troubleshooting</title>
   <variablelist>
-   <varlistentry>
-    <term>Mirroring completes with errors</term>
-    <listitem>
-     <para>
-      If some packages could not be downloaded because of timeouts, rerun the
-      <command>smt-mirror</command> command until all packages are downloaded.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term>Cannot access the &productname; repository</term>
-    <listitem>
-     <para>
-      The <filename>repodata</filename> directory on the &smt; server will not
-      be available until all of the packages for that repository are downloaded.
-      If some packages could not be downloaded to the &smt; server because of
-      timeouts during the first mirroring, rerun the <command>smt-mirror</command>
-      command until all packages are downloaded.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry>
-    <term><command>yum update</command> fails because of package conflicts</term>
-    <listitem>
-     <para>
-      If <package>sles_es-release-server</package> conflicts with existing packages,
-      try the following workaround:
-     </para>
-<screen>&prompt.root;<command>rm -r /usr/share/redhat-release</command></screen>
-     <para>
-      On CentOS, this removes the symbolic link between
-      <filename>redhat-release</filename> and <filename>centos-release</filename>.
-     </para>
-     <important role="compact">
+    <varlistentry>
+      <term><systemitem>nginx.service</systemitem> is inactive after installing the
+      <package>rmt-server</package> package</term>
+      <listitem>
       <para>
-       Make sure you run this command <emphasis>without</emphasis> a <literal>/</literal>
-      after <literal>redhat-release</literal>.
+        Continue the procedure to configure &rmt; in &yast;. This often resolves
+        the issue. If that fails, Apache might be installed on your server, and
+        must be disabled. Apache conflicts with NGINX because both web servers
+        listen on port 80.
       </para>
-     </important>
-    </listitem>
-   </varlistentry>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>&productname; doesn't appear in <command>rmt-cli products list</command>
+      after <command>rmt-cli sync</command></term>
+      <listitem>
+      <para>
+        Check your network. If the network is down, <command>rmt-cli sync</command> fails without
+        showing an error.
+      </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>Mirroring completes with errors</term>
+      <listitem>
+      <para>
+        If some packages could not be downloaded because of timeouts, rerun the
+        <command>rmt-cli mirror</command> command until all packages are downloaded.
+      </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>Setup script cannot access the &productname; repository</term>
+      <listitem>
+      <para>
+        The <filename>repodata</filename> directory on the &rmt; server will not
+        be available until all of the packages for that repository are downloaded.
+        If some packages could not be downloaded to the &rmt; server because of timeouts
+        during the first mirroring, rerun the <command>rmt-cli mirror</command>
+        command until all packages are downloaded.
+      </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>Setup script cannot install <package>SUSEConnect</package> because of
+      package dependencies</term>
+      <listitem>
+      <para>
+        &productname; only supports the latest minor release of &rhla; or CentOS Linux.
+        If your system is running the latest version and <package>SUSEConnect</package>
+        still has package dependency issues, try the following workaround:
+      </para>
+      <orderedlist>
+        <listitem>
+        <para>
+          Edit the <filename>rmt-client-setup-res</filename> script to add
+          <literal>--skip-broken</literal> to the following line:
+        </para>
+<screen>$DNF install SUSEConnect librepo <emphasis role="bold">--skip-broken</emphasis></screen>
+        </listitem>
+        <listitem>
+        <para>
+          Run the script and accept any proposed package changes.
+          <package>SUSEConnect</package> will be skipped.
+        </para>
+        </listitem>
+        <listitem>
+        <para>
+          Run the script a second time. The package changes from the first attempt
+          can sometimes resolve the package dependency issues, allowing the second
+          attempt to successfully install <package>SUSEConnect</package>.
+        </para>
+        </listitem>
+      </orderedlist>
+      </listitem>
+    </varlistentry>
   </variablelist>
  </section>
  <xi:include href="common_legal.xml"/>