Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1860928 - Last checkin date/time not update when hypervisor is checked in via virt-who
Summary: Last checkin date/time not update when hypervisor is checked in via virt-who
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.7.0
Hardware: All
OS: All
high
high
Target Milestone: 6.9.0
Assignee: Partha Aji
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-27 13:18 UTC by anerurka
Modified: 2024-06-13 22:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1890905 (view as bug list)
Environment:
Last Closed: 2021-04-21 13:17:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Copy of the debug output from virt-who reproducer. (43.63 KB, text/plain)
2020-08-11 13:45 UTC, Rohit Rajput 		no flags Details
HOTFIX RPM for Satellite 6.7.4 (10.87 MB, application/x-rpm)
2020-10-14 01:28 UTC, wclark 		no flags Details
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31004 0 Normal Closed reporter_id needs to be set for hypervisor update 2021-02-15 07:04:30 UTC
Red Hat Knowledge Base (Article) 5369751 0 None None None 2020-09-03 12:14:17 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:17:57 UTC

Description anerurka 2020-07-27 13:18:09 UTC 
Description of problem:

Last checkin date/time not update when hypervisor is checked in via virt-who

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

Red Hat Satellite v.6.7

How reproducible:


Steps to Reproduce:
1. Configure virt-who
2. Last check-in for the Hypervisor is not "updated"

Actual results:

Last Checkin is "not" updated whenever virt-who is restarted in Red Hat Satellite v.6.7

Expected results:

Last check-in date should be updated.

Additional info:

Currently virt-who only sends the reports if changes detected compared to the previous shared reports to satellite. If no changes have happened in the reports, then the hypervisor will not change the check-in date/time for the hypervisor.

It appears to be a possible regression, where hypervisor Last checkin date/time not updated. As per BZ, [X] and [Y], this should have been fixed with Candlepin 2.9 and Satellite v.6.7, but the problem is still observed.

[X] https://bugzilla.redhat.com/show_bug.cgi?id=1639479 
[Y] https://bugzilla.redhat.com/show_bug.cgi?id=1652549
Comment 11 William Poteat 2020-08-19 13:41:26 UTC 
The virt-who log shows that the hypervisor heartbeat is not whitelisted on the server. Once this is remedied, then the hypervisor checkin time should be updated.
Comment 16 anerurka 2020-09-11 14:57:23 UTC 
(In reply to William Poteat from comment #11)
> The virt-who log shows that the hypervisor heartbeat is not whitelisted on
> the server. Once this is remedied, then the hypervisor checkin time should
> be updated.

Hi William,

I believe you were referring to below error in the virt-who log.

====
2020-08-11 19:10:23,635 [virtwho.destination_1902698268407011099 ERROR] MainProcess(2023):Thread-3 @virt.py:_send_data:609 - Error during heartbeat: Communication with subscription manager failed with code 404: HTTP error (404 - Not Found): 
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 604, in _send_data
    self.dest.hypervisorHeartbeat(config=self.config, options=self.options)
  File "/usr/lib/python2.7/site-packages/virtwho/manager/subscriptionmanager/subscriptionmanager.py", line 274, in hypervisorHeartbeat
    raise ManagerError("Communication with subscription manager failed with code %d: %s" % (e.code, str(e)))
ManagerError: Communication with subscription manager failed with code 404: HTTP error (404 - Not Found): 
=====


- Upgrading to Sat 6.7.3, above error is not longer observed [https://bugzilla.redhat.com/show_bug.cgi?id=1832936]

- However primary problem i.e last check-in not update still persist.

I'll upload a fresh virt-who debug log along with reproducer details in the next comment.

- AmeyaN
Comment 25 Partha Aji 2020-10-06 17:29:12 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/31004 from this bug
Comment 29 Bryan Kearney 2020-10-12 20:02:17 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31004 has been resolved.
Comment 30 wclark 2020-10-14 01:28:32 UTC 
Created attachment 1721347 [details]
HOTFIX RPM for Satellite 6.7.4
Comment 31 wclark 2020-10-14 01:33:41 UTC 
HOTFIX RPM is available for Satellite 6.7.4

INSTALLATION INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite server

2. Download the attached Hotfix RPM and copy it to Satellite server

3. # yum install ./tfm-rubygem-katello-3.14.0.31-2.HOTFIXRHBZ1860928.el7sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart
Comment 37 errata-xmlrpc 2021-04-21 13:17:39 UTC 
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 (Moderate: Satellite 6.9 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-2021:1313
Note You need to log in before you can comment on or make changes to this bug.