Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The reported facts and reports are ignoring machine timezone #1171

Closed
ares opened this issue Mar 13, 2021 · 0 comments · Fixed by #1333
Closed

The reported facts and reports are ignoring machine timezone #1171

ares opened this issue Mar 13, 2021 · 0 comments · Fixed by #1333
Assignees

Comments

@ares
Copy link
Member

ares commented Mar 13, 2021

SUMMARY

A fresh report causes out of sync configuration status. This is caused by the timestamp in the report being without timezone information. The same problem is present for facts upload. We should unify the way how we fetch the current time information and include the TZ information. At the same time, the format can be a bit tweaked so it's more native to the Ruby that parses it.

ISSUE TYPE
  • Bug Report
ANSIBLE VERSION

N/A


COLLECTION VERSION

all


KATELLO/FOREMAN VERSION

N/A


STEPS TO REPRODUCE
  1. have a machine with non +00:00 TZ
  2. create a report and upload it to Foreman
  3. visit the report page, you can see the reported at information being wrong
EXPECTED RESULTS

The time zone should be correctly parsed

ACTUAL RESULTS
The time zone is ignored so the time is considered as UTC
evgeni added a commit to evgeni/foreman-ansible-modules that referenced this issue Jan 3, 2022
evgeni added a commit to evgeni/foreman-ansible-modules that referenced this issue Jan 3, 2022
evgeni added a commit to evgeni/foreman-ansible-modules that referenced this issue Jan 3, 2022
evgeni added a commit that referenced this issue Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants