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

Error: default expression for $package_source tries to illegally access not yet evaluated $rpm_iteration #89

Open
ltutar opened this issue Apr 14, 2016 · 2 comments

Comments

@ltutar
Copy link

ltutar commented Apr 14, 2016

When I use the module with PE 2016.1.1, I get the following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, default expression for $package_source tries to illegally access not yet evaluated $rpm_iteration

I did not have this error with PE 2015.3.3
Moving the line in init.pp

  $rpm_iteration       = $::grafana::params::rpm_iteration,

above

  $package_source      = $::osfamily ? {

solved the issue.

ltutar added a commit to ltutar/puppet-grafana that referenced this issue Apr 14, 2016
moved rpm_iteration parameter above package_source parameter.
Otherwise, I get the error
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Evaluation Error: Error while evaluating a Resource Statement,
Evaluation Error: Error while evaluating a Function Call, default
expression for $package_source tries to illegally access not yet
evaluated $rpm_iteration

fixes bfraser#89
@bfraser
Copy link
Owner

bfraser commented Apr 30, 2016

This should be fixed in acc8075 as a result of moving the version logic to the install manifest.

@ltutar
Copy link
Author

ltutar commented Jun 9, 2016

Hi,

The commit 774f8a6 is indeed taking care of the ordering but acc8075 is undoing the previous change. The master is now not working with PE2016.1.1.
Any chance to get 774f8a6 in the master?

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

Successfully merging a pull request may close this issue.

2 participants