"There are migrations pending in the system" error when foreman-rake migrate:status reports ok

Support
1

Hello,

Our foreman GUI is currently reporting

ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending in
the system.

And the same does hammer. foreman-rake migrate:status output seems to be ok
also (attached)

This is a little context on how we reached the current status:

After a problem with postgresql we had to recover foreman and candlepin DBs
from dump files.

Our instance is Foreman 1.15 - Katello 3.4. Unfortunately, we didn't know
about katello-backup and katello-restore being introduced in version 3.1,
so we backed up the DBs like we used to in our old katello 2:

pg_dump -Fc foreman > $BDIR/foreman.dump pg_dump -Fc candlepin >
$BDIR/candlepin.dump

And we recovered them like this:

dropdb foreman dropdb candlepin
pg_restore -C -d postgres $BDIR/foreman.dump pg_restore -C -d postgres
$BDIR/candlepin.dump

Now, Postgresql is up, the databases are there:

                              List of databases

Name | Owner | Encoding | Collate | Ctype | Access
privileges

··· -----------+----------+----------+-------------+-------------+------------------------ candlepin | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =Tc/postgres + > > > > > postgres=CTc/postgres + > > > > > candlepin=CTc/postgres foreman | foreman | UTF8 | en_US.utf8 | en_US.utf8 | =Tc/foreman + > > > > > foreman=CTc/foreman + > > > > > postgres=CTc/foreman postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + > > > > > postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + > > > > > postgres=CTc/postgres (5 rows)

Foreman and candlepin users have access privileges, I’ve seen our data is
in the tables and there are even connections going on. All components have
started up successfully but we still can’t access the GUI or execute hammer
commands.

Could anybody please shed some light on this issue? Is there any
post-recover step that we may have missed?

Thanks!

2

Attaching foreman-rake migrate:status output

foreman-rake output.txt (10.5 KB)

··· El jueves, 20 de julio de 2017, 13:06:54 (UTC+2), María Sierra escribió: > > Hello, > > Our foreman GUI is currently reporting > > ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending > in the system. > > And the same does hammer. foreman-rake migrate:status output seems to be > ok also (attached) > > This is a little context on how we reached the current status: > > After a problem with postgresql we had to recover foreman and candlepin > DBs from dump files. > > Our instance is Foreman 1.15 - Katello 3.4. Unfortunately, we didn't know > about katello-backup and katello-restore being introduced in version 3.1, > so we backed up the DBs like we used to in our old katello 2: > > pg_dump -Fc foreman > $BDIR/foreman.dump pg_dump -Fc candlepin > > $BDIR/candlepin.dump > > And we recovered them like this: > > dropdb foreman dropdb candlepin > pg_restore -C -d postgres $BDIR/foreman.dump pg_restore -C -d postgres > $BDIR/candlepin.dump > > > Now, Postgresql is up, the databases are there: > > List of databases > Name | Owner | Encoding | Collate | Ctype | Access > privileges > > -----------+----------+----------+-------------+-------------+------------------------ > candlepin | postgres | UTF8 | en_US.utf8 | en_US.utf8 | > =Tc/postgres + > > > > > > > postgres=CTc/postgres + > > > > > > > candlepin=CTc/postgres > foreman | foreman | UTF8 | en_US.utf8 | en_US.utf8 | =Tc/foreman > + > > > > > > > foreman=CTc/foreman + > > > > > > > postgres=CTc/foreman > postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | > template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres > + > > > > > > > postgres=CTc/postgres > template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres > + > > > > > > > postgres=CTc/postgres > (5 rows) > > Foreman and candlepin users have access privileges, I've seen our data is > in the tables and there are even connections going on. All components have > started up successfully but we still can't access the GUI or execute hammer > commands. > > Could anybody please shed some light on this issue? Is there any > post-recover step that we may have missed? > > Thanks! > >
3

any chance you simply didnt restart your foreman services after the
db:migrate?

··· On Thu, Jul 20, 2017 at 2:09 PM, María Sierra wrote:

Attaching foreman-rake migrate:status output

El jueves, 20 de julio de 2017, 13:06:54 (UTC+2), María Sierra escribió:

Hello,

Our foreman GUI is currently reporting

ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending
in the system.

And the same does hammer. foreman-rake migrate:status output seems to be
ok also (attached)

This is a little context on how we reached the current status:

After a problem with postgresql we had to recover foreman and candlepin
DBs from dump files.

