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 "You are running an outdated Graylog version" is stuck at the version of graylog when this system notification first appears #19725

Open
drewmiranda-gl opened this issue Jun 24, 2024 · 1 comment
Labels

Comments

@drewmiranda-gl
Copy link
Member

Graylog periodically checks to see if a newer version is available. If a newer version is available, graylog displays a system notification such as:

image

However, if one does not clear/dismiss this system notification, you will never receive another system notification of this type.

Expected Behavior

If a newer version of graylog is available, replace the existing system notification.

Current Behavior

System notification is frozen in time, never updates, may incorrectly say the "latest version is XYZ" when that could an older version.

Possible Solution

Steps to Reproduce (for bugs)

  1. Install a graylog version older than the latest
  2. Wait for the periodical to run (I believe this occurs 5 minutes after a graylog node "boots" and once every 30 min)
  3. Wait for a newer version of graylog to be released (or hijack the update URL somehow, https://versioncheck.graylog.com/check )

Please let me know if there are any questions. This is very minor but this was brought up by @Joel-Duffield-Graylog when he noticed a cluster saying the latest version was a much older version than the latest.

@drewmiranda-gl
Copy link
Member Author

drewmiranda-gl commented Jun 24, 2024

This could also open a discussion for how system notifications currently behave in that they block any future system notifications of the same type from appearing. The same behavior occurs with new Data adapter system notifications where even though this failure is happening constantly, the system notification only shows the first time the system notification was triggered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant