[Staypuft] Puppet Fail on CentOS

I managed to install foreman and Staypuft, albeit a couple of additional
not documented configurations. Now the problem arises when a new host is
provisioned and is getting its configuration via puppet. Here is the output:

[root@mac00505683aaaa ~]# puppet agent --test
Notice: Using less secure serialization of reports and query parameters for
compatibility
Notice: with older puppet master. To remove this notice, please upgrade
your master(s)
Notice: to Puppet 3.3 or newer.
Notice: See http://links.puppetlabs.com/deprecate_yaml_on_network for more
information.
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional
resources using 'eval_generate': Error 400 on SERVER: Not authorized to
call search on /file_metadata/pluginfacts with {:ignore=>[".svn", "CVS",
".git"], :recurse=>true, :links=>"manage", :checksum_type=>"md5"}
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not
retrieve file metadata for puppet://foreman.hq.ltg/pluginfacts: Error 400
on SERVER: Not authorized to call find on /file_metadata/pluginfacts with {:
source_permissions=>"use", :links=>"manage"}
Wrapped exception:
Error 400 on SERVER: Not authorized to call find on /file_metadata/pluginfacts
with {:source_permissions=>"use", :links=>"manage"}
Info: Retrieving plugin
Info: Loading facts in /var/lib/puppet/lib/facter/staging_http_get.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/hamysql_active_node.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardirtmp.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_host.rb
Info: Loading facts in /var/lib/puppet/lib/facter/hamysql_is_running.rb
Info: Loading facts in /var/lib/puppet/lib/facter/staging_windir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/openstack_services_enabled
.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_property.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ipa_client_configured.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_bug.rb
Info: Loading facts in /var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_fsuuid.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_vrrp.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_fsm.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_ports.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_uuid.rb
Info: Loading facts in /var/lib/puppet/lib/facter/
iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/gluster_bricks.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Invalid parameter config_hash at /etc/puppet/environments/production/modules
/quickstack/manifests/db/mysql.pp:113 on node mac00505683aaaa.hq.ltg
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

The last error seems to be an issue with the versioning of the mysql
database based on some google searches. (I have mysql++.x86_64 version
3.1.0-12.el7 from epel). What version are you using in RHEL?

Thanks,
IB

To add to the post, for the error where it references the config_hash,

Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Invalid parameter config_hash at /etc/puppet/environments/production/modules
/quickstack/manifests/db/mysql.pp:113 on node mac00505683aaaa.hq.ltg

by looking at the YAML file, there is no config_hash, but rather a
mysql_user, mysql_password, etc.

IB

··· On Wednesday, September 10, 2014 10:10:12 PM UTC-4, Ignacio Bravo wrote: > > I managed to install foreman and Staypuft, albeit a couple of additional > not documented configurations. Now the problem arises when a new host is > provisioned and is getting its configuration via puppet. Here is the output: > > [root@mac00505683aaaa ~]# puppet agent --test > Notice: Using less secure serialization of reports and query parameters > for compatibility > Notice: with older puppet master. To remove this notice, please upgrade > your master(s) > Notice: to Puppet 3.3 or newer. > Notice: See http://links.puppetlabs.com/deprecate_yaml_on_network for > more information. > Info: Retrieving pluginfacts > Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional > resources using 'eval_generate': Error 400 on SERVER: Not authorized to > call search on /file_metadata/pluginfacts with {:ignore=>[".svn", "CVS", > ".git"], :recurse=>true, :links=>"manage", :checksum_type=>"md5"} > Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not > retrieve file metadata for puppet://foreman.hq.ltg/pluginfacts: Error 400 > on SERVER: Not authorized to call find on /file_metadata/pluginfacts with > {:source_permissions=>"use", :links=>"manage"} > Wrapped exception: > Error 400 on SERVER: Not authorized to call find on /file_metadata/pluginfacts > with {:source_permissions=>"use", :links=>"manage"} > Info: Retrieving plugin > Info: Loading facts in /var/lib/puppet/lib/facter/staging_http_get.rb > Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/hamysql_active_node.rb > Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardirtmp.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_host.rb > Info: Loading facts in /var/lib/puppet/lib/facter/hamysql_is_running.rb > Info: Loading facts in /var/lib/puppet/lib/facter/staging_windir.rb > Info: Loading facts in /var/lib/puppet/lib/facter/ > openstack_services_enabled.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_property.rb > Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb > Info: Loading facts in /var/lib/puppet/lib/facter/ipa_client_configured.rb > Info: Loading facts in /var/lib/puppet/lib/facter/puppet_bug.rb > Info: Loading facts in /var/lib/puppet/lib/facter/rabbitmq_erlang_cookie. > rb > Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_fsuuid.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_vrrp.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_fsm.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_ports.rb > Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb > Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_uuid.rb > Info: Loading facts in /var/lib/puppet/lib/facter/ > iptables_persistent_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_version.rb > Info: Loading facts in /var/lib/puppet/lib/facter/gluster_bricks.rb > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Invalid parameter config_hash at /etc/puppet/environments/production/ > modules/quickstack/manifests/db/mysql.pp:113 on node mac00505683aaaa.hq. > ltg > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > > > > The last error seems to be an issue with the versioning of the mysql > database based on some google searches. (I have mysql++.x86_64 version > 3.1.0-12.el7 from epel). What version are you using in RHEL? > > > Thanks, > IB > > >

