5.1 -"Public Cloud Support" section partially wrong

CHANGELOG.md

@@ -1,3 +1,5 @@
+- Fixed PAYG documentation to reflect the changes in providing support
+  (bsc#1252869)
 - Fixed wrong --ssl-db-server-{cert|key} parameters in Specialized Guides
   (bsc#1249462)
 - Added additional step for client deletion in Client Configuration

modules/specialized-guides/pages/public-cloud-guide/payg-support.adoc

@@ -1,13 +1,13 @@
 = Public Cloud Support
-:description: Learn how to create a supportconfig archive containing detailed system information for easy troubleshooting and submission to Global Technical Support
+:description: Learn how to collect detailed system information for easy troubleshooting and submission to Global Technical Support
 :revdate: 2025-02-26
 :page-revdate: {revdate}
 ifeval::[{uyuni-content} == true]
 
 :noindex:
 endif::[]
 
-== {byos} and {payg} Support
+== {byos} and {payg} support
 
 
 Regardless of the public cloud service you use or the plan you choose, {suse} has you covered with support. 
@@ -29,56 +29,27 @@ The Public Cloud Information Tracker (PINT) provides information about the image
 PINT is available at link:https://pint.suse.com/[pint.suse.com] and provided as an API and command-line tool with the [literal]``python3-susepubliccloudinfo`` package from the Public Cloud Module repository.
 
 
-== Collecting System Information with `supportconfig`
+== Collecting system information
 
-To create a TAR archive with detailed system information that you can hand over to Global Technical Support, use the command `supportconfig`. 
-The command-line tool is provided by the package `supportutils` which is installed by default.
+To create a TAR archive with detailed system information that you can hand over to Global Technical Support, run the command:
 
-Depending on which packages are installed on your system, some of these packages integrate `supportconfig` plug-ins. 
-When `supportconfig` is executed, all plug-ins are executed as well, creating one or more result files for the archive. 
-This has the benefit that the only topics checked are those that contain a specific plug-in for them. 
-`supportconfig` plug-ins are stored in directory [path]``/usr/lib/supportconfig/plugins/``.
-
-The following procedure shows how to create a `supportconfig` archive, but without submitting it to support directly.
-
-
-.Procedure: Creating a [literal]``supportconfig`` Archive
-
-. Run [literal]``supportconfig`` as root. 
-  Usually, it is enough to run this tool without any options. 
-  Some options are very common and are displayed in the following list:
-+
-.Options:
 ----
--E MAIL, -N NAME, -O COMPANY, -P PHONE
-
-Sets your contact data: e-mail address (-E)
-Company name (-O)
-Your name (-N)
-Your phone number (-P)
-
--i KEYWORDS, -F
-Limits the features to check. 
-The placeholder KEYWORDS is a comma-separated list of case-sensitive keywords. 
-Get a list of all keywords with supportconfig -F.
+mgradm support config
 ----
-+
-. Wait for the tool to complete the operation.
-
-. The default archive location is `/var/log`, with the file name format being **scc_HOST_DATE_TIME.txz**
 
+The default archive location is [path]``/var/log``, with the file name format being **scc_HOST_DATE_TIME.txz**
 
 
 
-== Opening a New Support Case
+== Opening a new support case
 
 To open a new support case for your cloud {payglongform} instance, you need to generate a **supportconfig** file and then follow the steps listed on:
 
 link:https://scc.suse.com/cloudsupport[{scclongform} Cloudsupport]
 
 
 
-== Billing Services and Troubleshooting
+== Billing services and troubleshooting
 
 
 === billing-data-service
@@ -111,7 +82,7 @@ This service is maintained by public cloud team.
 
 
 
-=== mgr-check-payg.service
+=== uyuni-payg-timer
 
 This service checks if **billing-data-service** is installed and running.
 It also checks if the **csp-billing-adapter-service** is installed and running.
@@ -120,37 +91,29 @@ If these services are not running or installed it will attempt to install and st
 Consequences:: 
 If one of the previous billing services is not running and cannot be installed or started **spacewalk** will refuse to start.
 
-Check `journalctl -u mgr-check-payg.service` for additional issues.
-
+Check `journalctl -u uyuni-payg-timer.service` for additional issues.
 
 
-=== Continuous Compliance Checks
 
-.Procedure: Compliance Checks
-. The **payg-dimension-computation** taskomatic task must be active.
+=== Continuous compliance checks
 
+.Procedure: Compliance checks
+[role=procedure]
+____
 . Is the billing server running at http://localhost:18888/ ?
 
 . Is the **csp-billing-adapter.service** running?
 
 . What is the status of the **csp-billing-adapter** located in `/var/lib/csp-billing-adapter/csp-config.json`?
 
 
-The following files and packages are checked for tampering::
-* Billing-data-service
-* Csp-billing-adapter-service
-* Python3-csp-billing-adapter
-* Python3-csp-billing-adapter-local
-* Python3-csp-billing-adapter-amazon
-* python3-csp-billing-adapter-azure
-
-
 Failed Checks::
 Failed checks are logged in:
 
 * `/var/log/rhn/rhn_web_ui.log`
-* `/var/log/hrn/rhn_taskomatic_daemon.log`
+* `/var/log/rhn/rhn_taskomatic_daemon.log`
 
 Consequences::
 * No more actions will be executed.
 * `reposync` will stop synchronizing channels.
+____