Foreman

To reproduce:

1. Configure puppet to use storeconfigs.
2. Start puppetmasterd and have it create / populate the tables in the database.
3. Try to run 'rake db:migrate RAILS_ENV=production'

(should have added this when creating the bug report)

Matt Delves wrote:

If you run the command 'rake db:migrate RAILS_ENV=production' having configured the foreman database to be the same as the puppet database, it will error and not create the audits table.

Workaround: 1. Recreate the puppet database, though don't start puppetmasterd 2. run 'rake db:migrate RAILS_ENV=production' 3. start puppetmasterd.

can you provide the error that you've got?

Thanks

The error I get is:

Mysql::Error: Table 'puppet.audits' doesn't exist: SHOW FIELDS FROM `audits`

Matt Delves wrote:

The error I get is:

ChangeHostBuildDefaultToFale: migrating ========== -- change_column(:hosts, :build, :boolean, {:default=>false}) -> 0.0166s rake aborted! An error has occurred, all later migrations canceled:

Mysql::Error: Table 'puppet.audits' doesn't exist: SHOW FIELDS FROM `audits`

does commenting line 16 in app/models/host.rb solves the problem?
(acts_as_audited...)
if it does, let me know and I'll submit the patch.

Thanks

Ohad Levy wrote:

Matt Delves wrote:

The error I get is:

ChangeHostBuildDefaultToFale: migrating ========== -- change_column(:hosts, :build, :boolean, {:default=>false}) -> 0.0166s rake aborted! An error has occurred, all later migrations canceled:

Mysql::Error: Table 'puppet.audits' doesn't exist: SHOW FIELDS FROM `audits`

does commenting line 16 in app/models/host.rb solves the problem? (acts_as_audited...) if it does, let me know and I'll submit the patch.

Thanks

if it does work, please run rake db:migrate --trace RAILS_ENV=production and submit the error - thanks

commenting out the acts_as_audited line does fix the problem.

when initializing a new migration, Plugin db table has not been assigned yet, therefor it should be excluded in rake tasks or reordered.

I cant reproduce it.. what I've done:

enabled storeconfigs on a puppetmaster
run one host against it so it generated the storeconfigs database.

then I've configured config/database to point to the same database and I've run rake db:migrate.

everything seems to be working correctly.

could you reproduce your error? please provide the output with --trace

thanks

Attached is the output I ran from 'rake db:migrate RAILS_ENV=production'.

Thanks,
Matt

I'll try again with MySQL, I've only tried sqlite database.

ok, I can confirm this happens on MySQL.. I'll bump it to the current release

Applied in changeset 38a51fc29825625e09ebb9ed4bdb84afcdfe65da.