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.

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

Created attachment 1689567 [details]
Generated At date

This is fixed in Foreman 2.1, attaching related issue and PR.

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29839 has been resolved.

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.

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