The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
nagios resource: add support for ipv6 addresses
|Affected Puppet version:||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
We had a pull request to add ipv6 support to the nagios host resource type:
This pull request was based against puppet core, and nagios support has since been moved out to a module. The change is dead simple, just needs to be targeted against the new module codebase. Would also be advisable to write some tests for host parameters.
Also, at the time that the pull request was generated, this feature does not appear to be available in nagios core; it’s available via a patch and in the Icinga fork:
Thus, if we do add support for it, we might need to wrap it in a puppet “feature”—or otherwise ensure that it doesn’t cause problems with basic nagios deployments.
#1 Updated by Brian Rak almost 4 years ago
Wouldn’t this only break things if you were using a nagios version that didn’t support address6, and made use of address6 in your manifests? Would just including a note with the address6 field in the documentation be enough?
I’m running into this issue now, as I have some hosts with IPv6 support that I’d like to monitor, but the only way to get support is running a patched puppet.