Description of problem: Registered the system with the insight using " insights-client --register --display-name=eprasad-SaaS-testing" command, the command execution was successful, waited 5 more minutes and then opened Red Hat Cloud Services platform, navigated to inventory tab, searched the system using the display name set at the time of registering the system with insight client. System the doesnt appear there. Version-Release number of selected component (if applicable): [root@static ~]# insights-client --version Client: 3.0.3-9 Core: 3.0.80-1 How reproducible: always for me Steps to Reproduce: 1. Register the system with subscription Manager. subscription-manager register 2. Attach entitlements to the systems. subscription-manager attach --auto 3. Install insight client on the system. #yum install insights-client -y 4. Register the system to insight. # insights-client --register --display-name=eprasad-SaaS-testing Actual results: System doesn't show up the inventory app () Expected results: System should show up immediately. Additional info:
@Prasad Did you try finding the system in the UI using another fact, such as its hostname?
I am also facing the same issue. Registered machines are not reflecting on the portal.
Hey Sagar, Please provide host information such as the hostname for those you are unable to see in the portal. These additional details will allow us to trace and attempt to diagnose the problem. Thanks, Rob
Hey Prasad, I noticed you have one step missing before your registration, have you edited the insights-client.conf? You'll have to manually set legacy_upload=False in order to use this. The following play can solve that issue: - name: configure to use non legacy upload lineinfile: path: /etc/insights-client/insights-client.conf line: legacy_upload=False insertafter: EOF create: yes
Pavol, can you please try to reproduce this and leave a comment with your findings. If this works for you, I am tempted to close it until we get more information.
Prasad - We believe this issue should be all set at this time. Are you still encountering the reported issue?
Haven't heard back and engineering/BU believe its fixed. Closing out.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days