Bug 1836845

Summary: "Generate at" in report template should be current date
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: ReportingAssignee: Ranjan Kumar <rankumar>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: dchaudha, egolov, mhulan, mshira, oezr, oprazak, pcreech
Target Milestone: 6.8.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-2.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:02:42 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:
Attachments:
Description Flags
Generated At date none

Description Ranjan Kumar 2020-05-18 10:09:34 UTC 
Description of problem: Generated at in Report template shows default date '1-1-1970 '


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


How reproducible: Always


Steps to Reproduce:

Actual results:  Shows date 1 Jan 1970


Expected results: Should show selected date as Today's Date


Additional info: Screen Attached
Comment 1 Ranjan Kumar 2020-05-18 10:10:22 UTC 
Created attachment 1689567 [details]
Generated At date
Comment 2 Ondřej Ezr 2020-06-04 11:09:48 UTC 
This is fixed in Foreman 2.1, attaching related issue and PR.
Comment 3 Bryan Kearney 2020-06-04 12:05:11 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29839 has been resolved.
Comment 4 Lukáš Hellebrandt 2020-06-25 09:56:33 UTC 
Verified with Sat 6.8 snap 5.0.

Tried to generate a report in WebUI, date field is empty by default. When trying to enter a date through the calendar widget, the default is current date and time.
Comment 7 errata-xmlrpc 2020-10-27 13:02:42 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.8 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-2020:4366