Backport43 - Improved subscription-matcher Messages description. (#2746)

.changelog

@@ -4,6 +4,7 @@
 # - Fixed error in Bat section of Upgrade Guide (bsc#1234567)
 # For guidelines: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Changelog_section_.28.25changelog.29
 
+- Added detailed information about the messages produced by subscription matcher
 - Added Pay-as-you-go as supported service on Azure to the Public Cloud Guide
 - Added and fixed configuration details in Troubleshooting Renaming
   Server in Administration Guide

modules/administration/pages/subscription-matching.adoc

@@ -16,7 +16,8 @@ The report includes product names and the number of systems that remain unmatche
 The [guimenu]``Pins`` tab allows you to associate individual clients to the relevant subscription.
 This is especially useful if the subscription manager is not automatically associating clients to subscriptions successfully.
 
-The [guimenu]``Messages`` tab shows any errors that occurred during the matching process.
+The [guimenu]``Messages`` tab shows all the messages generated by subscription matcher during the matching process. 
+They provide information to help understand the results and to improve the matching.
 
 You can also download the reports in .csv format, or access them from that command prompt in the [path]``/var/lib/spacewalk/subscription-matcher/`` directory.
 

modules/reference/pages/audit/audit-subscription-matching.adoc

@@ -1,7 +1,7 @@
 [[ref-audit-subscription]]
 = Subscription Matching
 
-The menu:Audit[Subscription Matching] section provides reports that match your currently installed clients to your existing product subscriptions.
+The menu:Audit[Subscription Matching] section provides reports that match your currently installed clients to your existing product subscriptions.
 Subscription matching reports provide information about clients that do not have a subscription, and subscription start and end dates.
 
 
@@ -27,15 +27,19 @@ Table entries that have already expired are shown in grayscale.
 For messages relating to subscription matching, navigate to the [guimenu]``Messages`` tab.
 
 [[subscription-matching-status]]
-[cols="1,1,1", options="header"]
-.Subscription Matching Statuses
+[cols="1,1,1,1", options="header"]
+.Subscription Matching Messages
 |===
-| Status                  | Description | Action
-| Unsupported Part Number | The detected part number is unknown or unsupported. | Call {suse} support and open a Service Request ticket to have the part number added to the product.
-| Physical Guest          | A client is reporting as virtual, but could be a physical client. | Check the client hardware data.
-| Guest with Unknown Host | A virtual client has an unknown host. | Check the virtual host manager (VHM) configuration to ensure it is reporting correctly.
+| Message                 | Type | Description | Action
+| Unsupported part number detected | Debug | The detected part number is unknown or unsupported. | Call {suse} support and open a Service Request ticket to have the part number added to the product.
+| Physical system is reported as virtual guest, please check hardware data          | Debug | A client is reporting as virtual, but could be a physical client. | Check the client hardware data.
+| Virtual guest has unknown host, assuming it is a physical system | Warning | A virtual client has an unknown host. During the matching process, it was treated as a physical system. This might translate into a wrong subscription assignment. | Check the virtual host manager (VHM) configuration to ensure it is reporting correctly.
 For Linux-based hosts using ``libvirt``, check that the host is registered, and that the virtual host system type is set correctly.
-| Unknown CPU Count       | Unable to determine how many CPUs a client has. {productname} will default to 16 CPUs. | Schedule a hardware refresh on this client.
+| System has an unknown number of sockets, assuming 16 | Warning | Unable to determine how many CPUs a client has. {productname} used the default value of 16 CPUs every time the number was relevant for matching a subscription. This might translate into a wrong subscription assignment. | Schedule a hardware refresh on this client.
+| Two subscriptions with the same part number are in a bundle | Informational | Two subscriptions were identified to be part of a bundle and, as result, they were merged together during the computation process. | No actions needed.
+| Two subscriptions with the same part number (and other properties) have been merged together | Informational | Two subscription shared multiple common properties and they were merged together during the computation process. | No actions needed.
+| Pinned match adjusted due to merged subscriptions | Informational | A user defined pin was updated since the chosen subscription was merged with another one. | No actions needed.
+| Subscription with unsupported part number and no associated product has been ignored. | Informational | An unknown subscription without any associated product has been detected and it was ignored during the matching process. | No actions needed.
 |===