You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
have a machine with non +00:00 TZ
create a report and upload it to Foreman
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
The text was updated successfully, but these errors were encountered:
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
ANSIBLE VERSION
N/A
COLLECTION VERSION
all
KATELLO/FOREMAN VERSION
N/A
STEPS TO REPRODUCE
EXPECTED RESULTS
The time zone should be correctly parsed
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: