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

grafana_dashboard folder parameter issue #183

Open
xavigpich opened this issue Aug 23, 2019 · 2 comments
Open

grafana_dashboard folder parameter issue #183

xavigpich opened this issue Aug 23, 2019 · 2 comments

Comments

@xavigpich
Copy link

xavigpich commented Aug 23, 2019

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.x
  • Ruby: builtin
  • Distribution: Centos 7.6
  • Module version: master branch

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

grafana_dashboard { 'test_dashboard':
    grafana_url      => $grafana_url,
    grafana_user     => $grafana_admin_user,
    grafana_password => $grafana_password,
    grafana_api_path => $grafana_api_path,
    organization     => $grafana_organization,

    folder           => 'test',
    content          => template('/path/to/json/file'),
  }

What are you seeing

Module complains about folder parameter not existing for grafana_dashboard resource type.

What behaviour did you expect instead

Creation of test_dashboard dashboard based on json file. folder parameter does exist in the resource type in the master branch of this module

# cat modules/grafana/lib/puppet/type/grafana_dashboard.rb | grep folder -A 3
  newparam(:folder) do
    desc 'The folder to place the dashboard in (optional)'
  end

Output log

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: no parameter named 'folder' on Grafana_dashboard[test_dashboard]

Any additional information you'd like to impart

Folder exists and $grafana_xx variables work fine with other module resource types.

@tim-baker115
Copy link

Also seeing this error, can someone look into this?

@tim-baker115
Copy link

@thisisxgp I've since resolved this issue, after searching for

Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
Server Error: no parameter named

The results seemed to indicate that this was down to "module bleed" (a term I'd never come across before) and a restart of our puppetmaster would resolve it, which it did.

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

No branches or pull requests

2 participants