Could not find scope for mongodb::params

[pschichtel]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 4.10.1
• Ruby: 2.1.9p490 (puppet bundled)
• Distribution: Debian Jessie 8.10
• Module version: 1.1.0

How to reproduce (e.g Puppet code you use)

enable manage_package_repo in globals.pp

What are you seeing

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not find scope for mongodb::params at /etc/puppetlabs/code/environments/production/modules/mongodb/manifests/globals.pp:47:5 on node host

What behaviour did you expect instead

I expected the apt source list to be created by puppet.

Output log

see above

Any additional information you'd like to impart

n/a

[alexjfisher]

@pschichtel Thanks for reporting this. Could you share a complete example of how you're using this module? It looks like there may be some sort of circular inheritance going on. Very, very similar to this postgresql module bug report.

[alexjfisher]

The fix in postgresql module is puppetlabs/puppetlabs-postgresql@1507123

[pschichtel]

it is just:

include ::mongodb::server
include ::mongodb::client

with the following hiera keys:

mongodb::globals::manage_package_repo: true
mongodb::globals::manage_package: true
mongodb::server::auth: false
mongodb::server::bind_ip: '0.0.0.0'
mongodb::server::storage_engine: 'wiredTiger'

[pschichtel]

Setting manage_package_repo to false will solve/hide the problem.

[pschichtel]

This happens with puppet 5.3.3 as well

[pschichtel]

I have still the exact same problem.

[ekohl]

@pschichtel could you test #474 and see if it fixes your issue?

[pschichtel]

@ekohl the dependency problem is gone, but APT is telling me the repo isn't signed which seems wrong. I guess the issue reported here is fixed then.