Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Zach Leslie commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' Folks still seem to be running into this issue. What information is required to move this along? The PuppetX directory structure has been a pattern for quite some time, and this appears to be a change in behavior on the master side. If there is an updated way that this should be approached, perhaps we could document the fix so the community could update their modules, myself included. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3745) Group membership should be a type of its own.
Title: Message Title Zach Leslie commented on PUP-3745 Re: Group membership should be a type of its own. I've taken a stab at the problem. https://github.com/xaque208/puppet-groupmembership I expect to be adding more providers soon. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3618) Include pkgng provider for FreeBSD
Title: Message Title Zach Leslie commented on PUP-3618 Re: Include pkgng provider for FreeBSD I've updated the PR. Is there other information I can provide? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2995) Proposal for custom trusted oid mapping file
Title: Message Title Zach Leslie commented on PUP-2995 Re: Proposal for custom trusted oid mapping file Is this documentation planned to make it into a release? Looking at master, it looks like the option is documented, but in 3.7.4 it doesn't seem to be present. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2995) Proposal for custom trusted oid mapping file
Title: Message Title Zach Leslie commented on PUP-2995 Re: Proposal for custom trusted oid mapping file Ah, well looking at the PR has the information I was looking for. Just eagerly awaiting this feature. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3618) Include pkgng provider for FreeBSD
Title: Message Title Zach Leslie created an issue Puppet / PUP-3618 Include pkgng provider for FreeBSD Issue Type: Bug Assignee: Zach Leslie Components: Types and Providers Created: 2014/11/04 4:36 PM Priority: Minor Reporter: Zach Leslie Rather than require a module to implement this functionality, Puppet should ship with the new provider and update existing ones to deprecate functionality where no longer required. Add Comment This message was
Jira (PUP-3618) Include pkgng provider for FreeBSD
Title: Message Title Zach Leslie commented on PUP-3618 Re: Include pkgng provider for FreeBSD https://github.com/puppetlabs/puppet/pull/3276 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-714) Exported resource relationship woes
Title: Message Title
Zach Leslie commented on an issue
Re: Exported resource relationship woes
This appears to be related to a module conflict. I triple checked the modules in each of the modulepaths and removed any conflicting modules which then allowed the catalog to get submitted to PuppetDB. I don't know why the catalog was compiling in the first place and failing on submission to PuppetDB, but in any case, the catalog is now retrievable by the node in question.
Apologies for the false alarm. Thanks for taking the time to look at this with me Kenneth Barber.
Add Comment
PuppetDB / PDB-714
Exported resource relationship woes
Consider the following. {code} @@concat::fragment { bacula-client-${::fqdn}: target = '/etc/bacula/conf.d/client.conf', content = template('bacula/client.conf.erb'), tag = bacula-${bacula::params::bacula_director}, } {code} The above resource exports a fragment from a node to be backed up. For those familiar with the fragmen...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PDB-714) Exported resource relationship woes
Title: Message Title
Zach Leslie commented on an issue
Re: Exported resource relationship woes
I will try to replicate this in a testing environment with the minimal amount of setup and code around it. We'll see where this takes us.
Add Comment
PuppetDB / PDB-714
Exported resource relationship woes
Consider the following. {code} @@concat::fragment { bacula-client-${::fqdn}: target = '/etc/bacula/conf.d/client.conf', content = template('bacula/client.conf.erb'), tag = bacula-${bacula::params::bacula_director}, } {code} The above resource exports a fragment from a node to be backed up. For those familiar with the fragmen...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-714) Exported resource relationship woes
Title: Message Title
Zach Leslie created an issue
PuppetDB / PDB-714
Exported resource relationship woes
Issue Type:
Bug
Affects Versions:
1.5.2
Assignee:
Unassigned
Components:
PE
Created:
18/Jun/14 8:32 AM
Priority:
Normal
Reporter:
Zach Leslie
Consider the following.
@@concat::fragment { bacula-client-${::fqdn}:
target = '/etc/bacula/conf.d/client.conf',
content = template('bacula/client.conf.erb'),
tag = bacula-${bacula::params::bacula_director},
}
The above resource exports a fragment from a node to be backed up. For those familiar with the fragment pattern and specifically concat, you will know that there is a corresponding concat resource for the /etc/bacula/conf.d/client.conf file. Due to this being an exported resource, the concat resource exists exists on the node realizing all of the concat::fragment resources that match the given tag.
The problem with the above, is that the catalog fails to compile with an error like so:
Error:
Jira (PUP-2143) Allow OpenBSD service provider to implement :enableable
Title: Message Title Zach Leslie updated an issue Puppet / PUP-2143 Allow OpenBSD service provider to implement :enableable Change By: Zach Leslie PuppethasonlyeverstartedservicesonOpenBSDusingthe-fflag,whichdoesindeedstarttheservice,butdoesnotenablethem.Thisisaproblembecausetheservicesthatpuppetisforciblystartingdonotgetstartedatboottime.Thisisalessthanidealsituationasweshouldbeabletomanagetheenablementofaservice.Torectifysuchadeficiency,thefollowingPRhasbeenpostedforreviewandcomment:https://github.com/puppetlabs/puppet/pull/2495 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
