This functionality exists without the need to turn on the UI worker role already. The UI is running this: if version != available_version _("%{name} domain: Current version - %{version}, Available version - %{available_version}") % {:name => domain.name, :version => version, :available_version => available_version} end These methods can be directly run in console: => MiqAeDomain.find_by(:name => "ManageIQ").version "gaprindashvili-7" => "gaprindashvili-7" irb(main):017:0> MiqAeDomain.find_by(:name => "ManageIQ").available_version "gaprindashvili-7" => "gaprindashvili-7" I'm curious if that comparison is enough for the purposes of this ticket.
Absolutely, Ryan. I'm currently working out where the best place for that logging is since we have a variety of plausible options available to us.
(In reply to drew uhlmann from comment #7) > Absolutely, Ryan. I'm currently working out where the best place for that > logging is since we have a variety of plausible options available to us. Log is a good place but we have to make sure with log rotation it still available.. As an example if you do it as Emvserverd starting it will be only once and few weeks later it will be not available
I don't understand why the log rotation matters. The only time this information should be at all relevant is when we do updates of the existing system. I don't understand why we would care about this information from months ago. I think that the ideal implementation of this is that the plugins should have a health check, so we could conceivably say something like, loop over all the plugins and if they have a health check method implemented, run it. But that still doesn't address the question of how often the check for that should run, or where it should be stored.
If log rotation is a concern, I think we could do this check and log message as part of the last_startup.txt that's generated when the server starts up. As long as the version is still mismatched, we'd continually log the same thing and we wouldn't lose it. https://github.com/ManageIQ/manageiq/blob/8d219521d39198f7dab21492212b9fdf2a2e2263/app/models/miq_server.rb#L236
(In reply to Joe Rafaniello from comment #10) > If log rotation is a concern, I think we could do this check and log message > as part of the last_startup.txt that's generated when the server starts up. > As long as the version is still mismatched, we'd continually log the same > thing and we wouldn't lose it. > > https://github.com/ManageIQ/manageiq/blob/ > 8d219521d39198f7dab21492212b9fdf2a2e2263/app/models/miq_server.rb#L236 Excellent idea
https://github.com/ManageIQ/manageiq/pull/18756
Hey Ganesh, yeah, those steps aren't going to work to verify this. For verification purposes, you really would like to have a system with a different RedHat domain on disk version versus the version in the db. So you'd like to grep the logs for this string: "domain version on disk differs from db version" after doing an upgrade to an appliance, when the version discrepancy exists.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4199