PMM Security Check not detecting latest version for 5.7 instance under pmm monitoring
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
AFFECTED CS IDs
CS0026031
CS0025503
Attachments
4
Smart Checklist
Activity
Show:
Michael Okoko April 20, 2022 at 6:36 AM
agreed. Also, I think it's a general problem with how we approach version checks in Advisors (Postgres, MySQL, and Mongo). While the bug described specifically is now fixed, we could re-open it and update the details or open a new ticket to move version checks online and involve the tech leads in that.
Sveta Smirnova April 19, 2022 at 9:09 PM
this is what this bug is about. Version check should not be hard-coded and should happen online. Otherwise users cannot rely on this feature: upgrade schedule for PMM could be different from upgrade schedule for other products.
Michael Okoko April 18, 2022 at 9:36 AM
turned out changes to checked don't really take effect until we deploy a new version. Explains why it was still not showing the latest version earlier - Looks like it does now.
Iwo Panowicz April 1, 2022 at 1:57 PM
Done
Created April 1, 2022 at 8:31 AM
Updated March 6, 2024 at 1:24 AM
Resolved April 19, 2022 at 10:10 AM
Issue: PMM Security Check not detecting latest version for 5.7 instances under pmm monitoring. I do see the latest version check for 8.0 version.
Tested added, .7.36 and .0.26 version in pmm monitoring.
Running Security Checks --> Failed checks showing the latest version available for 8.0 i.e 8.0.27 as of this date , but 5.7 does not show latest version available i.e 5.7.37
Newer version of Percona Server for MySQL is available: Current version is 8.0.26, the latest available version is 8.0.27.