Updating to 0.0.2 results in uninitilized constant #6

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

Comments

Projects
None yet
4 participants
@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

This comment has been minimized.

Show comment
Hide comment
@skibum55

skibum55 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

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

This comment has been minimized.

Show comment
Hide comment
@911akash

911akash Sep 22, 2014

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

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

@tombell tombell closed this Sep 22, 2014

@doismellburning

This comment has been minimized.

Show comment
Hide comment
@doismellburning

doismellburning 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 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

This comment has been minimized.

Show comment
Hide comment
@tombell

tombell Sep 28, 2014

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

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