-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
-
False
-
-
We want to reproduce exactly the same scenario as in SWATCH-2942.
This is happening when the system facts from HBI is:
{ "rhsm": { "orgId": "11164879", "MEMORY": 16, "RH_PROD": [ "388", "479", "387", "389" ], "IS_VIRTUAL": true, "ARCHITECTURE": "x86_64", "SYNC_TIMESTAMP": "2024-09-27T00:06:26.672635574Z", "SYSPURPOSE_SLA": "Standard", "SYSPURPOSE_ROLE": "Red Hat Enterprise Linux Server", "SYSPURPOSE_USAGE": "Production" } }
Note the product IDs (RH_PROD) and the SYSPURPOSE_ROLE is "Red Hat Enterprise Linux Server".
In this scenario, we should identify the instance with both:
- "RHEL for x86" because the SYSPURPOSE_ROLE is "Red Hat Enterprise Linux Server" (and also the product ID has 479
- "rhel-for-sap-x86" because the product IDs contains 388 and 389
At the moment, we're only identifying "RHEL for x86".
- blocks
-
SWATCH-2942 EngID 389 is not considered as "RHEL for SAP x86"
-
- Closed
-
- is related to
-
SWATCH-2942 EngID 389 is not considered as "RHEL for SAP x86"
-
- Closed
-
- mentioned on