Description of problem:
After the upgrade to CloudForms 4.2, there is a hotfix to install cfme-126.96.36.199-2.el7cf.x86_64.rpm, to fix failed refresh for the OCP 3.3 provider. Once the hotfix is applied, these WARN messages are showing up in the logs:
[----] W, [2017-01-19T23:15:24.136788 #41978:369138] WARN -- : MIQ(MiqServer.check_migrations_up_to_date) database schema is from a newer version of the product and may be incompatible. Schema version is . Missing files: [20160106214719, 20160425161345]
[----] W, [2017-01-19T23:15:24.136884 #41978:369138] WARN -- : MIQ(MiqServer.check_migrations_up_to_date) appliance should be updated to match database version
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The issue here is that migrations that have been run previously are no longer present on the filesystem. This would be an issue if we ever wanted to migrate "down", but we don't ever do that in production.
The warning can be "fixed" by removing the version rows for the two migrations from the schema_migrations table.
What do you think Jason? Is that a thing we should do (write a new migration to edit schema_migrations) or should we be deleting the contents of the migrations rather than the entire files?
New commit detected on ManageIQ/manageiq/master:
Author: Nick Carboni <ncarboni>
AuthorDate: Wed Apr 19 11:51:51 2017 -0400
Commit: Nick Carboni <ncarboni>
CommitDate: Wed Apr 19 11:51:51 2017 -0400
Remove the rows from schema_migrations for deleted migration files
These migrations were removed in #11197 and #9696 and are now
causing a warning in the logs if the schema_migrations row is present,
but the files are not.
db/migrate/20170419154137_remove_deleted_migration_timestamps.rb | 9 +++++++++
1 file changed, 9 insertions(+)
create mode 100644 db/migrate/20170419154137_remove_deleted_migration_timestamps.rb
Verified in 188.8.131.52
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.