Bug 2119234

Summary: Timezone/timestamp issue with Ansible configuration management reports run via Capsule servers
Product: Red Hat Satellite Reporter: Puja Singh <pujsingh>
Component: Ansible CollectionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Griffin Sullivan <gsulliva>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.7CC: egolov, oezr, osousa, pmendezh, pwaghmar
Target Milestone: 6.12.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ansible-collection-redhat-satellite-3.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2136507 (view as bug list) Environment:
Last Closed: 2022-11-16 13:35:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2136507    

Comment 1 Brad Buckingham 2022-08-18 14:06:36 UTC
Moving to POST as the upstream issue is closed and PR below merged:
https://github.com/theforeman/foreman-ansible-modules/pull/1333

Comment 2 Griffin Sullivan 2022-09-15 16:45:19 UTC
Verified in 6.12 snap 11

Ansible config reports correctly display execution time.

Steps to Reproduce:

1) Run all ansible roles on a host

2) Check job under Monitor > Jobs

3) Check job under Monitor > Configuration Management

Results:

Steps 2 and 3 display the same time.

Comment 6 errata-xmlrpc 2022-11-16 13:35:21 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 (Important: Satellite 6.12 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-2022:8506

Comment 7 Brad Buckingham 2022-12-12 23:29:16 UTC
*** Bug 2136507 has been marked as a duplicate of this bug. ***