FAILED_QA:

After unregistering the client system using " insights-client --unregister", we can still see Insights status as Reporting for the client system in Satellite webui ( All Hosts page)


Insights:	Reporting

# rpm -qa | grep rh_cloud
tfm-rubygem-foreman_rh_cloud-3.0.24.1-1.el7sat.noarch

When we use legacy_upload = False option in the /etc/insights-client/insights-client.conf I see the --test-connection works properly


# insights-client --test-connection --net-debug
GET https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/v1/branch_info
GET branch_info status: 200
Running Connection Tests...
=== Begin Upload URL Connection Test ===
Testing https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/ingress/v1/upload
HTTP Status Code: 202
HTTP Status Text: Accepted
HTTP Response Text: {"request_id":"12b555601eda4fb48bc624d0a2f0d463","upload":{"account_number":"540155"}}
Successfully connected to: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/ingress/v1/upload
=== End Upload URL Connection Test: SUCCESS ===

=== Begin API URL Connection Test ===
Testing https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/apicast-tests/ping
HTTP Status Code: 200
HTTP Status Text: OK
HTTP Response Text: {"status":"available"}
Successfully connected to: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/apicast-tests/ping
=== End API URL Connection Test: SUCCESS ===

Connectivity tests completed successfully
See /var/log/insights-client/insights-client.log for more details.

Please ignore the earlier comment, it was for the bz #1984550 update. 

Sorry for the confusion.

You will have to wait until the aging mechanism decides it's a stale host. By default it's 48 hours and then the status updating task will run and move it to "red".

You can speed up the process, if you patch the code:

The interval lives here: https://github.com/theforeman/foreman_rh_cloud/blob/e61ab9d2af519e3aec5b9f40a4de324d27d9811f/app/models/insights_client_report_status.rb#L2
you can change it to 1.minutes
The task schedule lives here: https://github.com/theforeman/foreman_rh_cloud/blob/e61ab9d2af519e3aec5b9f40a4de324d27d9811f/lib/foreman_rh_cloud/engine.rb#L152
you can change the cron line to '0 * * * *' and it will run every minute.

@ahumbe can you please retest it with the patches?

Based on Comment 6, adding need info flag for Ashish.

Hi Shim,

I tried the suggested changes and set REPORT_INTERVAL =  1.minutes instead of 48.hours and also the cron change followed by # foreman-maintain service restart 

Even after 5-10 mins, I see insights status as Reporting.


Regards,
Ashish

Manually executing rake command to update the insights client aging data with " ForemanTasks.sync_task(InsightsCloud::Async::InsightsClientStatusAging)" command helps to reflect the webui status immediately. 

After executing the rake task, the Insights Status gets updated as " Not reporting " for the system which is unregistered from Insights, so marking this Bugzilla verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9.4 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2948