Bug 1417313
| Summary: | Schema missing warnings in logs | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | myoder |
| Component: | Providers | Assignee: | Nick Carboni <ncarboni> |
| Status: | CLOSED ERRATA | QA Contact: | luke couzens <lcouzens> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.7.0 | CC: | fsimonce, gblomqui, jfrey, jhardy, mfeifer, myoder, ncarboni, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | 5.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | black | ||
| Fixed In Version: | 5.9.0.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-01 13:09:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Bug | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
myoder
2017-01-27 23:09:13 UTC
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: https://github.com/ManageIQ/manageiq/commit/4a44664a08f67f5127ad4d04581f17d0c48a03a8 commit 4a44664a08f67f5127ad4d04581f17d0c48a03a8 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. https://bugzilla.redhat.com/show_bug.cgi?id=1417313 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 5.9.0.3 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/RHSA-2018:0380 |