Bug 1709902
| Summary: | Dates specified in search queries don't respect current user time zone | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Marek Hulan <mhulan> |
| Component: | Reporting | Assignee: | Marek Hulan <mhulan> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | egolov, inecas, kgaikwad, mhulan, oprazak |
| Target Milestone: | 6.6.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-scoped_search-0.4.7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-22 19:49:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marek Hulan
2019-05-14 14:03:22 UTC
Created from redmine issue https://projects.theforeman.org/issues/26757 Upstream bug assigned to mhulan Reproducing steps: 1) login as a user in some non +0 timezone, e.g. +0200 2) generate a report template Monitor -> Report templates -> whichever one, schedule for later, e.g. 2 minutes from now 3) observer the report does not start rendering as expected, based on your timezone it either start earlier or later (by hours) With the fix 1) scheduling works as expected *** Bug 1709901 has been marked as a duplicate of this bug. *** Verified with Sat 6.6 snap 4. Tested using Firefox 66.0.3 and Chromium 73.0.3683.86. Tested both with e-mail and polling. 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, 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-2019:3172 |