Created attachment 949508 [details] install and config logs Description of problem: [0;36mDebug: template[/var/tmp/packstack/1c5a526470b94178bf5a33ae0fd956e8/modules/mysql/templates/my.cnf.pass.erb]: Interpolated template /var/tmp/packstack/1c5a526470b94178bf5a33ae0fd956e8/modules/mysql/templates/my.cnf.pass.erb in 0.00 seconds[0m [0;36mDebug: importing '/var/tmp/packstack/1c5a526470b94178bf5a33ae0fd956e8/modules/mysql/manifests/server/providers.pp' in environment production[0m [0;36mDebug: Automatically imported mysql::server::providers from mysql/server/providers into production[0m [1;31mError: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type database_user at /var/tmp/packstack/1c5a526470b94178bf5a33ae0fd956e8/manifests/172.16.32.71_mariadb.pp:28 on node packstack.example.com Wrapped exception: Invalid resource type database_user[0m [1;31mError: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type database_user at /var/tmp/packstack/1c5a526470b94178bf5a33ae0fd956e8/manifests/172.16.32.71_mariadb.pp:28 on node packstack.example.com[0m see logs for install config and logs
openstack-puppet-modules-2014.2-dev.07546a684521743b5b3535f4445d55b6770b502d.fc20.noarch
This will never work correctly please don't use openstack puppet modules master but use o-p-m master.
I'm not sure We'll get away with using o-p-m master, what will happen when something is merged into an openstack project that requires a change to the puppet modules? In order to be able to use master packages for CI we need a deployment tool that is also developing against master if master or o-p-m and packstack are still being developed using RPM's built from a stable branch then it wont take long before it will become unusable for master based CI. Ideally we could get to a point where packstack branches at the same time as the openstack projects and packstack master could continue tracking master of the puppet modules and openstack components.
Note that ATM stable/juno has not be created in any puppet-* module repository, so I assume there hasn't been any Kilo work on puppet modules yet. I'm guessing only deployment tool closely tracking openstack master would be tripleo?
Yup, from a master tracking point of view tripleo would be suitable, although CI for tripleo is not trivial. It looks like the juno branches for the puppet modules wont be cut for a week if not longer. So basically we're stuck for the moment until packstack cuts a juno branch and starts development for master.
If It could help, we have now a packstack juno branch ! https://github.com/stackforge/packstack/tree/juno
This bug is against a version which has reached End of Life. Please reopen if it is still relevant with a latest version: http://releases.openstack.org/