Upgrading Foreman: Should `foreman-rake db:migrate` produce no output?

Support
1

I have a question about upgrading Foreman.

The Foreman Manual, under Step 3 (A) - Database migration and cleanup
<http://theforeman.org/manuals/1.11/index.html#step-3-a---database-migration-and-cleanup> says
the following:

The database should be migrated already, but you can make sure by executing
the migration script again, it should produce no errors or output:

foreman-rake db:migrate

foreman-rake db:seed

Is this really true? In my experience, foreman-rake db:migrate almost
always produces output. We've been running The Foreman from 1.3, and I've
updated to every point release. I'm updating to 1.10 right now. The rake
command doesn't necessarily produce any errors, but it usually prints other
information.

After some discussion on #theforeman , I believe that many others also see
output after this command.

Is this true for others? Should foreman-rake db:migrate be completely
silent every time?

-= Stefan

2

Though there are always database migrations on major version updates,
the implication is that the package update should already have run the
db:migrate in their postinst scripts.

There shouldn't be any migrations to run after the packages have updated
unless they failed for some reason. The idea of listing the commands to
run here is to detect when migrations failed.

··· On 28/04/16 21:53, Stefan Lasiewski wrote: > > I have a question about upgrading Foreman. > > The Foreman Manual, under Step 3 (A) - Database migration and cleanup > says > the following: > > The database should be migrated already, but you can make sure by > executing the migration script again, it should produce no errors or > output: > > >foreman-rake db:migrate| > > >foreman-rake db:seed| > > > > Is this really true? In my experience, `foreman-rake db:migrate` almost > always produces output. We've been running The Foreman from 1.3, and > I've updated to every point release. I'm updating to 1.10 right now. > The rake command doesn't necessarily produce any errors, but it usually > prints other information. > > After some discussion on #theforeman , I believe that many others also > see output after this command. > > Is this true for others? Should `foreman-rake db:migrate` be completely > silent every time?

–
Dominic Cleal
dominic@cleal.org