Hi again,
I was just setting up my development instance of the latest foreman and I ran into trouble when following the instructions on: Installing latest code - Foreman.
When I ran "RAILS_ENV=production bundle exec rake db:migrate" with the db settings set to the pg database already populated by puppetmaster it gave me and error at:
== ChangeHostBuildDefaultToFalse: migrating ==================================
– change_column(:hosts, :build, :boolean, {:default=>false})
-> 0.0663s
rake aborted!
An error has occurred, this and all later migrations canceled:
This works fine when I do it to a separate empty database. The 0.42 branch worked fine last time I did this onto the storeconfigs database.
I reran it with --trace and attached output.
Cheers,
Lard
trace.txt (10.1 KB)
So apparently there is some conflict with active record in rails 3 and the puppet storeconfigs. The solution is to do the db::migrate before populating the database with the puppetmaster : ).
···
On 02/06/2012, at 10:59 PM, Lard Farnwell wrote:
Hi again,
I was just setting up my development instance of the latest foreman and I ran into trouble when following the instructions on: Installing latest code - Foreman.
When I ran “RAILS_ENV=production bundle exec rake db:migrate” with the db settings set to the pg database already populated by puppetmaster it gave me and error at:
== ChangeHostBuildDefaultToFalse: migrating ==================================
– change_column(:hosts, :build, :boolean, {:default=>false})
-> 0.0663s
rake aborted!
An error has occurred, this and all later migrations canceled:
This works fine when I do it to a separate empty database. The 0.42 branch worked fine last time I did this onto the storeconfigs database.
I reran it with --trace and attached output.
Cheers,
Lard
<trace.txt>
> So apparently there is some conflict with active record in rails 3 and the
> puppet storeconfigs. The solution is to do the db::migrate before
> populating the database with the puppetmaster : ).
>
> interesting… since PuppetDB is the new future for puppet, I would vote
not to share Foreman and Storeconfigs database.
additionally, as of recently, we also realized that we cant use the new
uuid's[1] with puppet storeconfigs while still giving the system a name.
Thanks!
Ohad
[1] UUID support for certnames - Foreman
···
On Wed, Jun 20, 2012 at 1:39 PM, Lard Farnwell wrote:
On 02/06/2012, at 10:59 PM, Lard Farnwell wrote:
Hi again,
I was just setting up my development instance of the latest foreman and
I ran into trouble when following the instructions on:
Installing latest code - Foreman.
When I ran “RAILS_ENV=production bundle exec rake db:migrate” with the
db settings set to the pg database already populated by puppetmaster it
gave me and error at:
== ChangeHostBuildDefaultToFalse: migrating
==================================
– change_column(:hosts, :build, :boolean, {:default=>false})
-> 0.0663s
rake aborted!
An error has occurred, this and all later migrations canceled:
This works fine when I do it to a separate empty database. The 0.42
branch worked fine last time I did this onto the storeconfigs database.
I reran it with --trace and attached output.
Cheers,
Lard
<trace.txt>
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
