Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJessica Richards
2022-02-02 18:45:31 UTC
Description of problem:
When customers use Satellite 6.10 to run all Ansible roles against their hosts, the results (whether failures or successes) appear under Monitor > "Config Management" with future-dated times. Moreover, when they click on any of the results, they see errors like this:
Host times seem to be adrift!
Host reported time is 2022-02-02 01:46:32 -0700
Satellite report creation time is 2022-02-01 18:46:32 -0700
Which is an offset of about 7 hours
However, the customer's hosts don't show this clock drift. We also compared time zone differences, and they didn't match the reported offsets, either.
I was able to reproduce this issue on my own Satellite 6.10 server as well, using both the customer's Ansible roles and Red Hat's Ansible roles (specifically, RedHatInsights.insights-client).
However, when altering the search criteria to look for the Satellite server, we can see updates from puppet that don't have this problem.
Version-Release number of selected component (if applicable):
satellite-6.10.1-2.el7sat.noarch
ansible-test-2.9.27-1.el7ae.noarch
ansible-runner-1.4.6-1.el7ar.noarch
ansible-collection-redhat-satellite-2.2.0-1.el7sat.noarch
ansible-2.9.27-1.el7ae.noarch
satellite-6.10.2-1.el7sat.noarch
ansible-test-2.9.27-1.el7ae.noarch
ansible-runner-1.4.6-1.el7ar.noarch
ansible-collection-redhat-satellite-2.2.0-1.el7sat.noarch
ansible-2.9.27-1.el7ae.noarch
How reproducible:
100%
Steps to Reproduce:
1. assign one or more ansible roles to a host
2. go to Hosts > All Hosts
3. run all ansible roles against a host
Actual results:
- result shows up under Monitor > "Config Management" with a future time
- the result details themselves report clock drift
Expected results:
- result should show up under Monitor > "Config Management" with a past but recent time
- the result details themselves shouldn't erroneously report clock drift
note: the customer's servers had different timezones defined. their timezones were three hours apart, whereas their error message showed a 5 hour "drift". however, when i reproduced the issue in my environment, my servers were in the same timezone, and the satellite/ansible-reported drift was even greater.
also note: i was unable to reproduce this problem in satellite 6.9.
Hi, this is most likely a duplicate of bz#2035907 that is aligned to 6.10.z so the fix should get to a 6.10 z stream soon.
*** This bug has been marked as a duplicate of bug 2035907 ***