-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stack level too deep #40
Comments
A little more info would be appreciated .. |
the puppet version is puppet-3.7.3, ruby-1.8.7 this is my nodes.pp this is the output on the puppet agent: for the code, i'm using the last version of the XLDeploy module version 1.1.2 |
do me a favour .. do a run with --trace and post the output here ? |
with the --trace |
thnx, i think i've spotted the problem .. |
closed it by accident .. sorry about that |
please try adding seperate ci's for the directory structure.. that should fix the problem for now . |
is it this kind of struture you suggest ? xldeploy_ci{ 'Infrastructure/projectx': xldeploy_ci{ "Infrastructure/projectx/${hostname}_sshHost": |
just hold on .. i'm investigating this .. |
so far i have been unable to recreate the issue using ruby 1.9.3 . |
Hi, [root@nlbdeployx1 ~]# puppet agent -t --trace --debug |
hmm .. i wonder why it's still saying site_ruby/1.8 all throughout the logs... |
Hi, |
try http://rvm.io |
I used the rvm so now i have this: |
Hi, |
Hi, yum remove -y ruby facter puppet still have the same issue but no more using lib 1.8.7. You have new mail in /var/spool/mail/root |
Stack level too deep usually means recursion, and it shows in the output. It's flipping between persist and ensure_parent_directory. The problem is that the persist method calls ensure_parent_directory, and if the parent does not exist it calls persist to make sure it exists.. @WianVos Can you check your local code to see what you have if you cannot reproduce this: https://github.com/xebialabs/puppet-xldeploy/blob/master/lib/puppet_x/xebialabs/xldeploy/ci.rb#L61 |
my code is the last version |
I've found the problem . It was in the default behaviour of the ruby pathname module . Sorry for putting you through the whole debugging process. Regards |
Hi,
since the last update, i have this issue:
Error: Could not set 'present' on ensure: stack level too deep at 45:/etc/puppet/environments/production/modules/xldeploy/manifests/client/config_ci.pp
The text was updated successfully, but these errors were encountered: