Puppet users - Aug 2007 - update from 0.22.4 to 0.23.x, not migrating database schema

Hello everybody,
I have updated the puppetmaster from 0.22.4 to 0.23.0 (and today to 
0.23.2). Although ''dbmigrate=true'' is turned on AND the
puppetmaster is
saying it migrates the databse at startup, this does not happen.

When it should store configs, I get the error:

  Could not store configs: Mysql::Error: #42S02Table 
''database.resource_tags'' doesn''t exist: SELECT * FROM
resource_tags
WHERE (resource_tags.resource_id

I had the error after updating from 0.22.4 to 0.23.0, I created the one 
or the other column by hand, as it seems not all of them.

Would be nice if this would be done by puppet itself.
Thanks,
udo.

On Aug 13, 2007, at 10:18 AM, Udo Waechter wrote:
> Hello everybody,
> I have updated the puppetmaster from 0.22.4 to 0.23.0 (and today to
> 0.23.2). Although ''dbmigrate=true'' is turned on AND the  
> puppetmaster is
> saying it migrates the databse at startup, this does not happen.
>
> When it should store configs, I get the error:
>
>   Could not store configs: Mysql::Error: #42S02Table
> ''database.resource_tags'' doesn''t exist: SELECT *
FROM resource_tags
> WHERE (resource_tags.resource_id
>
> I had the error after updating from 0.22.4 to 0.23.0, I created the  
> one
> or the other column by hand, as it seems not all of them.
Sorry; I started the db schema from scratch, rather than using  
migrations to make the changes.

Basically, you should have just removed your old db and used -- 
dbmigrate to create the new one.

  --
  The covers of this book are too far apart.      -- Ambrose Bierce
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com