Bug 1711255 - [RFE] Unable to search obfuscated hostname systems in the inventory.
Summary: [RFE] Unable to search obfuscated hostname systems in the inventory.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: Inventory
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Shaun Dunning
QA Contact: Brandon Tweed
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-17 11:32 UTC by Amar Huchchanavar
Modified: 2019-12-02 16:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-02 16:23:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Amar Huchchanavar 2019-05-17 11:32:30 UTC
Description of problem:

There is no option to search 'obfuscate_hostname=True'  system over the portal.

~~~
If you access cloud.redhat.com and browse the host inventory it will onlly show the hostname. In case of obfuscated hostnames this is not very useful. In the old insights page or on satellite insights the hosts are also showing the display name. 

Please bring the "display name" into the inventory view.
~~~
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Set  obfuscate_hostname=True in insights-client.conf 
~~
# Obfuscate IP addresses
obfuscate=True

# Obfuscate hostname
obfuscate_hostname=True
~~

2. #insights-client  --register 


Actual results:
systems get registered with 'host1.example.com' (next system would be host2.example.com ) 


Expected results:
There is no filter over the portal to find these systems. 

Additional info:
#curl -vv -u <PORTAL_LOGIN>  https://access.redhat.com/r/insights/v3/systems/?account_number=<ACCOUNT_NO> | python -mjson.tool

Comment 3 Ian Page Hands 2019-12-02 16:23:08 UTC
Closing this. Today I can set and search via displayname in the Inventory.


Note You need to log in before you can comment on or make changes to this bug.