Jira (PUP-1744) User creation fails on OS X 10.9 if user is added to more than one group
Title: Message Title
Paul Ttterman commented on an issue
Re: User creation fails on OS X 10.9 if user is added to more than one group
We have the same issue.
Add Comment
Puppet / PUP-1744
User creation fails on OS X 10.9 if user is added to more than one group
When I try to create a user with more then one group on Mac OS X 10.9 with puppet 3.4.3 errors are thrown: {noformat} change from absent to admin,wheel failed: undefined method `split' for :absent:Symbol Could not prefetch user provider 'directoryservice': invalid byte sequence in US-ASCII undefined method `split' for :absent:Symbol ---...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-237) Hiera behaviour with variables is inconsistent
Title: Message Title
Vincent Miszczak created an issue
Hiera / HI-237
Hiera behaviour with variables is inconsistent
Issue Type:
Bug
Assignee:
Unassigned
Created:
02/May/14 4:26 AM
Priority:
Normal
Reporter:
Vincent Miszczak
Suppose you have this hierarchy: :hierarchy:
nodes/%{::clientcert}
datacenters/% {datacenter} - common common.yaml: classes: - datacenter nodes/testnode.yaml: datacenter: mydatacenter datacenters/mydatacenter.yaml: classes: - ntp ntp::servers: - myntpserver site.pp that does hiera_include(classes) class datacenter do the following: $datacenter=hiera(datacenter) hiera_include(classes) This gives inconsistent behavior: First pass, %{datacenter}
is not set, so nothing is done there. When common hierarchy is evaluated, Puppet processes datacenter class, get the value for $datacenter then do the hiera_include(). hiera_include() then get datacenters/mydatacenter.yaml classes, ie ntp but ntp settings are defaults, not those in file datacenters/mydatacenter.yaml
That is to say : Puppet was able to get % {datacenter} variable dynamically, was able to instanciate the class ntp dynamically, but does not evaluate the variables dynamically. I don't want to declare datacenterclass for every node (Puppet principle : don't repeat yourself). I want to declare datacenter class as a common rule that exports a %{datacenter}
variable that allows me to include more hiera content dynamically, without having to push facts on the node that would require 2 passes of Puppet to achieve this.
Jira (PDB-629) Is checklist current
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-629 Is checklist current Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Do sub-tickets here match steps in https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process? And do those steps need updating for any recent tooling changes? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-632) Ensure tests are passing
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-632 Ensure tests are passing Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PDB-634) Is there a commit for every bug targeted at the release?
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-634 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Ensure that all tickets targetted at this release have corresponding commits in git. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because
Jira (PDB-635) Tag the release and create packages
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-635 Tag the release and create packages Issue Type: Sub-task Assignee: Melissa Stone Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Developer provides the SHA Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from
Jira (PDB-628) PuppetDB 2.0.0 Release
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-628 PuppetDB 2.0.0 Release Issue Type: Task Assignee: Kenneth Barber Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PDB-633) Is there a bug targeted at the release for every commit?
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-633 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Ensure that all commits in git between the last and current release have corresponding tickets pointing at this release. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PDB-630) Update changelog/release notes
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-630 Update changelog/release notes Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Update the changelog/release notes in documentation/changes.md Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PDB-631) Update documentation indexes for new major release
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-631 Update documentation indexes for new major release Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-642) Push changes to pe-puppetdb branch
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-642 Push changes to pe-puppetdb branch Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber These changes will need to be pushed to the relevant branch for pe-puppetdb Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google
Jira (PDB-638) Packages pushed
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-638 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Distribute the packages previously built into their public places. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (PDB-640) Update the downloads page
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-640 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Update the downloads page with the public download locations and new version information. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PDB-636) Smoke test packages
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-636 Smoke test packages Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PDB-637) Go/no-go meeting
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-637 Go/no-go meeting Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Should include: dev, docs, product, qa, releng Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PDB-628) PuppetDB 2.0.0 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-628 PuppetDB 2.0.0 Release Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-643) Close all resolved tickets and release version in Jira
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-643 Close all resolved tickets and release version in Jira Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Ensure all tickets that were previously resolved are marked now as closed. Ensure the version in Jira is released. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PDB-641) Send out announcements
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-641 Send out announcements Issue Type: Sub-task Assignee: Unassigned Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Send out the release notes in the release format on puppet-users, puppet-dev and puppet-announce. Obtain a bit.ly link to such a thing from marketing and twitter it out, and send a PSA message to IRC channels #puppet and #puppet-dev. Update our hipchat channel with the new link. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-639) Push tag
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-639 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 02/May/14 4:54 AM Priority: Normal Reporter: Kenneth Barber Push the tag made earlier up to the main public repo for the branch in question. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PDB-628) PuppetDB 2.0.0 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-628 PuppetDB 2.0.0 Release Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-628) PuppetDB 2.0.0 Release (May 7th, 2014)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-628 PuppetDB 2.0.0 Release (May 7th, 2014) Change By: Kenneth Barber Due Date: 7/May/14 Fix Version/s: 2.0.0 Summary: PuppetDB2.0.0Release (May7th,2014) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-644) Retire node-ttl-days
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-644 Retire node-ttl-days Issue Type: Improvement Assignee: Unassigned Created: 02/May/14 5:53 AM Priority: Normal Reporter: Kenneth Barber node-ttl-days has been changed to node-ttl, we need to retire this. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PDB-644) Retire node-ttl-days
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-644 Retire node-ttl-days Change By: Kenneth Barber Fix Version/s: 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Rob Reynolds commented on an issue Re: Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Have you verified that this does work as expected with only .net 2.0? I'm under the impression (possibly mistaken) that it requires 3.5. Add Comment Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed With Windows 2012, installing the puppet MSI (3.5.0-rc1 in this case) and then trying to run the Run Facter or Run Puppet Agent commands from the Start Menu will result in an error that it needs the .NET Framework version 3.5 in order to run and it cannot install it. However Start Command Prompt With Puppet works without issue. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2302) New evaluator does not properly handle resource defaults
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2302 New evaluator does not properly handle resource defaults Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Joshua Cooper commented on an issue
Re: ACL module permissions are not formatted correctly
If format_value_for_display is only being used for the permissions property, we should be able to use bare words for other parameters/properties like?
ensure = present,
inherit_parent_permissions = false,
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Kenneth Barber commented on an issue Re: Support trusted facts in PuppetDB fact storage The fact that it may not currently work this way notwithstanding, is there any reason why this couldn't be included in the request object handed to the facts terminus during #save? Deepak Giridharagopal I think this is a reasonable way to go about it. Add Comment PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PDB-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Kenneth Barber commented on an issue Re: Support trusted facts in PuppetDB fact storage I've raised PUP-2429 to track the changes required in Puppet core. Add Comment PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title Kenneth Barber created an issue Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) Issue Type: Improvement Assignee: Unassigned Created: 02/May/14 8:28 AM Priority: Normal Reporter: Kenneth Barber PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object supplied to the Fact terminus, so the PuppetDB terminus can receive it and submit it with the 'replace facts' command submission. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-309) Update Schema config conversion logic for 2.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-309 Update Schema config conversion logic for 2.0 Change By: Kenneth Barber Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-143) puppetdb-ssl-setup script uses `puppet master configprint`
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-143 puppetdb-ssl-setup script uses `puppet master configprint` Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-571) Schematize resources/edges in catalogs.clj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-571 Schematize resources/edges in catalogs.clj Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-310) Prismatic Schema: Separate configuration conversion code into it's own library
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-310 Prismatic Schema: Separate configuration conversion code into it's own library Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-561) Rename name to certname in nodes endpoint
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-561 Rename name to certname in nodes endpoint Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-16) Store status for reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-16 Store status for reports Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x Change By: Kylo Ginsberg Assignee: KyloGinsberg BrananPurvine-Riley Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x Branan Purvine-Riley I assigned to you so that you can give (what I hope will be) the thumbs-up wrt PE CI. Thanks! Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-16) Store status for reports
Title: Message Title Kenneth Barber assigned an issue to Ryan Senior PuppetDB / PDB-16 Store status for reports Change By: Kenneth Barber Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-47) Expose puppet environment in storage and querying
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-47 Expose puppet environment in storage and querying Change By: Kenneth Barber Epic Status: ToDo Done Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-645) API Inconsistences
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-645 API Inconsistences Issue Type: Epic Assignee: Unassigned Created: 02/May/14 9:21 AM Priority: Normal Reporter: Kenneth Barber This epic covers tickets that apply to API inconsistencies - that is, bugs that relate to the API (and code that drives it) being inconsistent with other end-points and related behaviours. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-645) API Inconsistences
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-645 API Inconsistences Change By: Kenneth Barber Epic Name: PDBAPI /Query Inconsistencies Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-247) Support netmask fact on AIX
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-247 Support netmask fact on AIX Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2317) Future parser does not error on import statements
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2317 Future parser does not error on import statements Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-646) SSL Setup Improvements
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-646 SSL Setup Improvements Issue Type: Epic Assignee: Unassigned Created: 02/May/14 9:43 AM Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files Change By: Kenneth Barber Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-561) Rename name to certname in nodes endpoint
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-561 Rename name to certname in nodes endpoint Change By: Kenneth Barber Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
From what I understand it is being used for all - that's how the formatter works. Or am I missing something?
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-451) Versions for routes should be handled in a single place
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-451 Versions for routes should be handled in a single place Change By: Kenneth Barber Fix Version/s: 2.1.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1547) PR (2311) Undefined method `groups' for nil:NilClass
Title: Message Title
R Tyler commented on an issue
Re: PR (2311) Undefined method `groups' for nil:NilClass
Was there a work-around you discovered to make it possible to continue using rspec-puppet sanely until this fix is in a publicly available Puppet release?
Add Comment
Puppet / PUP-1547
PR (2311) Undefined method `groups' for nil:NilClass
Lost quite some time in a rspec-puppet issue due to this error Ultimately it was due to being on os x and setting {{operatingsystem}} fact to centos, making puppet unable to find providers for the user type. {code} NoMethodError: undefined method `groups' for nil:NilClass # /Users/csanchez/.rvm/gems/ruby-1.9.3-p484/gems/puppet-3.4
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
But perhaps we should check it against something else to see how it behaves differently.
puppet resource group
group { 'Performance Monitor Users':
ensure = 'present',
gid= 'S-1-5-32-558',
}
group { 'Power Users':
ensure = 'present',
gid= 'S-1-5-32-547',
}
group { 'Remote Desktop Users':
ensure = 'present',
gid= 'S-1-5-32-555',
}
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received
Jira (PUP-1547) PR (2311) Undefined method `groups' for nil:NilClass
Title: Message Title
Carlos Sanchez commented on an issue
Re: PR (2311) Undefined method `groups' for nil:NilClass
yes, mocking some methods, https://github.com/maestrodev/maestro-puppet-example/blob/master/spec/spec_helper.rb#L19
Add Comment
Puppet / PUP-1547
PR (2311) Undefined method `groups' for nil:NilClass
Lost quite some time in a rspec-puppet issue due to this error Ultimately it was due to being on os x and setting {{operatingsystem}} fact to centos, making puppet unable to find providers for the user type. {code} NoMethodError: undefined method `groups' for nil:NilClass # /Users/csanchez/.rvm/gems/ruby-1.9.3-p484/gems/puppet-3.4
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-247) Support netmask fact on AIX
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-247 Support netmask fact on AIX Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
Joshua Cooper I think I see some confusion here. We've overridden format_value_for_display in the permissions property so we can control how permissions look during the application of catalog changes. We have absolutely NO control of how it is formatted from puppet resource acl OTHER than making it appear as a hash or an array. It completely ignores our overrides and uses the one at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/resource.rb#L300 which calls directly to the default Puppet::Parameter.format_value_for_display for every parameter/property. Even if we override those in each of the properties, it will completely ignore those (as it is already doing based on the call in resource.rb).
Another note on that, we can control how it looks, but we'd be monkey patching puppet and the maintainability of that would be very low.
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Joshua Cooper commented on an issue
Re: ACL module permissions are not formatted correctly
Ah, I see Rob Reynolds, thanks for clearing that up. I'm +1
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2430) Testing
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2430 Testing Issue Type: Bug Assignee: Unassigned Created: 02/May/14 10:24 AM Priority: Normal Reporter: Joshua Cooper testing Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an
Jira (PUP-1892) PR (2420) Puppet remote fileserver facility for file resources.
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1892 PR (2420) Puppet remote fileserver facility for file resources. Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title Kyle Smith commented on an issue Re: incorrect header check using Ruby 2.1.0 I work with Marc Seeger, and just got this to happen with --trace: Wrapped exception: incorrect header check /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/network/http/compression.rb:69:in `inflate' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/network/http/compression.rb:69:in `uncompress' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:221:in `block (3 levels) in chunk_file_from_source' /usr/local/lib/ruby/2.1.0/net/protocol.rb:407:in `call_block' /usr/local/lib/ruby/2.1.0/net/protocol.rb:398:in `' /usr/local/lib/ruby/2.1.0/net/http/response.rb:369:in `block (2 levels) in inflate_adapter' /usr/local/lib/ruby/2.1.0/net/http/response.rb:368:in `inflate' /usr/local/lib/ruby/2.1.0/net/http/response.rb:368:in `block in inflate_adapter' /usr/local/lib/ruby/2.1.0/net/protocol.rb:407:in `call_block' /usr/local/lib/ruby/2.1.0/net/protocol.rb:398:in `' /usr/local/lib/ruby/2.1.0/net/protocol.rb:106:in `read' /usr/local/lib/ruby/2.1.0/net/http/response.rb:390:in `read' /usr/local/lib/ruby/2.1.0/net/http/response.rb:284:in `block in read_body_0' /usr/local/lib/ruby/2.1.0/net/http/response.rb:260:in `inflater' /usr/local/lib/ruby/2.1.0/net/http/response.rb:274:in `read_body_0' /usr/local/lib/ruby/2.1.0/net/http/response.rb:201:in `read_body' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:221:in `block (2 levels) in chunk_file_from_source' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/network/http/compression.rb:43:in `uncompress' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:221:in `block in chunk_file_from_source' /usr/local/lib/ruby/2.1.0/net/http.rb:1415:in `block (2 levels) in transport_request' /usr/local/lib/ruby/2.1.0/net/http/response.rb:162:in `reading_body' /usr/local/lib/ruby/2.1.0/net/http.rb:1414:in `block in transport_request' /usr/local/lib/ruby/2.1.0/net/http.rb:1405:in `catch' /usr/local/lib/ruby/2.1.0/net/http.rb:1405:in `transport_request' /usr/local/lib/ruby/2.1.0/net/http.rb:1378:in `request' /usr/local/lib/ruby/2.1.0/net/http.rb:1371:in `block in request' /usr/local/lib/ruby/2.1.0/net/http.rb:853:in `start' /usr/local/lib/ruby/2.1.0/net/http.rb:1369:in `request' /usr/local/lib/ruby/2.1.0/net/http.rb:1280:in `request_get' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/network/http/connection.rb:128:in `request_get' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:213:in `block in get_from_source' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/indirector/request.rb:258:in `do_request' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:211:in `get_from_source' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:219:in `chunk_file_from_source' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:190:in `each_chunk_from' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:169:in `block in write' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/util/checksums.rb:51:in `md5_stream' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/checksum.rb:30:in `sum_stream' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file/content.rb:168:in `write' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file.rb:854:in `write_content' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/type/file.rb:758:in `block in write' /usr/local/lib/ruby/gems/2.1.0/gems/puppet-3.5.1/lib/puppet/util.rb:429:in `replace_file'
Jira (PDB-16) Store status for reports
Title: Message Title Verne Lindner commented on an issue Re: Store status for reports stack72 If you can share it, would you briefly describe what action it's blocking for you? I'm from the PL User Experience team. We are looking at reporting improvements; your feedback would be especially useful now. Add Comment PuppetDB / PDB-16 Store status for reports We recently learned that when a puppet run fails due to catalog compilation error or catalog timeout, the agent will submit a report with a status of `failed`, but without any events. Because the current implementation of report storage in PuppetDB relies entirely on events to indicate success/failure, there is no way to look at the PuppetDB data and ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
Wheee!
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2431) PMT doesn't follow http redirects
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2431 PMT doesn't follow http redirects Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 02/May/14 10:43 AM Priority: Normal Reporter: Joshua Cooper Was trying to functional review PUP-2278, and tried to connect to HTTP forge: 1 ~/work/puppet (master) $ bundle exec puppet module install --version 4.1.0 --target-dir '/tmp/with spaces/stdlib' --module_repository 'http://forge.puppetlabs.com' --modulepath '/tmp/with spaces/stdlib' --module_working_dir '/tmp/with spaces/stdlib_working' --ignore-dependencies puppetlabs/stdlib Notice: Preparing to install into /tmp/with spaces/stdlib ... Notice: Created target directory /tmp/with spaces/stdlib Notice: Downloading from http://forge.puppetlabs.com ... Error: Could not execute operation for 'puppetlabs-stdlib' The server being queried was http://forge.puppetlabs.com/v3/releases?module=puppetlabs-stdlib The HTTP response we received was '301 Moved Permanently' I would have expected PMT to follow redirects (unless the forge isn't setting the Location header, in which case that'd be a forge issue)
Jira (PUP-2431) PMT doesn't follow http redirects
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2431 PMT doesn't follow http redirects Change By: Joshua Cooper Assignee: PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2278) puppet module install fails when given path containing spaces
Title: Message Title Joshua Cooper commented on an issue Re: puppet module install fails when given path containing spaces Verified, note that the forge service has changed, so I had to use forgeapi.puppetlabs.com and not forge.puppetlabs.com. Omitting the module_repository also works. $ git branch --contains 547af9b8208fe9a3c1657738824d55b2c4a9cf6b * master ... $ bundle exec puppet module install --version 4.1.0 --target-dir '/tmp/with spaces/stdlib' --module_repository 'https://forgeapi.puppetlabs.com' --modulepath '/tmp/with spaces/stdlib' --module_working_dir '/tmp/with spaces/stdlib_working' --ignore-dependencies puppetlabs/stdlib Notice: Preparing to install into /tmp/with spaces/stdlib ... Notice: Created target directory /tmp/with spaces/stdlib Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /tmp/with spaces/stdlib └── puppetlabs-stdlib (v4.1.0) Add Comment Puppet / PUP-2278 puppet module install fails when given path containing spaces I apologize if I haven't set this issue up correctly. First time. :) I found while using Librarian-Puppet that I couldn't install modules into paths containing spaces. I thought this was a problem with Librarian so I filed an issue there. https://github.com/rodjek/librarian-puppet/issues/201 It turns out the problem is with puppet module install. A...
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Kyle Smith commented on an issue
Re: incorrect header check using Ruby 2.1.0
Found this in compression.rb, not sure what else to look at without actually having the compressed chunk. When Puppet encounters such a failure, it tends to repeat, for what it's worth:
In some local testing an 'incorrect header check' is thrown by Zlib::Inflater#inflate passed invalid data.
def uncompress(chunk)
out = @uncompressor.inflate(chunk)
@first = false
return out
rescue Zlib::DataError
# it can happen that we receive a raw deflate stream
# which might make our inflate throw a data error.
# in this case, we try with a verbatim (no header)
# deflater.
@uncompressor = Zlib::Inflate.new
if @first then
@first = false
retry
end
raise
end
Add Comment
Puppet / PUP-1680
incorrect header check using Ruby 2.1.0
I haven't found anything out there so far, so I thought I'd just document it while I'm at it. We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related. So far we haven't been able to fix it. {code} Error: incorrect header check Error: /Stage[main]/...
Jira (PUP-2093) PMT should use the Forge's /v3 API
Title: Message Title Joshua Cooper commented on an issue Re: PMT should use the Forge's /v3 API Merge commit was 3f0e88d Add Comment Puppet / PUP-2093 PMT should use the Forge's /v3 API The PMT has been using an outdated, obsolete, and unscalable API for some time now. In an effort to deprecate those legacy APIs, we should update the PMT to use the more sustainable /v3 API. One side-effect of this change is that we will be forced to handle all dependency resolution in the PMT (since the server-side dependency resolution was not susta... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2093) PMT should use the Forge's /v3 API
Title: Message Title Joshua Cooper commented on an issue Re: PMT should use the Forge's /v3 API $ git branch --contains 3f0e88d * master $ bundle exec puppet module search registry Notice: Searching https://forgeapi.puppetlabs.com ... NAME DESCRIPTION AUTHORKEYWORDS puppetlabs-registry This module provides a native type and provider to manage keys an... @puppetlabs windows type registry win32 Add Comment Puppet / PUP-2093 PMT should use the Forge's /v3 API The PMT has been using an outdated, obsolete, and unscalable API for some time now. In an effort to deprecate those legacy APIs, we should update the PMT to use the more sustainable /v3 API. One side-effect of this change is that we will be forced to handle all dependency resolution in the PMT (since the server-side dependency resolution was not susta... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PUP-2285) Update PMT generate's README template
Title: Message Title Joshua Cooper commented on an issue Re: Update PMT generate's README template $ git branch --contains 19c087717dd8fbea781d54adc902ed67580afc2a * master ... $ bundle exec puppet module generate foo-bar ... Notice: Generating module at /Users/josh/work/puppet/foo-bar... Notice: Populating ERB templates... Finished; module generated in foo-bar. foo-bar/manifests foo-bar/manifests/init.pp foo-bar/metadata.json foo-bar/Rakefile foo-bar/README.md foo-bar/spec foo-bar/spec/classes foo-bar/spec/classes/init_spec.rb foo-bar/spec/spec_helper.rb foo-bar/tests foo-bar/tests/init.pp Used http://www.markdownviewer.com/ to view resulting README.md looks good. Pieter van de Bruggen one minor nitpik, the README refers to http not https, (For an example, see http://forge.puppetlabs.com/puppetlabs/firewall). Add Comment Puppet / PUP-2285 Update PMT generate's README template We have a wonderful README template (found at http://docs.puppetlabs.com/puppet/latest/reference/modules_documentation.html) which we've believed was shipped in core Puppet for some time now. We should actually do the work of integrating it into the PMT's default module skeleton. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Kyle Smith commented on an issue
Re: incorrect header check using Ruby 2.1.0
This thread (http://stackoverflow.com/questions/1361892/how-to-decompress-gzip-string-in-ruby) seems to indicate that using inflate on gzip compressed data will result in an 'incorrect header check'. My master is configured with the default mod_deflate config for precise:
IfModule mod_deflate.c
# these are known to be safe with MSIE 6
AddOutputFilterByType DEFLATE text/html text/plain text/xml
# everything else may cause problems with MSIE 6
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/x-_javascript_ application/_javascript_ application/ecmascript
AddOutputFilterByType DEFLATE application/rss+xml
/IfModule
Add Comment
Puppet / PUP-1680
incorrect header check using Ruby 2.1.0
I haven't found anything out there so far, so I thought I'd just document it while I'm at it. We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related. So far we haven't been able to fix it. {code} Error: incorrect header check Error: /Stage[main]/...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title
Joshua Cooper commented on an issue
Re: `puppet module build` should create `metadata.json` instead of `Modulefile`
$ git branch --contains ede281b70275d70550d4210cc055e222fd653d28
* master
...
$ bundle exec puppet module generate foo-bar
...
Finished; module generated in foo-bar.
foo-bar/manifests
foo-bar/manifests/init.pp
foo-bar/metadata.json
foo-bar/Rakefile
foo-bar/README.md
foo-bar/spec
foo-bar/spec/classes
foo-bar/spec/classes/init_spec.rb
foo-bar/spec/spec_helper.rb
foo-bar/tests
foo-bar/tests/init.pp
So it generated metadata.json and not Modulefile:
{
name: foo-bar,
version: 0.1.0,
author: foo,
summary: It's awesome,
license: Apache 2.0,
source: https://github.com/foo/bar,
project_page: https://github.com/foo/bar,
issues_url: https://github.com/foo/bar/issues,
dependencies: [
{
name: puppetlabs-stdlib,
version_range: = 1.0.0
}
]
}
Add Comment
Puppet / PUP-1977
`puppet module build` should create `metadata.json` instead of `Modulefile`
Since we're moving away from the {{Modulefile}} as the canonical source of metadata, we should do our users the favor of no longer generating a {{Modulefile}} – instead, we should generate the {{metadata.json}} file we expect them to use.
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Joshua Cooper commented on an issue Re: `puppet module build` should use `metadata.json` as input format Pieter van de Bruggen can you provide steps to verify this change, or get someone from the module team to review? Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2284) Add a user interview for creating a metadata.json file
Title: Message Title
Joshua Cooper commented on an issue
Re: Add a user interview for creating a metadata.json file
$ git branch --contains c1e5ae1582c1270e3ce6f74bcbc5ff560b50032e
* master
...
$ bundle exec puppet module generate foo-bar
We need to create a metadata.json file for this module. Please answer the
following questions; if the question is not applicable to this module, feel free
to leave it blank.
Puppet uses Semantic Versioning (semver.org) to version modules.
What version is this module? [0.1.0]
--
Who wrote this module? [foo]
--
What license does this module code fall under? [Apache 2.0]
--
How would you describe this module in a single sentence?
-- It's awesome
Where is this module's source code repository?
-- https://github.com/foo/bar
Where can others go to learn more about this module? [https://github.com/foo/bar]
--
Where can others go to file issues about this module? [https://github.com/foo/bar/issues]
--
{
name: foo-bar,
version: 0.1.0,
author: foo,
summary: It's awesome,
license: Apache 2.0,
source: https://github.com/foo/bar,
project_page: https://github.com/foo/bar,
issues_url: https://github.com/foo/bar/issues,
dependencies: [
{
name: puppetlabs-stdlib,
version_range: = 1.0.0
}
]
}
About to generate this metadata; continue? [n/Y]
-- y
Notice: Generating module at /Users/josh/work/puppet/foo-bar...
Notice: Populating ERB templates...
Finished; module generated in foo-bar.
foo-bar/manifests
foo-bar/manifests/init.pp
foo-bar/metadata.json
foo-bar/Rakefile
foo-bar/README.md
foo-bar/spec
foo-bar/spec/classes
foo-bar/spec/classes/init_spec.rb
foo-bar/spec/spec_helper.rb
foo-bar/tests
foo-bar/tests/init.pp
Add Comment
Puppet / PUP-2284
Add a user interview for creating a metadata.json file
Jira (PDB-647) Unfork our puppet related installation helpers in our acceptance tests
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-647 Unfork our puppet related installation helpers in our acceptance tests Issue Type: Improvement Assignee: Unassigned Created: 02/May/14 10:55 AM Priority: Normal Reporter: Kenneth Barber We currently use forks of the Puppet installation helpers rather then the core ones in beaker. We should be relying on this library of knowledge and throw away our own. We have however built up assumptions around our helpers, so we'd need to tread carefully and fix any bugs found once the new helpers are introduced. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Pieter van de Bruggen commented on an issue Re: `puppet module build` should use `metadata.json` as input format puppet module build with an old (Modulefile-backed) module: you should be warned that Modulefile is deprecated, and a metadata.json file (with the same metadata) should be added to the module directory. That metadata.json file should be bundled in the tarball. puppet module build with a module containing both a Modulefile and a metadata.json: you should be warned the Modulefile is deprecated, that the tool is using the metadata.json file instead, the metadata.json file is not updated with data from the Modulefile, and that metadata.json file should be bundled in the tarball. puppet module build with only a metadata.json file: it should run without warning, and the metadata.json file should be bundled in the tarball. Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2414) Get Puppet acceptance to use the new internal forge being set up by the module team.
Title: Message Title Roger Ignazio commented on an issue Re: Get Puppet acceptance to use the new internal forge being set up by the module team. Based on discussions with Dominic Maraglia and Justin Stoller, this ticket should be moved to the QENG tracker so that it can be triaged and moved into a future QENG sprint. This way I'm not straddling two sprints every week/two weeks. Add Comment Puppet / PUP-2414 Get Puppet acceptance to use the new internal forge being set up by the module team. Currently Puppet Acceptance relies on being able to reach a testing forge instance forge-aio01-petest.puppetlabs.com. This is an external node hosted on linode, and susceptible to all the same connectivity issues which have caused us to create local rubygem, github and packaging mirrors. So a request was put in for an internal forge instance for testing... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2406) Run all acceptance jobs in parallel
Title: Message Title Roger Ignazio commented on an issue Re: Run all acceptance jobs in parallel Based on discussions with Dominic Maraglia and Justin Stoller, this ticket should be moved to the QENG tracker so that it can be triaged and moved into a future QENG sprint. This way I'm not straddling two sprints every week/two weeks. Add Comment Puppet / PUP-2406 Run all acceptance jobs in parallel Right now it takes up to 4 or 5 hours from the start of a test pipeline run to the end. We should be able to reduce this by an hour if we start the linux, solaris, and windows acceptance jobs all at the same time instead of gating the Windows and Solaris jobs on a good Linux run. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-646) SSL Setup Improvements
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-646 SSL Setup Improvements Change By: Kenneth Barber TicketsthatcoverbugsandimprovementstothewaywesetupSSL. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Joshua Cooper commented on an issue Re: puppet module generate should produce a skeleton spec test It generates a spec file, but doesn't generate a Gemfile. So if you don't have puppetlabs_spec_helper, puppet-lint, and puppet (and its dependencies) installed, the rake task blows up: $ rake spec /Users/josh/.rbenv/versions/1.9.3-p392/bin/ruby -S rspec spec/classes/init_spec.rb --color /Users/josh/.rbenv/versions/1.9.3-p392/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- puppet (LoadError) from /Users/josh/.rbenv/versions/1.9.3-p392/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' /Users/josh/.rbenv/versions/1.9.3-p392/bin/ruby -S rspec spec/classes/init_spec.rb --color failed But it still fails after manually installing necessary gems (not sure about which versions the skeleton Rakefile is expecting): $ gem install puppetlabs_spec_helper $ gem install puppet-lint $ gem install puppet $ gem install autorun $ gem install rake rspec it still fails due to require 'spec/autorun': $ rake spec ... /Users/josh/.rbenv/versions/1.9.3-p392/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:126:in `require': cannot load such file -- spec/autorun (LoadError) If I comment that require out from the spec_helper.rb, it generates deprecation warnings along with a hard NameError $ rake spec ... DEPRECATION: Spec::Runner.configure is deprecated. Use RSpec.configure instead. Called from /Users/josh/work/puppet/foo-bar/spec/spec_helper.rb:9:in `top (required)'. /Users/josh/work/puppet/foo-bar/spec/spec_helper.rb:16:in `class:Object': undefined method `should' for class `Object' (NameError) Add Comment
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title garrett honeycutt commented on an issue Re: puppet module generate should produce a skeleton spec test Looks like Thebo already merged my code for this https://github.com/puppetlabs/puppet/pull/2253 and it did not include autorun. Not sure where you are getting that from as the errors above do not reference what code you are testing with. Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title garrett honeycutt commented on an issue Re: puppet module generate should produce a skeleton spec test Do you want a PR for a Gemfile? Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Joshua Cooper commented on an issue Re: puppet module generate should produce a skeleton spec test and it did not include autorun. Not sure where you are getting that from as the errors above do not reference what code you are testing with. It's coming from the spec_helper skeleton It's also calling the deprecated method for configuring rspec Do you want a PR for a Gemfile? Yes, please open a separate ticket and PR for that. Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-476) Make the 'processor' fact for OpenBSD consistent with other systems
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-476 Make the 'processor' fact for OpenBSD consistent with other systems Issue Type: Improvement Affects Versions: 2.0.1 Assignee: Eric Sorenson Created: 02/May/14 11:54 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse Turns out 'processor = sparc64' is too terse, we already get that information via other facts so make the 'processor' fact on OpenBSD behave like other systems and return a value like SUNW,UltraSPARC-T1 (rev 0.0) @ 1000 MHz Add Comment This message was sent by
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title garrett honeycutt commented on an issue Re: puppet module generate should produce a skeleton spec test https://github.com/puppetlabs/puppet/pull/2611 Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title garrett honeycutt created an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Issue Type: Bug Affects Versions: 3.5.1 Assignee: Andy Parker Components: Modules Created: 02/May/14 11:57 AM Priority: Normal Reporter: garrett honeycutt Joshua Cooper states that we are using a deprecated method for configuring rspec Add Comment
Jira (PUP-1046) puppet module generate should produce a skeleton spec test
Title: Message Title garrett honeycutt commented on an issue Re: puppet module generate should produce a skeleton spec test sorry @josh created a new ticket PUP-2432 for this. Add Comment Puppet / PUP-1046 puppet module generate should produce a skeleton spec test # Overview # In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module. I think the example could simply add the class to the catalog and make sure it got added. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title garrett honeycutt commented on an issue Re: module skeleton is using deprecated way to configure spec_helper https://github.com/puppetlabs/puppet/pull/2612 Add Comment Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper [~josh] states that we are using a deprecated method for configuring rspec This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Trevor Vaughan commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Ok, changing hiera_interpolate in interpolate.rb to the following does what I expect: def hiera_interpolate(data, key, scope, extra_data) value = Hiera::Backend.lookup(key, nil, scope, nil, :priority) if value.is_a?(String) return data.sub(METHOD_INTERPOLATION, value) else return value end end I'm not sure about the far reaching ramifications of this, but it certainly does what I need it to do consistently. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2241) Add logging functions to static loader
Title: Message Title Henrik Lindberg commented on an issue Re: Add logging functions to static loader For review: The new functions uses formatted output. Notice [sic] the difference of executing: $a = 1,2,3] notice $a with parser=future, and when parser=current Add Comment Puppet / PUP-2241 Add logging functions to static loader The new loader system's static loader should contain the logging functions (notice, warn, etc.) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PDB-16) Store status for reports
Title: Message Title Kenneth Barber commented on an issue Re: Store status for reports Initial terminus work is here: https://github.com/kbarber/puppetdb/tree/ticket/master/pdb-16-store-report-status Add Comment PuppetDB / PDB-16 Store status for reports We recently learned that when a puppet run fails due to catalog compilation error or catalog timeout, the agent will submit a report with a status of `failed`, but without any events. Because the current implementation of report storage in PuppetDB relies entirely on events to indicate success/failure, there is no way to look at the PuppetDB data and ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Kyle Smith commented on an issue
Re: incorrect header check using Ruby 2.1.0
Just confirmed that the same 4 files threw this error both times.
The files end in .html and .txt. If Puppet is attaching a content-type based on the extension then they're probably the only files being compressed by mod_deflate.
Add Comment
Puppet / PUP-1680
incorrect header check using Ruby 2.1.0
I haven't found anything out there so far, so I thought I'd just document it while I'm at it. We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related. So far we haven't been able to fix it. {code} Error: incorrect header check Error: /Stage[main]/...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2440) Prepare long form release notes and short form release story
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2440 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment This message was
Jira (PUP-2436) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2436 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Ensure all tickets targeted at the release have a corresponding commit git log old tag..new tag This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with tasks 3 and 4 (it beats doing it manually, but requires manual steps and hacking the script for the specific release) Add Comment
Jira (PUP-2447) Update the downloads page
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2447 Update the downloads page Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2448) Send out announcements
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2448 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2442) Smoke test packages
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2442 Smoke test packages Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Procedure may vary by project and point in the release cycle. Ask around. Add a link to the Packages repository Example: Smoke test platforms: pick some platforms such as RHEL 5/6/7 CentOS 5/6 Windows 2003/2008/2012 Debian 6/7/ Ubuntu 10.04/12.04/14.04 Smoke test procedure: Start/stop/restart a master with the init scripts (on debian try the passenger master) Start/stop/restart an agent
Jira (PUP-2434) Ensure tests are passing
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2434 Ensure tests are passing Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds All tests (spec, acceptance) should be passing on all platforms for both stable master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Add Comment
Jira (PUP-2435) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2435 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Ensure all tickets referenced in the commit log have a bug targeted at the release git log old tag..new tag look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with tasks 3 and 4 (it beats doing it manually, but requires manual steps and hacking the script for the specific release) Add Comment
Jira (PUP-2443) Go/no-go meeting
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2443 Go/no-go meeting Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Should include: dev, docs, product, qa, releng Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-2445) Packages pushed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2445 Packages pushed Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2433) Puppet 3.6.0-TEST 2014-05-10 Release
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2433 Puppet 3.6.0-TEST 2014-05-10 Release Issue Type: Task Assignee: Release Engineering Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds Puppet 3.6.0-TEST 2014-05-10 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (PUP-2438) Merge master into stable
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2438 Merge master into stable Issue Type: Sub-task Assignee: Rob Reynolds Created: 02/May/14 1:15 PM Priority: Normal Reporter: Rob Reynolds git checkout stable git merge master --no-ff --log Dependencies: Ensure tests are passing Is there a commit for every JIRA ticket targeted at the release? Update version number in source Add Comment
