Bug 2089074 - [Sat6] Option to obfuscate hostnames in "Satellite WebUI >> Configure > Inventory Upload >> Obfuscate host names" does not obfuscate hosts with "virt-who-FQDN" [NEEDINFO]
Summary: [Sat6] Option to obfuscate hostnames in "Satellite WebUI >> Configure > Inven...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Inventory
Version: 6.9.0
Hardware: All
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Shimon Shtein
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 00:28 UTC by jalviso
Modified: 2023-07-21 05:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
jalviso: needinfo? (sshtein)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18876 0 None None None 2023-07-11 13:05:15 UTC

Description jalviso 2022-05-23 00:28:06 UTC 
Description of problem:

Option to obfuscate hostnames in "Satellite WebUI >> Configure > Inventory Upload >> Obfuscate host names" does not obfuscate hosts with "virt-who-FQDN".

Version-Release number of selected component (if applicable): 6.9+


How reproducible: Always


Steps to Reproduce:
1. Turn on "Obfuscate host names" in 
   Satellite WebUI >> Configure > Inventory Upload

2. Upload the Organization's inventory 

3. Wait for 24 hours to get all inventory uploaded to console.redhat.com

Actual results:

Hostnames with "virt-who-FULLY_QUAIFIED_DOMAIN_NAME" is still listed as it is, it is not obfuscated.

Expected results:

Same way as other hostname-FQDN, "virt-who-FULLY_QUAIFIED_DOMAIN_NAME" shoud be obfuscated too.

Additional info:
Comment 1 Shimon Shtein 2023-07-11 13:02:37 UTC 
Can you please download and share the report?
You can download the report by going to:
Configure -> Inventory upload, click the "Uploading" tab and then the "Download report" button.
Then please share the report.
Note You need to log in before you can comment on or make changes to this bug.