Just after interesting findings in my previous blog posts about WineHQ (https://linardsliepins.wordpress.com/2015/05/20/a-little-yet-ichy-mess-about-fedora-nad-winehq-cooperation-to-deliver-latest-updates-to-nix-users/) and AMD Catalyst (https://linardsliepins.wordpress.com/2015/06/03/amd-catalyst-15-5-beta-for-linux-but-is-it-for-kernel-4-x/), the new happy happy stuff reviles…
As title says, it is about DevOps – Automation Tools ( for Enterpisrses ) – Puppet in the focus here.
First, the fact, that it got 3.7.x version, is pretty strange for so DevOps oriented companies product.
Secondly, Puppets online documentation do not clearly mention where to use sudo and where not to use sudo for privileges.
Thirdly, Node Definitions in SITE.PP ( AS PUPPET DOCS SUGGESTS ), simply do not work for puppet apply command. With sample from docs I got syntax error of ‘}’. WHAT THE FUCK???!!!
Fourthly, This release still use chkconfig utility. Source and Fix: https://projects.puppetlabs.com/issues/17593
Fifthly, puppet installation do not handle and docs do not mention some interesting this like ports and firewalls. So, had again google to find out that I had to do this ( Quote from blog below ):
Needless to say that step one would always be to ensure that the names are resolving and the puppet client and master can communicate. Also make sure that port 8140 is white listed.
.. using this ( not firewall-cmd or anything else ) …
Sixty, interesting spamming in console, very similar to this bug: http://permalink.gmane.org/gmane.linux.suse.opensuse.ruby/691
That’s it for now… :)
P.S. Thanks for info from this blog: http://blog.adityapatawari.com/2012/02/puppet-and-common-errors.html – it helped to solve some issues.
Minute after updating this blog, I decided to reboot my virtual fedora 22 server installation after update deployment. Well, once I put dnf upgrade, I had surprise – fedora had been pushing puppet-4.1 as updates and it just rolled out. Well. Rebooted. And again tried to install this rtyler-jenkins module… and it succeeded. We’ll see if I can start jenkins service…