Bug 2049828

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