Description of problem: All the time customers are looking for a way to check the last_checkin just to remove the content host automatically (based on timeframe). For example, virt-who-* servers, hypervisors with more than 10 days without checking could be removed. Version-Release number of selected component (if applicable): 6.6.z How reproducible: 100% Steps to Reproduce: 1. We don't have this report available. 2. 3. Actual results: not available Expected results: List of content hosts with last_checkin --- [root@wallsat66 ~]# echo "select h.name,h.id,ksf.host_id,ksf.last_checkin,ksf.hypervisor from katello_subscription_facets as ksf, hosts as h where h.id=ksf.host_id and ksf.hypervisor='t' order by ksf.last_checkin" | su - postgres -c "psql foreman" name | id | host_id | last_checkin | hypervisor ----------------------------------------------+----+---------+---------------------+------------ virt-who-esxi1.lab.eng.rdu2.redhat.com-1 | 16 | 16 | 2020-01-10 18:36:44 | t virt-who-esxi2.lab.eng.rdu2.redhat.com-1 | 17 | 17 | 2020-01-10 18:36:44 | t virt-who-esxi5.lab.eng.rdu2.redhat.com-1 | 19 | 19 | 2020-01-10 18:36:44 | t virt-who-newserver.lab.eng.rdu2.redhat.com-1 | 18 | 18 | 2020-01-10 19:37:04 | t --- Additional info:
Upstream bug assigned to wpinheir
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/28787 has been resolved.
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 (Important: Satellite 6.15.0 release), 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/RHSA-2024:2010