-
Notifications
You must be signed in to change notification settings - Fork 95
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
4.0.4 not actually installing newrelic-sysmond #40
Comments
Could you paste your manifest declaring the newrelic module/parameters and a fake hiera data so I can reproduce here with the same config. |
Also the Linux OS/version. |
We are seeing the same problems on the first run with 4.1.1 and puppetlabs-apt 2.1.0 on Ubuntu 14.04. On the second puppet apply it corrects.
|
I'm leveraging automatic parameters, so I'm just including your module via console classification (PE3.8) and setting this in hiera: newrelic::server::linux::newrelic_license_key: 'my key here' Ubuntu 14.04.02 (on both nodes and puppetmaster) |
I'm not sure if that's the same issue but I'm having troubles on the first run as well:
That's how I'm using it:
On second run it works fine. |
Is this still an issue using the latest version of the module? |
I just now did the same thing, and I got the same error with puppet version 4.8.1. It stops at
|
From what I can see of newrelic::server::linux it should be installing the newrelic-sysmond package.
I'm trying to feed data from hiera, so I have:
newrelic::server::linux::newrelic_license_key: ''
Is that not enough?
Because it's not actually installing the package
The text was updated successfully, but these errors were encountered: