Skip to content
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

Updating to 0.0.2 results in uninitilized constant #6

Closed
tombell opened this issue Feb 24, 2014 · 4 comments
Closed

Updating to 0.0.2 results in uninitilized constant #6

tombell opened this issue Feb 24, 2014 · 4 comments

Comments

@tombell
Copy link

@tombell tombell commented Feb 24, 2014

So I updated the module to 0.0.2 from 0.0.1 and seem to be getting the following error when running boxen

~ > boxen
Boxen is up-to-date.
Error: uninitialized constant Puppet::DataBinding::LookupError at /opt/boxen/repo/manifests/site.pp:1 on node winterfell.local
Wrapped exception:
uninitialized constant Puppet::DataBinding::LookupError
Error: uninitialized constant Puppet::DataBinding::LookupError at /opt/boxen/repo/manifests/site.pp:1 on node winterfell.local

Reverting back to 0.0.1 seems to fix the error, have I missed something when updating to 0.0.2?

@skibum55
Copy link

@skibum55 skibum55 commented Feb 28, 2014

I'm getting something similar
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::Compiler failed with error NameError: uninitialized constant Puppet::DataBinding::LookupError on node rhel64-ruzp6mfh
puppet --version =3.3.3 (Puppet Enterprise 3.1.1)
Have not tried 0.0.1

@911akash
Copy link

@911akash 911akash commented Sep 22, 2014

any luck skibum55 ??? am getting exact error as yours

@tombell tombell closed this Sep 22, 2014
@doismellburning
Copy link

@doismellburning doismellburning commented Sep 28, 2014

@tombell I notice you closed this, any chance of some context as to why / pointers for anyone else ending up with the same issue? Thanks

@tombell
Copy link
Author

@tombell tombell commented Sep 28, 2014

I was using this with boxen, and the issue went away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.