And the last tip. Look here for another clue:

··· On Thursday, September 11, 2014 9:07:03 AM UTC-4, Ignacio Bravo wrote: > > To add to the post, for the error where it references the config_hash, > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Invalid parameter config_hash at /etc/puppet/environments/production/ > modules/quickstack/manifests/db/mysql.pp:113 on node mac00505683aaaa.hq. > ltg > > by looking at the YAML file, there is no config_hash, but rather a > mysql_user, mysql_password, etc. > > IB > >

The serverfault answer seems to be a good direction. Can you check the mysql
module version? Module should be at
/etc/puppet/environments/production/modules/mysql/

If the version is different from 0.9.0, could you manually try to install this
specific version from puppet forge [1]?

[1] https://forge.puppetlabs.com/puppetlabs/mysql/0.9.0

··· On Thursday 11 of September 2014 06:11:57 Ignacio Bravo wrote: > And the last tip. Look here for another clue: > > http://serverfault.com/questions/589294/invalid-parameter-config-hash-attemp > ting-to-install-mysql-and-openstack-via-p > On Thursday, September 11, 2014 9:07:03 AM UTC-4, Ignacio Bravo wrote: > > To add to the post, for the error where it references the config_hash, > > > > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > > Invalid parameter config_hash at /etc/puppet/environments/production/ > > modules/quickstack/manifests/db/mysql.pp:113 on node mac00505683aaaa.hq. > > ltg > > > > by looking at the YAML file, there is no config_hash, but rather a > > mysql_user, mysql_password, etc. > > > > IB


Marek

It didn't like it. Same results.

The version installed was 2.3.1 so I replaced with 0.9.0 and imported the
puppet classes again into foreman.
The run provided the same errors.

IB

··· On Friday, September 12, 2014 4:54:33 AM UTC-4, Marek Hulan wrote: > > On Thursday 11 of September 2014 06:11:57 Ignacio Bravo wrote: > > And the last tip. Look here for another clue: > > > > > http://serverfault.com/questions/589294/invalid-parameter-config-hash-attemp > > ting-to-install-mysql-and-openstack-via-p > > On Thursday, September 11, 2014 9:07:03 AM UTC-4, Ignacio Bravo wrote: > > > To add to the post, for the error where it references the config_hash, > > > > > > Error: Could not retrieve catalog from remote server: Error 400 on > SERVER: > > > Invalid parameter config_hash at /etc/puppet/environments/production/ > > > modules/quickstack/manifests/db/mysql.pp:113 on node > mac00505683aaaa.hq. > > > ltg > > > > > > by looking at the YAML file, there is no config_hash, but rather a > > > mysql_user, mysql_password, etc. > > > > > > IB > > The serverfault answer seems to be a good direction. Can you check the > mysql > module version? Module should be at > /etc/puppet/environments/production/modules/mysql/ > > If the version is different from 0.9.0, could you manually try to install > this > specific version from puppet forge [1]? > > [1] https://forge.puppetlabs.com/puppetlabs/mysql/0.9.0 > > -- > Marek >

Hm, I'm out of ideas. Maybe you could create issue on github [1] or preferably
in bugzilla. If you do so, please send a link to ticket so we can track it.

[1] https://github.com/redhat-openstack/openstack-puppet-modules

··· -- Marek

On Friday 12 of September 2014 06:06:48 Ignacio Bravo wrote:

It didn’t like it. Same results.

The version installed was 2.3.1 so I replaced with 0.9.0 and imported the
puppet classes again into foreman.
The run provided the same errors.

IB

On Friday, September 12, 2014 4:54:33 AM UTC-4, Marek Hulan wrote:

On Thursday 11 of September 2014 06:11:57 Ignacio Bravo wrote:

And the last tip. Look here for another clue:
http://serverfault.com/questions/589294/invalid-parameter-config-hash-atte

ting-to-install-mysql-and-openstack-via-p

On Thursday, September 11, 2014 9:07:03 AM UTC-4, Ignacio Bravo wrote:

To add to the post, for the error where it references the config_hash,

Error: Could not retrieve catalog from remote server: Error 400 on

SERVER:

Invalid parameter config_hash at /etc/puppet/environments/production/
modules/quickstack/manifests/db/mysql.pp:113 on node

mac00505683aaaa.hq.

ltg

by looking at the YAML file, there is no config_hash, but rather a
mysql_user, mysql_password, etc.

IB

The serverfault answer seems to be a good direction. Can you check the
mysql
module version? Module should be at
/etc/puppet/environments/production/modules/mysql/

If the version is different from 0.9.0, could you manually try to install
this
specific version from puppet forge [1]?

[1] https://forge.puppetlabs.com/puppetlabs/mysql/0.9.0


Marek