Our instance is Foreman 1.15 - Katello 3.4. Unfortunately, we didn’t know
about katello-backup and katello-restore being introduced in version 3.1,
so we backed up the DBs like we used to in our old katello 2:

pg_dump -Fc foreman > $BDIR/foreman.dump pg_dump -Fc candlepin >
$BDIR/candlepin.dump

And we recovered them like this:

dropdb foreman dropdb candlepin
pg_restore -C -d postgres $BDIR/foreman.dump pg_restore -C -d postgres
$BDIR/candlepin.dump

Now, Postgresql is up, the databases are there:

                              List of databases

Name | Owner | Encoding | Collate | Ctype | Access
privileges
-----------±---------±---------±------------±-----------
-±-----------------------
candlepin | postgres | UTF8 | en_US.utf8 | en_US.utf8 |
=Tc/postgres +
> > > > >
postgres=CTc/postgres +
> > > > >
candlepin=CTc/postgres
foreman | foreman | UTF8 | en_US.utf8 | en_US.utf8 |
=Tc/foreman +
> > > > >
foreman=CTc/foreman +
> > > > >
postgres=CTc/foreman
postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
=c/postgres +
> > > > >
postgres=CTc/postgres
template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
=c/postgres +
> > > > >
postgres=CTc/postgres
(5 rows)

Foreman and candlepin users have access privileges, I’ve seen our data is
in the tables and there are even connections going on. All components have
started up successfully but we still can’t access the GUI or execute hammer
commands.

Could anybody please shed some light on this issue? Is there any
post-recover step that we may have missed?

Thanks!

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

Thanks! Not sure if I restarted them before or not to be honest, but it's
finally working :slight_smile:

··· El jueves, 20 de julio de 2017, 13:54:32 (UTC+2), ohad escribió: > > any chance you simply didnt restart your foreman services after the > db:migrate? > > On Thu, Jul 20, 2017 at 2:09 PM, María Sierra > wrote: > >> Attaching foreman-rake migrate:status output >> >> >> El jueves, 20 de julio de 2017, 13:06:54 (UTC+2), María Sierra escribió: >>> >>> Hello, >>> >>> Our foreman GUI is currently reporting >>> >>> ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending >>> in the system. >>> >>> And the same does hammer. foreman-rake migrate:status output seems to be >>> ok also (attached) >>> >>> This is a little context on how we reached the current status: >>> >>> After a problem with postgresql we had to recover foreman and candlepin >>> DBs from dump files. >>> >>> Our instance is Foreman 1.15 - Katello 3.4. Unfortunately, we didn't >>> know about katello-backup and katello-restore being introduced in version >>> 3.1, so we backed up the DBs like we used to in our old katello 2: >>> >>> pg_dump -Fc foreman > $BDIR/foreman.dump pg_dump -Fc candlepin > >>> $BDIR/candlepin.dump >>> >>> And we recovered them like this: >>> >>> dropdb foreman dropdb candlepin >>> pg_restore -C -d postgres $BDIR/foreman.dump pg_restore -C -d postgres >>> $BDIR/candlepin.dump >>> >>> >>> Now, Postgresql is up, the databases are there: >>> >>> List of databases >>> Name | Owner | Encoding | Collate | Ctype | Access >>> privileges >>> >>> -----------+----------+----------+-------------+-------------+------------------------ >>> candlepin | postgres | UTF8 | en_US.utf8 | en_US.utf8 | >>> =Tc/postgres + >>> > > > > > >>> postgres=CTc/postgres + >>> > > > > > >>> candlepin=CTc/postgres >>> foreman | foreman | UTF8 | en_US.utf8 | en_US.utf8 | >>> =Tc/foreman + >>> > > > > > >>> foreman=CTc/foreman + >>> > > > > > >>> postgres=CTc/foreman >>> postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >>> template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >>> =c/postgres + >>> > > > > > >>> postgres=CTc/postgres >>> template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >>> =c/postgres + >>> > > > > > >>> postgres=CTc/postgres >>> (5 rows) >>> >>> Foreman and candlepin users have access privileges, I've seen our data >>> is in the tables and there are even connections going on. All components >>> have started up successfully but we still can't access the GUI or execute >>> hammer commands. >>> >>> Could anybody please shed some light on this issue? Is there any >>> post-recover step that we may have missed? >>> >>> Thanks! >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >