installation failure about puppet-gitlab

[spuder]

There may be a bug in the nginx template. I'll spin up a vagrant vm and test it again.

If you add --debug to the output, does it show you the line number that it is failing on?

[moozer]

vagrant is on my todo list :-)

In the initial post I have made a 6.6 vs 6.7 copy'n' paste error. I am using 6-7 now.

With --debug:

puppet apply --verbose /etc/puppet/manifests/sites.pp --debug
info: Loading facts in /etc/puppet/modules/ruby/lib/facter/gemhome.rb
info: Loading facts in /etc/puppet/modules/puppi/lib/facter/last_run.rb
info: Loading facts in /etc/puppet/modules/puppi/lib/facter/puppi_projects.rb
info: Loading facts in /etc/puppet/modules/puppi/lib/facter/windows_common_appdata.rb
info: Loading facts in /etc/puppet/modules/concat/lib/facter/concat_basedir.rb
info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
debug: importing '/etc/puppet/modules/mysql/manifests/init.pp' in environment production
debug: importing '/etc/puppet/modules/mysql/manifests/server.pp' in environment production
debug: Automatically imported mysql::server from mysql/server into production
debug: importing '/etc/puppet/modules/mysql/manifests/params.pp' in environment production
debug: Automatically imported mysql::params from mysql/params into production
debug: importing '/etc/puppet/modules/mysql/manifests/server/root_password.pp' in environment production
debug: Automatically imported mysql::server::root_password from mysql/server/root_password into production
debug: importing '/etc/puppet/modules/mysql/manifests/db.pp' in environment production
debug: Automatically imported mysql::db from mysql/db into production
debug: importing '/etc/puppet/modules/mysql/manifests/server/install.pp' in environment production
debug: Automatically imported mysql::server::install from mysql/server/install into production
debug: importing '/etc/puppet/modules/mysql/manifests/server/config.pp' in environment production
debug: Automatically imported mysql::server::config from mysql/server/config into production
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Scope(Class[Mysql::Server::Config]): Retrieving template mysql/my.cnf.erb
debug: template[/etc/puppet/modules/mysql/templates/my.cnf.erb]: Bound template variables for /etc/puppet/modules/mysql/templates/my.cnf.erb in 0.00 seconds
debug: template[/etc/puppet/modules/mysql/templates/my.cnf.erb]: Interpolated template /etc/puppet/modules/mysql/templates/my.cnf.erb in 0.00 seconds
debug: importing '/etc/puppet/modules/mysql/manifests/server/service.pp' in environment production
debug: Automatically imported mysql::server::service from mysql/server/service into production
debug: Scope(Class[Mysql::Server::Root_password]): Retrieving template mysql/my.cnf.pass.erb
debug: template[/etc/puppet/modules/mysql/templates/my.cnf.pass.erb]: Bound template variables for /etc/puppet/modules/mysql/templates/my.cnf.pass.erb in 0.00 seconds
debug: template[/etc/puppet/modules/mysql/templates/my.cnf.pass.erb]: Interpolated template /etc/puppet/modules/mysql/templates/my.cnf.pass.erb in 0.01 seconds
debug: importing '/etc/puppet/modules/mysql/manifests/server/providers.pp' in environment production
debug: Automatically imported mysql::server::providers from mysql/server/providers into production
debug: importing '/etc/puppet/modules/gitlab/manifests/init.pp' in environment production
debug: Automatically imported gitlab from gitlab into production
debug: importing '/etc/puppet/modules/gitlab/manifests/params.pp' in environment production
debug: Automatically imported gitlab::params from gitlab/params into production
debug: Scope(Class[Gitlab]): A debian os was detected: Debian
debug: importing '/etc/puppet/modules/gitlab/manifests/packages.pp' in environment production
debug: Automatically imported gitlab::packages from gitlab/packages into production
debug: importing '/etc/puppet/modules/apt/manifests/init.pp' in environment production
debug: Automatically imported apt from apt into production
debug: importing '/etc/puppet/modules/apt/manifests/params.pp' in environment production
debug: Automatically imported apt::params from apt/params into production
debug: importing '/etc/puppet/modules/apt/manifests/update.pp' in environment production
debug: Automatically imported apt::update from apt/update into production
debug: Resource package[libicu-dev] was not determined to be defined
debug: Resource package[python2.7] was not determined to be defined
debug: Resource package[python-docutils] was not determined to be defined
debug: Resource package[libxml2-dev] was not determined to be defined
debug: Resource package[libxslt1-dev] was not determined to be defined
debug: Resource package[python-dev] was not determined to be defined
debug: Resource package[build-essential] was not determined to be defined
debug: Resource package[libmysqlclient-dev] was not determined to be defined
debug: Resource package[redis-server] was not determined to be defined
debug: Resource package[logrotate] was not determined to be defined
debug: importing '/etc/puppet/modules/apt/manifests/ppa.pp' in environment production
debug: Automatically imported apt::ppa from apt/ppa into production
debug: importing '/etc/puppet/modules/apt/manifests/key.pp' in environment production
debug: Automatically imported apt::key from apt/key into production
debug: importing '/etc/puppet/modules/ruby/manifests/init.pp' in environment production
debug: Automatically imported ruby from ruby into production
debug: importing '/etc/puppet/modules/ruby/manifests/params.pp' in environment production
debug: Automatically imported ruby::params from ruby/params into production
debug: importing '/etc/puppet/modules/postfix/manifests/init.pp' in environment production
debug: Automatically imported postfix from postfix into production
debug: importing '/etc/puppet/modules/postfix/manifests/params.pp' in environment production
debug: Automatically imported postfix::params from postfix/params into production
debug: importing '/etc/puppet/modules/gitlab/manifests/user.pp' in environment production
debug: Automatically imported gitlab::user from gitlab/user into production
debug: importing '/etc/puppet/modules/gitlab/manifests/setup.pp' in environment production
debug: Automatically imported gitlab::setup from gitlab/setup into production
debug: Scope(Class[Gitlab::Setup]): Retrieving template gitlab/gitlab-shell.erb
debug: template[/etc/puppet/modules/gitlab/templates/gitlab-shell.erb]: Bound template variables for /etc/puppet/modules/gitlab/templates/gitlab-shell.erb in 0.00 seconds
debug: template[/etc/puppet/modules/gitlab/templates/gitlab-shell.erb]: Interpolated template /etc/puppet/modules/gitlab/templates/gitlab-shell.erb in 0.00 seconds
debug: Scope(Class[Gitlab::Setup]): Retrieving template gitlab/gitlab.yml.6-7-stable.erb
debug: template[/etc/puppet/modules/gitlab/templates/gitlab.yml.6-7-stable.erb]: Bound template variables for /etc/puppet/modules/gitlab/templates/gitlab.yml.6-7-stable.erb in 0.00 seconds
Failed to parse template gitlab/gitlab.yml.6-7-stable.erb:
Filepath: /usr/lib/ruby/vendor_ruby/puppet/parser/scope.rb
Line: 459
Detail: undefined method `[]' for #Puppet::Parser::Scope:0x7ff902b858a0
at /etc/puppet/modules/gitlab/manifests/setup.pp:62 on node gitlab05.xx.xx

[spuder]

6-7 works on my vagrant box. I suspect it has something to do with the version of ruby installed.

Recently the erb templates switched to the following syntax.

<% if scope['gitlab::use_custom_login_logo'] == true ....

The output appears to indicate that it is choking on the scope definition.

What version of ruby are you running?
What version of puppet are you running?

[spuder]

I'm fairly positive this is caused by having a version of puppet < 3.x

According to the docs, puppet 3.x introduced the scope[::foo] syntax

http://docs.puppetlabs.com/guides/templating.html#erb-template-syntax

[moozer]

I have updated puppet to the packages from debian/jessie.
Now I get this error

...
Debug: Automatically imported gitlab::service from gitlab/service into production
Debug: Scope(Class[Gitlab::Service]): Retrieving template gitlab/init.6-7-stable.erb
Debug: template[/etc/puppet/modules/gitlab/templates/init.6-7-stable.erb]: Bound template variables for /etc/puppet/modules/gitlab/templates/init.6-7-stable.erb in 0.00 seconds
Debug: template[/etc/puppet/modules/gitlab/templates/init.6-7-stable.erb]: Interpolated template /etc/puppet/modules/gitlab/templates/init.6-7-stable.erb in 0.00 seconds
Error: apt::ppa is currently supported on Ubuntu only. at /etc/puppet/modules/apt/manifests/ppa.pp:18 on node gitlab04.xx.xx
Error: apt::ppa is currently supported on Ubuntu only. at /etc/puppet/modules/apt/manifests/ppa.pp:18 on node gitlab04.xx.xx

The way I read it, we have a debian/ubuntu incompatability. Are you using ubuntu or debian in your vagrant box?

# puppet version
Puppet v3.4.3

# ruby --version
ruby 2.0.0p457 (2014-03-03) [x86_64-linux-gnu]

[moozer]

some notes on ppa's

I went here to see where they were used
https://github.com/spuder/puppet-gitlab/search?q=ppa&ref=cmdform

You have a comment about the git-core from standard repos being a too old version. Standard debian repo now uses version 1.7.10, and testing/jessie is using version 1.9.1. So I suppose that the standard packages could be used instead of the ppa

I will fork, and attempt a pull request :-)

[moozer]

I have made a pull request. see #56

[moozer]

I have found time to work with this again. Now with the change you introduced in response to my pull request. It is a simple solution to avoid the ppa problem when using debian as opposed to ubuntu.

The check for version is done on the client side version of puppet, and the scope problem that I mentioned in the initial post is related to the puppet version on the master. The conclusion is that the master must run debian/jessie (aka. testing).

I have looked a bit, but cannot find a fact/variable/whatever that says anything about the server version. And since the recommendations are that the version on the server is the same or newer than the one on the client - the version check already in place should be sufficient.