-
Notifications
You must be signed in to change notification settings - Fork 91
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
Make events_backread switchable #491
Conversation
OpenStack should expect timestamps in UTC. However some production environments might work in different way. The safest way fix seems to be extend event_backread feature with possibility to turn it off. Event backread can be now turned off by setting :event_backread_seconds settings option to number less than 1, e.g. 0. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734338
Checked commit aufi@d854ee9 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aufi makes sense to be able to disable it 👍
Although what is the exact issue this is causing? I don't see how the backread would cause not receiving events. (also by disabling this, will we loose events again?)
@Ladas There was problem with intepretation time with timezones between CF and OSP, disabling backread avoids timestamp manipulation on CF side. |
@aufi |
Make events_backread switchable (cherry picked from commit a600714) https://bugzilla.redhat.com/show_bug.cgi?id=1734338
Ivanchuk backport details:
|
Make events_backread switchable (cherry picked from commit a600714) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1740767
Hammer backport details:
|
OpenStack should expect timestamps in UTC. However some production environments
might work in different way. The safest way fix seems to be extend event_backread
feature with possibility to turn it off.
Event backread can be now turned off by setting :event_backread_seconds
settings option to number less than 1, e.g. 0.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734338