Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Currently, task export contains times in UTC. That is a bit confusing when one needs to correlate a task execution time frame (with times in the UTC) with other logs (with times in local timezone). One nas to keep in mind the difference every time and has to convert the times - that is error prone.
Please update task export (or the way how the tasks are written to psql) to provide date× in local timezone.
Version-Release number of selected component (if applicable):
Sat 6.1.7
How reproducible:
100%
Steps to Reproduce:
1. Have a Satellite in non-UTC timezone
2. Create a task (import manifest, sync a repo, register a contetn host, whatever)
3. Get task export:
foreman-rake foreman_tasks:export_tasks
4. Check in the export when the task was started/finished
Actual results:
4. task export having times in UTC
Expected results:
4. task export to have times in local timezone
Additional info:
In Sat6.2:
- foreman tasks (satellite.example.com/foreman_tasks/tasks) have timestamps in local timezone - that's OK
- dynflow tasks (/foreman_tasks/dynflow) have timestamps in UTC - that's not OK
/me tried some hack in removing "utc" references in dynflow code but it didnt help
Ivan,
do you have an easy idea why dynflow writes all timestamps in UTC and not in local timezone, like foreman-tasks does?
Becuase dynflow itself is a low-level tool, that can serve users from different timezones and it itself doesn't need the concept of timezones for the thing it's doing. From implementation point of view, it's more useful to store all the times in UTC, when it comes to scheduling, timeouts etc.
(In reply to Ivan Necas from comment #7)
> Becuase dynflow itself is a low-level tool, that can serve users from
> different timezones and it itself doesn't need the concept of timezones for
> the thing it's doing. From implementation point of view, it's more useful to
> store all the times in UTC, when it comes to scheduling, timeouts etc.
It makes sense to _store_ times in UTC. I am asking for _showing_ the times to end users in the timezone of the server.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.