freifunk-berlin / puppet

Deprecated: New infrastructure development is happening in https://github.com/freifunk-berlin/ansible
Other
2 stars 4 forks source link

puppet apply fails on monitor.berlin.freifunk.net #64

Closed egmont1227 closed 4 years ago

egmont1227 commented 5 years ago
root@monitor:~/berlin-puppet/puppet# puppet apply --noop --verbose --modulepath=/root/berlin-puppet/puppet/modules manifests/site.pp 
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class php-fpm at /root/berlin-puppet/puppet/manifests/site.pp:127 on node monitor.berlin.freifunk.net
Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class php-fpm at /root/berlin-puppet/puppet/manifests/site.pp:127 on node monitor.berlin.freifunk.net

looks like some problem with php-fpm module of @booo , although puppet module list seems to be fine

root@monitor:~/berlin-puppet/puppet# puppet module list --modulepath=/root/berlin-puppet/puppet/modules 
Warning: Missing dependency 'puppetlabs-stdlib':
  'ulhpc-exim4' (v0.1.2) requires 'puppetlabs-stdlib' (>=4.2.2 <5.0.0)
  'engage-uwsgi' (v1.3.0) requires 'puppetlabs-stdlib' (>=3.2.0)
/root/berlin-puppet/puppet/modules
├── bbbdigger (???)
├── communitytunnel (???)
├── engage-uwsgi (v1.3.0)
├── files (???)
├── fpm (???)
├── jfryman-nginx (v0.2.7)
├── puppet-collectd (v4.2.0)
├── puppet-unattended_upgrades (v1.0.3)
├── puppetlabs-apt (v2.2.0)
├── puppetlabs-concat (v1.2.4)
├── puppetlabs-ntp (v4.1.0)
├── puppetlabs-postgresql (v4.6.0)
├── puppetlabs-stdlib (v4.9.0)
├── puppetlabs-vcsrepo (v1.3.1)
├── rrdcached (???)
├── stahnma-epel (v1.1.1)
├── stankevich-python (v1.9.8)
├── thias-sysctl (v1.0.2)
├── tunneldigger (???)
├── ulhpc-exim4 (v0.1.2)
└── vpn03 (???)
pmelange commented 5 years ago

https://github.com/booo/puppet-php-fpm/commit/0fa7b28d9c0a97fda4b0ec39249c3e7eb076040a should be used instead

pmelange commented 4 years ago

I believe @rtznprmpftl has fixed this issue. But I am not going to close it yet before getting confirmation.

nicolasberens commented 4 years ago

on the new node it works, so i will close this issue