Support #22429
closed
Jobs page fails to open with error message "PG::UndefinedTable: ERROR: relation "job_invocations" does not exist"
Description
"Oops, we're sorry but something went wrong PG::UndefinedTable: ERROR: relation "job_invocations" does not exist LINE 1: SELECT "job_invocations".* FROM "job_invocations" ORDER BY... ^ : SELECT "job_invocations".* FROM "job_invocations" ORDER BY job_invocations.id DESC LIMIT 50 OFFSET 0"
This is after an upgrade to foreman 1.16.0. I think I deleted the schema from the database because of the "PG::DuplicateColumn: ERROR: column "version" of relation "dynflow_schema_info" already exists" problem. I resolved that by downgrading pg and sequel, but db:migrate and db:seed don't seem to re-create the job_invocations table.
Is there a foreman-rake command that can fix this? Is it possible to rebuild my database without destroying all of the info that's currently in it?
Updated by Anonymous almost 7 years ago
- Project changed from Foreman to Foreman Remote Execution
- Category set to Foreman
- Priority changed from High to Normal
Updated by Anonymous almost 7 years ago
- Related to Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environment added
Updated by Anonymous over 6 years ago
- Related to deleted (Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environment)
Updated by Anonymous over 6 years ago
- Is duplicate of Bug #20050: ruby-sequel-pg DEB pollutes Foreman ruby gem environment added