Jira (PUP-5362) `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5362 `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache Change By: Josh Cooper Comment: This is a regression introduced in [fa4a1d9|https://github.com/puppetlabs/puppet/commit/fa4a1d9] in 3.0.0 as part of applying the catalog in a forked child. 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 (PDB-2049) extract with aggregate function application still requires a subexpression
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2049 extract with aggregate function application still requires a subexpression Issue Type: Bug Assignee: Unassigned Created: 2015/10/13 10:46 PM Priority: Normal Reporter: Wyatt Alt We still lack support for queries of this form: curl -X GET http://localhost:8080/pdb/query/v4/reports -d 'query=["extract",[["function","count"],"status"],["group_by","status"]]' Add Comment
Jira (FACT-780) Running 'facter --puppet' produced no warning/debug messages
Title: Message Title Josh Cooper updated an issue Facter / FACT-780 Running 'facter --puppet' produced no warning/debug messages Change By: Josh Cooper Fix Version/s: FACT 3.1.1 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 (FACT-1195) Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter
Title: Message Title Josh Cooper updated an issue Facter / FACT-1195 Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter Change By: Josh Cooper Sprint: Client 2015- 10 11 - 28 11 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-5144) Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5144 Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Puppet Change By: Josh Cooper Sprint: Client 2015- 10 11 - 28 11 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-5143) Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5143 Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet Change By: Josh Cooper Sprint: Client 2015- 10 11 - 28 11 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 (FACT-1196) Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Facter
Title: Message Title Josh Cooper updated an issue Facter / FACT-1196 Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Facter Change By: Josh Cooper Sprint: Client 2015- 10 11 - 28 11 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-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Change By: Josh Cooper Prior to PUP-5215, the openssl vendored in our MSI would attempt to load certificates from an insecure directory (ie not owned by Administrators/System). We need to add an acceptance test to verify our vendored ruby is using a trusted directory, e.g. 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-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Change By: Josh Cooper Prior to PUP-5215, the openssl vendored in our MSI would attempt to load certificates from an insecure directory (ie not owned by Administrators/System). We need to add an acceptance test to verify our vendored ruby is using a trusted directory , e . g. 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-5340) puppet apply doesn't honor --catalog_cache_terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5340 puppet apply doesn't honor --catalog_cache_terminus Change By: Josh Cooper Release Notes Summary: Changes `puppet apply` to store a cached copy of the catalog it applied in `$client_datadir/catalog/.json`, to be consistent with `puppet agent`. Release Notes: Bug Fix 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-5362) `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache
Title: Message Title Josh Cooper commented on PUP-5362 Re: `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache This is a regression introduced in fa4a1d9 in 3.0.0 as part of applying the catalog in a forked child. 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-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Josh Cooper Status: Ready for CI Test Assignee: Peter Huene qa 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-4055) Support DNF package manager (yum successor)
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-4055 Support DNF package manager (yum successor) Change By: Josh Cooper Status: Ready for CI Test Assignee: qa 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 (FACT-1252) SPARC-T4 not in solaris.models fact
Title: Message Title Josh Cooper updated an issue Facter / FACT-1252 SPARC-T4 not in solaris.models fact Change By: Josh Cooper Fix Version/s: FACT 3.1.1 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-5083) Fail env catalog compilation if there are unfulfilled dependencies
Title: Message Title Thomas Hallgren commented on PUP-5083 Re: Fail env catalog compilation if there are unfulfilled dependencies I added a test to validate that require also creates a dependency in maint commit 5aa1ce0 and another test to assert that require without export is detected in maint commit 64a0cde. This ticket does not address the case where properties are not referenced. I think the JIRA that Eric Thompson didn't find is PUP-5304. 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-5083) Fail env catalog compilation if there are unfulfilled dependencies
Title: Message Title Thomas Hallgren assigned an issue to Eric Thompson Puppet / PUP-5083 Fail env catalog compilation if there are unfulfilled dependencies Change By: Thomas Hallgren Assignee: Thomas Hallgren Eric Thompson 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-5060) Add support for --facts in 'puppet lookup' command
Title: Message Title Thomas Hallgren commented on PUP-5060 Re: Add support for --facts in 'puppet lookup' command The description of this issue is a bit vague. How should these facts be used? Do they override by merging with existing facts or do they replace all facts? Would it be a good idea to make that a choice? 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-5342) Empty arrays does not match type of typed arrays
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5342 Empty arrays does not match type of typed arrays Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (HI-118) There's no way to set resolution_type when using data bindings
Title: Message Title John Bollinger commented on HI-118 Re: There's no way to set resolution_type when using data bindings +1 for lookupoptions. This seems to be a viable way to define the lookup type on a per-item basis. Questions: Is it intended that a merge strategy being defined for a given key indicates that ordinary lookups for that key should employ merging (of the specified flavor)? The alternative would be that only hash-merge lookups that happen to be performed for the key, as requested by some other means, would employ the specified strategy. The details presented in the proposal seem specific to hash-valued items. Supposing that the answer to my previous question is "yes", is it intended or desirable that array lookup type can be specified this way as well (i.e. as if hiera_array() were used)? I think the proposal says that the lookupoptions::* keys are intended themselves to be looked up in the data hierarchy. What type of lookup is used for them? Does the facility they provide apply recursively? 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-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-5089) classes should be allowable as application components
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5089 classes should be allowable as application components Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5076) Non-component resources need to have defined behavior for PuppetConf
Title: Message Title Henrik Lindberg commented on PUP-5076 Re: Non-component resources need to have defined behavior for PuppetConf In the discussion about this, it was concluded that regular resources contained in the environment catalog (i.e. contained in/under a site _expression_) should fail since there is no functionality that applies those resources to anything. (A "regular resource" would be either an instance of a resource type e.g. File, or a user defined resource that is not a service/capability). (Can we also change the title of this ticket now that we are passed Puppet Conf?) Ping Ryan Coleman 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-5292) regsubst doesn't work on empty arrays in puppet 4.x
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5292 regsubst doesn't work on empty arrays in puppet 4.x Change By: Henrik Lindberg Assignee: John Duarte Henrik Lindberg 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-5292) regsubst doesn't work on empty arrays in puppet 4.x
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5292 regsubst doesn't work on empty arrays in puppet 4.x Change By: Henrik Lindberg Story Points: 1 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-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-5342) Empty arrays does not match type of typed arrays
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5342 Empty arrays does not match type of typed arrays Change By: Henrik Lindberg Scope Change Category: Found Scope Change Reason: this makes it difficult to call certain functions Release Notes Summary: The type system did not accept an empty array as valid when the array type matched against did not accept Undef entries. Sprint: Language Triage 2015-10-14 Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5292) regsubst doesn't work on empty arrays in puppet 4.x
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5292 regsubst doesn't work on empty arrays in puppet 4.x Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-5208) owner uid --> integer 4294967294 too big to convert to `int'
Title: Message Title Karsten commented on PUP-5208 Re: owner uid --> integer 4294967294 too big to convert to `int' sorry for the delay I try it with other puppet agent version: ``` rubygem-puppet-vim-3.8.2-1.2 puppet-3.8.2-5 ruby1.8-rubygem-puppet-3.8.2-1.2 rubygem-puppet-3.8.2-1.2 ``` the result is the same ``` Error: Failed to set owner to '4294967294': integer 4294967294 too big to convert to `int' Error: /Stage[main]/Users::Services/Users::Virtual::Localuser[w2008]/File[/etc/ssh/authorized_keys/w2008]/owner: change from root to w2008 failed: Failed to set owner to '4294967294': integer 4294967294 too big to convert to `int' Error: Failed to set group to '4294967294': integer 4294967294 too big to convert to `int' Error: /Stage[main]/Users::Services/Users::Virtual::Localuser[w2008]/File[/etc/ssh/authorized_keys/w2008]/group: change from root to w2008 failed: Failed to set group to '4294967294': integer 4294967294 too big to convert to `int' Notice: /Stage[main]/Users::Services/Users::Virtual::Localuser[w2008]/Ssh_authorized_key[w2008]: Dependency File[/etc/ssh/authorized_keys/w2008] has failures: true Warning: /Stage[main]/Users::Services/Users::Virtual::Localuser[w2008]/Ssh_authorized_key[w2008]: Skipping because of failed dependencies ``` any ideas? 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-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5208) owner uid --> integer 4294967294 too big to convert to `int'
Title: Message Title Karsten updated an issue Puppet / PUP-5208 owner uid --> integer 4294967294 too big to convert to `int' Change By: Karsten Environment: Master: Debian Jessie (puppetmaster 3.7.2-4)Agent: SLES 11 SP3 (puppet-3.8.2-1.2 , ruby 1.8.7 ) 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-5208) owner uid --> integer 4294967294 too big to convert to `int'
Title: Message Title Karsten updated an issue Puppet / PUP-5208 owner uid --> integer 4294967294 too big to convert to `int' Change By: Karsten Environment: Master: Debian Jessie (puppetmaster 3.7.2-4)Agent: SLES 11 SP3 (puppet-3. 3 8 . 1 2 - 5 1 . 6 2 ) 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-5076) Non-component resources need to have defined behavior
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-5076 Non-component resources need to have defined behavior Change By: Ryan Coleman Summary: Non-component resources need to have defined behavior for PuppetConf 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 (HI-118) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on HI-118 Re: There's no way to set resolution_type when using data bindings The options should be given as for the lookup function (it covers the functionality of hiera, hiera_array and hiera_hash and works with both hiera as well as "data in modules" (a.k.a data providers). The puppet setting should not be specific to "hiera" - it is a data-binder feature. The lookup options for the key only applies to automatic data binding. For other use cases (i.e. directly calling lookup the user can manually look up the lookup options for the key. For manual calls to the hiera_xxx functions, the user also needs to pick a specific hiera_xxx call based on the options as well as transforming the options to adapt to the hiera_xxx functions limited set of features. 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-5350) Puppet filter function does not behave consistently across all supported argument types.
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5350 Puppet filter function does not behave consistently across all supported argument types. Change By: Thomas Hallgren Sprint: Language Triage Client 2015-10-14 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-5350) Puppet filter function does not behave consistently across all supported argument types.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5350 Puppet filter function does not behave consistently across all supported argument types. Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5292) regsubst doesn't work on empty arrays in puppet 4.x
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5292 regsubst doesn't work on empty arrays in puppet 4.x Change By: Steve Barlow Sprint: Client Language 2015-10-14 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-5350) Puppet filter function does not behave consistently across all supported argument types.
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5350 Puppet filter function does not behave consistently across all supported argument types. Change By: Steve Barlow Sprint: Client Language 2015-10-14 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-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-1963) Generated resources never receive dependency edges
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Michael Smith Assignee: Michael Smith 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-1963) Generated resources never receive dependency edges
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Michael Smith Assignee: Michael Smith 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-5076) Non-component resources need to have defined behavior
Title: Message Title Luke Kanies commented on PUP-5076 Re: Non-component resources need to have defined behavior Henrik Lindberg We will almost definitely need to differentiate resource types - those that have to run on a local host, and those that contact remote hosts. We'll continue to fail if host-local resources are included in the catalog – just like we should fail if, for instance, Cisco resources are attempted to be used on Solaris machines. You might even find that the 'confine' mechanism works just fine to support this. It'll end up being pretty complicated, probably on multiple dimensions. In the short term (i.e., Ankeny) we just need consistent behavior. In the long term, though, it needs to align with the thread in my keynote, which is that the orchestrator becomes the integration point for all agentless work. Does that make sense? 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 (PDB-2047) (maint) Initial HA design doc
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2047 (maint) Initial HA design doc Issue Type: Bug Assignee: Unassigned Created: 2015/10/13 9:50 AM Priority: Normal Reporter: gepetto-bot 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-5083) Fail env catalog compilation if there are unfulfilled dependencies
Title: Message Title Eric Thompson commented on PUP-5083 Re: Fail env catalog compilation if there are unfulfilled dependencies thanks Thomas Hallgren! 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title James Pogran commented on PUP-5064 Re: Remove ability to install Puppet on Windows Server 2003 Tested against win2012 and MSI installs normally 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5064 Remove ability to install Puppet on Windows Server 2003 Change By: Ryan Gard QA Risk Assessment: Medium QA Status: Reviewed QA Contact: Ryan Gard 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title Ryan Gard assigned an issue to Ryan Gard Puppet / PUP-5064 Remove ability to install Puppet on Windows Server 2003 Change By: Ryan Gard Assignee: qa Ryan Gard 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-5355) Add additional OIDs for cloud specific data
Title: Message Title Chris Barker commented on PUP-5355 Re: Add additional OIDs for cloud specific data PR here containing the additional names https://github.com/puppetlabs/puppet/pull/4338/ ["1.3.6.1.4.1.34380.1.1.18", 'pp_region', 'Puppet Node Region Name'], ["1.3.6.1.4.1.34380.1.1.19", 'pp_datacenter', 'Puppet Node Datacenter Name'], ["1.3.6.1.4.1.34380.1.1.20", 'pp_zone', 'Puppet Node Zone Name'], ["1.3.6.1.4.1.34380.1.1.21", 'pp_network', 'Puppet Node Network Name'], ["1.3.6.1.4.1.34380.1.1.22", 'pp_securitypolicy', 'Puppet Node Security Policy Name'], ["1.3.6.1.4.1.34380.1.1.23", 'pp_cloudplatform', 'Puppet Node Cloud Platform Name'], Add Comment
Jira (PUP-5355) Add additional OIDs for cloud specific data
Title: Message Title Chris Barker created an issue Puppet / PUP-5355 Add additional OIDs for cloud specific data Issue Type: New Feature Assignee: Unassigned Created: 2015/10/13 10:23 AM Priority: Normal Reporter: Chris Barker After using the OID's as part of cloud provisioning practices, it has become apparent we need to add some more 'cloud' specific information / words. While not trying to be specific to one cloud platform, these words are descriptive of where the origin of a machine may be coming from, useful for both classification and validation in autosigning policies. pp_region 1.3.6.1.4.1.34380.1.1.18 pp_datacenter 1.3.6.1.4.1.34380.1.1.19 pp_zone 1.3.6.1.4.1.34380.1.1.20 pp_network 1.3.6.1.4.1.34380.1.1.21 pp_securitypolicy 1.3.6.1.4.1.34380.1.1.22 Add Comment
Jira (PUP-5334) Puppet can't remove users from groups in OSX.
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5334
Puppet can't remove users from groups in OSX.
Change By:
William Hopper
When specifying members of a group in OSX, users can be added successfully, but not removed.{noformat}lyokd3cqy68n68o:~ root# puppet apply -e "group { 'group_a': members => ['test1','test2','test3'] }"Notice: Compiled catalog for lyokd3cqy68n68o.delivery.puppetlabs.net in environment production in 0.36 secondsNotice: /Stage[main]/Main/Group[group_a]/ensure: createdNotice: Applied catalog in 0.32 secondslyokd3cqy68n68o:~ root# puppet resource group group_agroup { 'group_a': ensure => 'present', gid => '23', members => ['test1', 'test2', 'test3'],}lyokd3cqy68n68o:~ root# puppet apply -e "group { 'group_a': members => ['test1','test2'] }"Notice: Compiled catalog for lyokd3cqy68n68o.delivery.puppetlabs.net in environment production in 0.35 secondsNotice: /Stage[main]/Main/Group[group_a]/members: members changed 'test1,test2,test3' to 'test1,test2'Notice: Applied catalog in 0.07 secondslyokd3cqy68n68o:~ root# puppet resource group group_agroup { 'group_a': ensure => 'present', gid => '23', members => ['test1', 'test2', 'test3'],}{noformat}From GitHub, ccaviness reports that this is *not* a problem in OSX 10.11 on Puppet 3.8.2 , so this is potentially a regression :{noformat}@whopper I can remove users from groups just fine:fox:~ root# puppet resource group removegroup { 'remove': ensure => 'present', gid => '23', members => ['root', 'daemon', 'crc'],}fox:~ root# puppet applygroup { 'remove': ensure => 'present', members => ['root', 'daemon'],}Notice: Compiled catalog for 045627f2-3d66-46b1-95bc-1bc74154e1d3 in environment gmac_unstable in 0.58 secondsNotice: /Stage[main]/Main/Group[remove]/members: members changed 'root,daemon,crc' to 'root,daemon'Notice: Finished catalog run in 0.30 secondsfox:~ root# puppet resource group removegroup { 'remove': ensure => 'present', gid => '23', members => ['root', 'daemon'],}This is on OS X 10.11 and (patched with this PR) puppet 3.8.2.{noformat}
Add Comment
Jira (PUP-5334) Puppet can't remove users from groups in OSX.
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5334
Puppet can't remove users from groups in OSX.
Change By:
William Hopper
When specifying members of a group in OSX, users can be added successfully, but not removed.{noformat}lyokd3cqy68n68o:~ root# puppet apply -e "group { 'group_a': members => ['test1','test2','test3'] }"Notice: Compiled catalog for lyokd3cqy68n68o.delivery.puppetlabs.net in environment production in 0.36 secondsNotice: /Stage[main]/Main/Group[group_a]/ensure: createdNotice: Applied catalog in 0.32 secondslyokd3cqy68n68o:~ root# puppet resource group group_agroup { 'group_a': ensure => 'present', gid => '23', members => ['test1', 'test2', 'test3'],}lyokd3cqy68n68o:~ root# puppet apply -e "group { 'group_a': members => ['test1','test2'] }"Notice: Compiled catalog for lyokd3cqy68n68o.delivery.puppetlabs.net in environment production in 0.35 secondsNotice: /Stage[main]/Main/Group[group_a]/members: members changed 'test1,test2,test3' to 'test1,test2'Notice: Applied catalog in 0.07 secondslyokd3cqy68n68o:~ root# puppet resource group group_agroup { 'group_a': ensure => 'present', gid => '23', members => ['test1', 'test2', 'test3'],}{noformat} From GitHub, ccaviness reports that this is *not* a problem in OSX 10.11 on Puppet 3.8.2:{noformat}@whopper I can remove users from groups just fine:fox:~ root# puppet resource group removegroup { 'remove': ensure => 'present', gid => '23', members => ['root', 'daemon', 'crc'],}fox:~ root# puppet applygroup { 'remove': ensure => 'present', members => ['root', 'daemon'],}Notice: Compiled catalog for 045627f2-3d66-46b1-95bc-1bc74154e1d3 in environment gmac_unstable in 0.58 secondsNotice: /Stage[main]/Main/Group[remove]/members: members changed 'root,daemon,crc' to 'root,daemon'Notice: Finished catalog run in 0.30 secondsfox:~ root# puppet resource group removegroup { 'remove': ensure => 'present', gid => '23', members => ['root', 'daemon'],}This is on OS X 10.11 and (patched with this PR) puppet 3.8.2.{noformat}
Add Comment
Jira (FACT-1238) Facter should respect long-form hostnames to populate hostname, domain, and FQDN
Title: Message Title Peter Huene assigned an issue to qa Facter / FACT-1238 Facter should respect long-form hostnames to populate hostname, domain, and FQDN Change By: Peter Huene Status: Ready for CI Test Assignee: qa 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-5025) Package resource showing notice when ensure attribute contains Epoch tag
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-5025 Package resource showing notice when ensure attribute contains Epoch tag Change By: Peter Huene Assignee: Peter Huene 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 (PDB-2018) Update changelog/release notes
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2018 Update changelog/release notes Change By: Wyatt Alt Fix Version/s: PDB 2.3.x 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 (PDB-2048) Add option to disable cleartext HTTP port
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2048 Add option to disable cleartext HTTP port Issue Type: Bug Assignee: Unassigned Created: 2015/10/13 10:41 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title James Pogran assigned an issue to qa Puppet / PUP-5064 Remove ability to install Puppet on Windows Server 2003 Change By: James Pogran Status: Ready for CI Test Assignee: James Pogran qa 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 (PDB-2043) (maint) This commit tidy's up the examples and markdown in the README
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2043 (maint) This commit tidy's up the examples and markdown in the README Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Had time, during Contrib Summit Story Points: 1 Sprint: PuppetDB 2015-10-21 Fix Version/s: PDB module-5.1.0 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"
Jira (PUP-3953) Puppet resource doesn't properly escape single quotes.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3953 Puppet resource doesn't properly escape single quotes. Change By: Josh Cooper Story Points: 1 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-5316) puppet agent paths test should be skipped on non-AIO test runs
Title: Message Title Josh Cooper commented on PUP-5316 Re: puppet agent paths test should be skipped on non-AIO test runs The puppet-agent path test was updated as part of PUP-5009 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title James Pogran commented on PUP-5064 Re: Remove ability to install Puppet on Windows Server 2003 CI successful packaging https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet/job/platform_aio-puppet_pkg-build_master/252/ 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-5351) Create AuthConfLoader hook for Puppet Server tk-authorization
Title: Message Title Kurt Wall updated an issue Puppet / PUP-5351 Create AuthConfLoader hook for Puppet Server tk-authorization Change By: Kurt Wall QA Status: Reviewed 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-5351) Create AuthConfLoader hook for Puppet Server tk-authorization
Title: Message Title Kurt Wall updated an issue Puppet / PUP-5351 Create AuthConfLoader hook for Puppet Server tk-authorization Change By: Kurt Wall QA Risk Assessment: Low 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 (PDB-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection Here's 2092 lines of log from puppetdb, it throws a general ssl error. Seems to start fine but failed on a connection from puppetserver. Here's the puppetdb log https://gist.github.com/prometheanfire/42d7c79e49eae852b17c Here's the puppetserver log (just the connection to puppetdb) https://gist.github.com/prometheanfire/81132568f8c3820d8520 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 (PDB-2048) Add option to disable cleartext HTTP port
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2048 Add option to disable cleartext HTTP port Change By: Kurt Wall QA Risk Assessment Reason: Adding additional functionality 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-5351) Create AuthConfLoader hook for Puppet Server tk-authorization
Title: Message Title Kurt Wall updated an issue Puppet / PUP-5351 Create AuthConfLoader hook for Puppet Server tk-authorization Change By: Kurt Wall QA Risk Assessment Reason: New features not risked 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 (PDB-2048) Add option to disable cleartext HTTP port
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2048 Add option to disable cleartext HTTP port Change By: Kurt Wall QA Risk Assessment: Low 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 (PDB-2048) Add option to disable cleartext HTTP port
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2048 Add option to disable cleartext HTTP port Change By: Kurt Wall QA Status: Reviewed 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-3713) Allow zfs to create a zvol
Title: Message Title Kylo Ginsberg commented on PUP-3713 Re: Allow zfs to create a zvol Andrew Thompson would you be interested in submitting that as a pull request at https://github.com/puppetlabs/puppet? 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-5358) user resource should_modify_gid test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5358 user resource should_modify_gid test fails on AIX Issue Type: Bug Assignee: Unassigned Created: 2015/10/13 1:31 PM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte Puppet acceptance test Case tests/resource/user/should_modify_gid.rb fails with the following: Failed Tests Cases: Test Case tests/resource/user/should_modify_gid.rb reported: #
Jira (PUP-5009) Fix "git" acceptance tests
Title: Message Title Josh Cooper commented on PUP-5009 Re: Fix "git" acceptance tests Stable passed CI, resolving /cc Eric Thompson Sean Griffin 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-5356) Nagios extension check_puppet.rb error
Title: Message Title Kylo Ginsberg commented on PUP-5356 Re: Nagios extension check_puppet.rb error I moved the ticket to PUP since that's where the fix would be. That said, to be honest, I didn't even know this script exists. And on casual look it has been out of date for a while (e.g. on the stable branch it was never updated for puppet 4 paths). So David Ruiz Estefanía, given the above, I doubt we'll have a chance to work on this any time soon (although we always welcome community contributions to fix such things). 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 (PDB-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Kenneth Barber commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection Matthew Thode what error do you get from the puppet master when this failure occurs? I presume the source of your debugging here is the failure from a puppet master right? 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-5357) PMT - Allow Installation of Latest Pre-release Modules
Title: Message Title Alex Dreyer moved an issue Puppet / PUP-5357 PMT - Allow Installation of Latest Pre-release Modules Change By: Alex Dreyer Component/s: pmt Component/s: PMT Issue Type: Improvement New Feature Key: CODEMGMT PUP - 395 5357 Project: Code Management Puppet 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
Jira (PUP-3953) Puppet resource doesn't properly escape single quotes.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3953 Puppet resource doesn't properly escape single quotes. Change By: Josh Cooper Component/s: Community 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-3953) Puppet resource doesn't properly escape single quotes.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3953 Puppet resource doesn't properly escape single quotes. Change By: Josh Cooper Sprint: Client 2015-10-28 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-3953) Puppet resource doesn't properly escape single quotes.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3953 Puppet resource doesn't properly escape single quotes. Change By: Josh Cooper Fix Version/s: PUP 4.2.3 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-5340) puppet apply doesn't honor --catalog_cache_terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5340 puppet apply doesn't honor --catalog_cache_terminus Change By: Josh Cooper Fix Version/s: PUP 4.3.0 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title James Pogran updated an issue Puppet / PUP-5064 Remove ability to install Puppet on Windows Server 2003 Change By: James Pogran Attachment: Screen Shot 2015-10-13 at 1.01.35 PM.png Attachment: Screen Shot 2015-10-13 at 1.02.04 PM.png 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-5064) Remove ability to install Puppet on Windows Server 2003
Title: Message Title James Pogran commented on PUP-5064 Re: Remove ability to install Puppet on Windows Server 2003 Tested against windows 2003 x86_x64 and ran both the x86 and x64 installers. Both produced the intended error message. 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-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title Kenneth Barber commented on PUP-5081 Re: CapabilityFinder needs to look up capabilities by code_id Note: So this only works against the puppetdb stable branch, which will be shipped as 3.2.0 soon. There is no shipped version that includes this yet. So the query would be against: /pdb/query/v4/resources ... ["in", "certname", ["extract", "certname", ["select_catalogs", ["=", "code_id", "abcdefg"]]] Obviously you can combined this subquery ^^ with other queries: ["and", ["=","type","Package"], ["=","title","foo"], ["in", "certname", ["extract", "certname",
Jira (PDB-2048) Add option to disable cleartext HTTP port
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2048 Add option to disable cleartext HTTP port Change By: Kenneth Barber Scope Change Category: Adopted Scope Change Reason: PR raised by community Story Points: 1 Sprint: PuppetDB 2015-10-21 Scrum Team: PuppetDB Fix Version/s: PDB module-5.1.0 Issue Type: Bug New Feature Add Comment
Jira (PUP-5356) Nagios extension check_puppet.rb error
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-5356 Nagios extension check_puppet.rb error Change By: Kylo Ginsberg Workflow: Release Engineering Scrum Team Workflow Key: CPR PUP - 236 5356 Project: Community Package Repository Puppet 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-1963) Generated resources never receive dependency edges
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Michael Smith Assignee: Michael Smith 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-1963) Generated resources never receive dependency edges
Title: Message Title Eric Thompson commented on PUP-1963 Re: Generated resources never receive dependency edges risk is independent of test-level. good coverage at unit-level is great. but medium risk implies we should still manually validate against full stack. 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 (PDB-2045) puppetdb immediately closes valid ssl connection
Title: Message Title Matthew Thode commented on PDB-2045 Re: puppetdb immediately closes valid ssl connection here's the openssl command echo 'GET /' | openssl s_client -connect puppet.mthode.org:8081 -4 -tls1_2 -no_ssl3 -no_ssl2 -no_tls1 -no_tls1_1 -CAfile ca.pem -cert public.pem -key private.pem I'm using puppetserver 2.1.1 and I saw the error first on a puppet run (400 error trying to connect to puppetdb) Warning: Error 400 on SERVER: Could not retrieve facts for puppet-client.mthode.org: Failed to find facts from PuppetDB at puppet:8140: Failed to execute '/pdb/query/v4/nodes/puppet-client.mthode.org/facts' on any of the following 'server_urls': https://puppetdb.mthode.org:8081 this is with `soft_write_failure = true` 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-1963) Generated resources never receive dependency edges
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium QA Contact: Narmadha Perumal 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
Jira (PUP-5359) scheduled_task won't work with schedule monthly
Title: Message Title
Anthony Scudese updated an issue
Puppet / PUP-5359
scheduled_task won't work with schedule monthly
Change By:
Anthony Scudese
When trying to set a scheduled_task trigger I get the following error:{code}C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:8:in `'Error: /Stage[main]/Adoberum::Service/Scheduled_task[Adobe Remote Update Manager]/ensure: change from absent to present failed: Failed to call #::SetTrigger with HRESULT: -2147024809.: The parameter is incorrect.{code}This happens for both month-by-date and month-by-weekday.My scheduled_task resource is as follows:{code}scheduled_task { 'Adobe Remote Update Manager': ensure=> present, command => $adoberum::command_source, enabled => true, trigger => {schedule => monthly, on => [1,3,last,17], start_time => '08:00', months => [1, 3, 5]},}{code}I've tried quoting and unquoting the parameter in the triggers hash. Works completely fine for daily and weekly triggers.This has been tested on two different windows 7 machines with two different puppet version and the error is the same. Full Trace:{code}Error: Failed to call #::SetTrigger with HRESULT: -2147024809.: The parameter is incorrect.C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:142:in `block (3 levels) in []'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:966:in `block (2 levels) in populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `block in populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:621:in `block (2 levels) in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:117:in `block in UseInstance'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `UseInstance'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:620:in `block in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:193:in `block in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:188:in `each'C:/Program Files/Puppet
Jira (PUP-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title Henrik Lindberg commented on PUP-5081 Re: CapabilityFinder needs to look up capabilities by code_id Thanks Kenneth Barber. Eric Thompson How does the PDB feature availability on stable only (atm) affect us testing wise? 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-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5081 CapabilityFinder needs to look up capabilities by code_id Change By: Henrik Lindberg Assignee: Kenneth Barber 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-5359) scheduled_task won't work with schedule monthly
Title: Message Title
Anthony Scudese updated an issue
Puppet / PUP-5359
scheduled_task won't work with schedule monthly
Change By:
Anthony Scudese
When trying to set a scheduled_task trigger I get the following error:{code}C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:8:in `'Error: /Stage[main]/Adoberum::Service/Scheduled_task[Adobe Remote Update Manager]/ensure: change from absent to present failed: Failed to call #::SetTrigger with HRESULT: -2147024809.: The parameter is incorrect.{code}This happens for both month-by-date and month-by-weekday.My scheduled_task resource is as follows:{code}scheduled_task { 'Adobe Remote Update Manager': ensure=> present, command => $adoberum::command_source, enabled => true, trigger => {schedule => monthly, on => [1,3,last,17], start_time => '08:00', months => [1, 3, 5]},}{code}I've tried quoting and unquoting the parameter in the triggers hash. Works completely fine for daily and weekly triggers.This has been tested on two different windows 7 machines with two different puppet version and the error is the same.Full Trace (from 3.7.4 Puppet) :{code}Error: Failed to call #::SetTrigger with HRESULT: -2147024809.: The parameter is incorrect.C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:142:in `block (3 levels) in []'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:966:in `block (2 levels) in populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:918:in `block in populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:917:in `populate_trigger'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:621:in `block (2 levels) in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:117:in `block in UseInstance'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/com.rb:114:in `UseInstance'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:620:in `block in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/taskscheduler.rb:615:in `trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:193:in `block in trigger='C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:188:in `each'C:/Program
Jira (PUP-5360) Support for autorelations of defined types inside custom types
Title: Message Title
Adam S created an issue
Puppet / PUP-5360
Support for autorelations of defined types inside custom types
Issue Type:
New Feature
Affects Versions:
PUP 4.x
Assignee:
Kylo Ginsberg
Components:
Catalog Application, Community, DSL
Created:
2015/10/13 2:14 PM
Priority:
Normal
Reporter:
Adam S
Add support for Custom types to autorelation a defined type. Currently you can only do autorelations(require, before, notify, subscribe, etc.) inside a custom type of another custom type and there is no ability to do it with a defined type.
This feature would extend the current capability of putting the soft relationship ability of: custom type - autorequire(:customtype) do .. end, over to, custom type - autorequire(:definedtype) do .. end and if colons exist, autorequire('definedtype::define') do .. end.
One example where this helps is with a firewall or firewalld module where you want to create a direct rule that contains an ipset, an ipset is an extension of iptables and the corresponding ipset should be created before the direct rule is created if the --match-set exists in their direct rule line. Firewall and firewalld are both custom types and ipset from mighq/ipset is currently a defined type. Note :component is THE wrapper class for all defined types in puppet DSL.
Jira (PUP-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title Eric Thompson commented on PUP-5081 Re: CapabilityFinder needs to look up capabilities by code_id i don't believe it really impacts our testing right now, assuming capability/service finder works either way. 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-5359) scheduled_task won't work with schedule monthly
Title: Message Title Anthony Scudese created an issue Puppet / PUP-5359 scheduled_task won't work with schedule monthly Issue Type: Bug Affects Versions: PUP 3.8.3, PUP 3.7.4 Assignee: Kylo Ginsberg Components: Types and Providers, Windows Created: 2015/10/13 2:09 PM Environment: Ubuntu Puppet Master 3.8.2 / 3.4.3 Windows 7 3.8.3/3.7.4 Labels: scheduled_task windows monthly settrigger hresult Priority: Normal Reporter: Anthony Scudese When trying to set a scheduled_task trigger I get the following error:
Jira (PUP-5360) Support for autorelations of defined types inside custom types
Title: Message Title
Adam S updated an issue
Puppet / PUP-5360
Support for autorelations of defined types inside custom types
Change By:
Adam S
Add support for Custom types to autorelation a defined type. Currently you can only do autorelations(require, before, notify, subscribe, etc.) inside a custom type of another custom type and there is no ability to do it with a defined type.This feature would extend the current capability of putting the soft relationship ability of: custom type - autorequire(:customtype) do .. end, over to, custom type - autorequire(:definedtype) do .. end and if colons exist, autorequire('definedtype::define') do .. end.One example where this helps is with a firewall or firewalld module where you want to create a direct rule that contains an ipset, an ipset is an extension of iptables and the corresponding ipset should be created before the direct rule is created if the --match-set exists in their direct rule line. Firewall and firewalld are both custom types and ipset from mighq/ipset is currently a defined type. Note :component is THE wrapper class for all defined types in puppet DSL.Previously support for this was provided via:{noformat} autorequire(:component) doipset_arr = []self[:rules].each do |rule| if /-m\s+set.*--match-set\s+(.*?)\s+/.match(rule['args'])if result = catalog.resource("Ipset[#{$1}]") ipset_arr << resultend endendipset_arr end{noformat}Proposed changes would allow:{noformat} autorequire(:ipset) doipset_arr = []self[:rules].each do |rule| if /-m\s+set.*--match-set\s+(.*?)\s+/.match(rule['args'])if result = catalog.resource("Ipset[#{$1}]") ipset_arr << resultend endendipset_arr end{noformat}The only difference there is that it ensures we have a defined type of that name(:ipset) prior to going into to parse the details, whereas :component is the custom type wrapper class for all defined types and is rather generic which means any class that calls :component will run even if the defined type it's looking for isn't in the catalog. It's no real time savings and may be a slight compile burden but allows for more straightforward flexible autorelations usage. I could also just return in my ipset_arr the names of the ipset rules at that point such as $1 rather than grabbing catalog.resource("Ipset[#{$1}]") (the whole resource) as the autorelations already knows how to handle it if we return an array in our that doesn't include the resource, rather only the namevar contents of the resource that we're wishing to autorelation.That would bring us inline with how File autorelations work where it's often {noformat}[self[:name]]{noformat} that's used. We can then do: {noformat} autorequire(:ipset) doipset_arr = []self[:rules].each do |rule| if /-m\s+set.*--match-set\s+(.*?)\s+/.match(rule['args']) ipset_arr << $1 endendipset_arr end{noformat}Finally here is the link to the PR to supply this feature, I have yet to create a spec test for this but it works.https://github.com/puppetlabs/puppet/pull/4337 Also defined types that are inside of modules and not root can be called via autorequire('module::definedtype') do .. end
Jira (PDB-29) Notification hooks
Title: Message Title Eric Zounes commented on PDB-29 Re: Notification hooks I would also like to see events emitted based on all the various actions available through the command API: https://docs.puppetlabs.com/puppetdb/3.1/api/command/v1/commands.html For example, every time a catalog is created, replaced, or deactivated emit an event with the result of this command. 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-5351) Create AuthConfLoader hook for Puppet Server tk-authorization
Title: Message Title Jeremy Barlow commented on PUP-5351 Re: Create AuthConfLoader hook for Puppet Server tk-authorization Merged to puppet master branch at 512bc8. 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-5362) `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache
Title: Message Title William Hopper created an issue Puppet / PUP-5362 `puppet agent` errors out if it can't get a catalog and there's no catalog in the cache Issue Type: Bug Affects Versions: PUP 4.2.2, PUP 3.8.3 Assignee: Unassigned Created: 2015/10/13 5:30 PM Environment: All platforms Priority: Normal Reporter: William Hopper When `puppet agent` is run without the `--no-usecacheonfailure` option (as is the case when running puppet resource service puppet ensure=running, and there is no catalog available in the cache, puppet will explode with: /root/puppet/lib/puppet/agent.rb:77:in `exit': no implicit conversion from nil to integer (TypeError) from
Jira (PUP-5346) Investigate puppet_mcollective_service_management acceptance test failure on AIX
Title: Message Title William Hopper commented on PUP-5346 Re: Investigate puppet_mcollective_service_management acceptance test failure on AIX The root cause of this has been identified in https://tickets.puppetlabs.com/browse/PUP-5362. Fixing that is a much more involved issue, and for now we should focus on getting this test passing on AIX. We'll need to figure out why there's no catalog in the cache for AIX during the acceptance run and try to correct that. 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-5350) Puppet filter function does not behave consistently across all supported argument types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5350 Puppet filter function does not behave consistently across all supported argument types. Change By: Henrik Lindberg Sprint: Language 2015-10-14 Triage 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-5350) Puppet filter function does not behave consistently across all supported argument types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5350 Puppet filter function does not behave consistently across all supported argument types. Change By: Henrik Lindberg Scope Change Category: Found Scope Change Reason: found when testing + running out of non-blocked tickets towards end of sprint Story Points: 1 Release Notes Summary: Note that story points must be set before bringing a ticket into a sprint. To fix, it cannot simply be changed when in the sprint. (Hence the back and forth on this ticket to set story points). Also set the "scope change category" and "reason". Sprint: Language Triage 2015-10-14 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
