The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #15820

Undefined method "empty_answer"

Added by Lee Lowder almost 2 years ago. Updated almost 2 years ago.

Status:ClosedStart date:08/03/2012
Priority:NormalDue date:
Assignee:Lee Lowder% Done:

0%

Category:-
Target version:-
Keywords: Affected Hiera-Puppet Version:
Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Using:

puppet* 3.0.0-0.1rc3puppetlabs1

hiera 1.0.0-0.1rc4

hiera-puppet 1.0.0-0.1rc1-1-g3e68ff0

When I run puppet agent --test I get the following:

Info: Retrieving plugin
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.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
Info: Loading facts in /etc/puppet/modules/custom/lib/facter/cluster_id.rb
Info: Loading facts in /etc/puppet/modules/custom/lib/facter/node_id.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/cluster_id.rb
Info: Loading facts in /var/lib/puppet/lib/facter/node_id.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error NoMethodError: undefined method `empty_answer' for Hiera::Backend:Module at /etc/puppet/environments/test/manifests/nodes/puppet_nodes.pp:47 on node ll-puppet-master-vm.XXXX
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

hiera.yaml:

# cat /etc/puppet/hiera.yaml
---
:hierarchy:
- %{node_id}
- common
:backends:
- yaml
- puppet
:yaml:
:datadir: '/etc/puppet/hieradata'

puppet.conf:

# cat /etc/puppet/puppet.conf
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
report=true
server=ll-puppet-master-vm.XXXX
certname=ll-puppet-master-vm.XXXX
pluginsync=true
archive_files = true
listen=true
[agent]
environment=test
[master]
facts_terminus = yaml
environment=test
manifest=/etc/puppet/environments/test/manifests/site.pp
modulepath=/etc/puppet/environments/test/modules:/etc/puppet/modules
ssl_client_header=SSL_CLIENT_S_DN
ssl_client_verify_header=SSL_CLIENT_VERIFY
storeconfig=true
dbadapter=mysql
dbuser = XXXXX
dbpassword = XXXXX
dbconnections = 75
reports = store

The section that is referenced in the error message:

class { 'basenode':
is_puppet_master => true;
}

And the class definition for basenode:

class basenode (
$is_puppet_master = false,
$apt_host = 'XXXXXXXXXXX'
) {
...
}

History

#1 Updated by Lee Lowder almost 2 years ago

Updating to hiera-puppet 1.0.0-0.1rc2 resolved this issue, but introduced different ones.

#2 Updated by Mitchell Hashimoto almost 2 years ago

To add to this. There is a bug in hiera-puppet 1.0.0-0.1rc1. RC2 fixes this, but for some reason, I think due to the structure of the version string, apt thinks 1.0.0-0.1rc1 is a LATER version than 1.0.0-0.1rc2. Easy enough, I can force the install of RC2.

After RC2 is installed, it is missing “hiera_puppet.rb,” so this actually needs to be retrieved from GitHub and put into the Ruby load path. This appears to be a packaging issue with hiera-puppet RC2.

Hopefully these are fixed up in RC3. :)

#3 Updated by eric sorenson almost 2 years ago

  • Assignee set to Lee Lowder

Mitch / Lee — Did 1.0.0rc4 in fact fix this? I’m just coming up to speed on this project so I’m not sure what the exact state of play is.

#4 Updated by Lee Lowder almost 2 years ago

I have not yet tested with rc3 or rc4, but I should be able to do so on Monday of next week.

I will give a proper update as soon as I am able to.

#5 Updated by eric sorenson almost 2 years ago

  • Status changed from Unreviewed to Needs More Information

#6 Updated by Curtis Ruck almost 2 years ago

I’m getting this issue in rc4.

#7 Updated by Bruno LEON almost 2 years ago

rc3 fixes the empty_answer issue. It needs to be forced at install though because apt installs the rc1

#8 Updated by Lee Lowder almost 2 years ago

  • Status changed from Needs More Information to Closed

Sorry for the delays in my response, life got busy.

This does seem to be fully fixed, I ran into it again, but that is because I forgot I needed to copy the files over still in 2.7.x and use pluginsync to get them into the right place. Closing this out.

Also available in: Atom PDF