Jira (PUP-704) puppet facts find returns facts for wrong node
Title: Message Title Kylo Ginsberg commented on PUP-704 Re: puppet facts find returns facts for wrong node In puppet 4 we moved the inventory service and reworked the puppet facts face, the primary intended use of which is now retrieving facts from the node it's run on. For background, see: PUP-3698 PUP-3697 PUP-3700 PUP-2560 I'm going to go ahead and close this issue, given the above. If there is something remaining here, please reopen! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
Jira (PUP-3067) Windows Package provider should verify DisplayName after install
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3067 Windows Package provider should verify DisplayName after install Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3375) Filebucket Diffs on Windows
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3375 Filebucket Diffs on Windows Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title Charlie Sharpsteen commented on PUP-2695 Re: defining a class twice merges their behaviors This still exists in 4.2.1 and surprised many of us that played around with it. The ability to re-open a class in a module from a manifest in a different module is particularly surprising. Can we add this to the list of Puppet 5 deprecations? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-735) Status unchanged when Could not apply complete catalog
Title: Message Title Kylo Ginsberg commented on PUP-735 Re: Status unchanged when Could not apply complete catalog 3.x patch merged in: https://github.com/puppetlabs/puppet/commit/45f5f3757aabf48cdb63bd08994f9a9a22863f92 3.x acceptance touchup merged in: https://github.com/puppetlabs/puppet/commit/2667053d0438d650c909158c79ce85cfaee8019a Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2709) Puppet Agent: fails to run on non english Windows
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-2709 Puppet Agent: fails to run on non english Windows Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2695 defining a class twice merges their behaviors Change By: Charlie Sharpsteen CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2695 defining a class twice merges their behaviors Change By: Charlie Sharpsteen Affects Version/s: PUP4.2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Eric Thompson commented on PUP-4864 Re: Get pre-suites working for Fedora 22 and package installs should work with yum.repos.d as dnf is backwards compatible with it. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Should I bite off part of QENG-2677 and put F22 into the master Puppet pipeline as a build only target and folks can test locally the ci:test:aio target? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title
Justin Stoller commented on PUP-4864
Re: Get pre-suites working for Fedora 22
Also, you should be able to build packages for any platform locally by checking out puppet-agent and after {{bundle install}}ing run: bundle exec build puppet-agent platform where platform is the filename at (from the root of the puppet-agent repo) configs/platforms/platform.rb
NB: if the ssh key to log into pooler vms isn't part of your ssh agent then you'll need to specify VANAGON_SSH_KEY=/path/to/pooler/key
That should leave you with a local package, I know CI calls a ship and a repo command (in that order) to stage the local packages to builds.d.pl.n and create the package repositories that the acceptance tests expect, respectively. Melissa Stone Matthaus Owens would have to chime in if that's something Developers can do locally (I don't know if there'd be permissions issues). They might also know if there's a confluence page on this (I couldn't find it).
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Kylo Ginsberg commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Justin Stoller, John Duarte: given that git passed and that the aio presuite doesn't have specifics for different fedora versions, I'd suggest we just enable F22 as a build target and test target on the stable pipeline, and run it once through and see. That seems like the least work all around and pretty low risk. If it blows up and the fix isn't completely trivial, drop it from the test (or build, if appropriate) targets and ticket what we learned.. Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5009) Fix acceptance tests for fedora-22
Title: Message Title John Duarte commented on PUP-5009 Re: Fix acceptance tests for fedora-22 The only one of these failures that I don't understand is tests/config/puppet_manages_own_configuration_in_robust_manner.rb which fails due to the puppet master command exiting with a 1 rather than a 74 when the system users are not available. The command is unsuccessful, so functionally this seems to be alright. This appears to be consistent when running the tests on a git install. Running the puppet master command with the system users intact results in an exit of 0 and the /usr/bin/ruby /usr/bin/puppet master process running on the system. Joshua Partlow since the test has your name on it, can you comment on whether this should be a failure or whether a non-zero exit code should be allowed for this test. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4771) Static compiler only looks for file content in production environment
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4771 Static compiler only looks for file content in production environment Change By: Eric Thompson Assignee: qa EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1883) Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-1883 Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB Change By: Nick Walker SometimesImanagefiles(orotherresources)thatcontainpasswordsandI'dlikeawaytopreventthoseresourcesfrombeingstoredinPuppetDBtopreventaccidentalexposure.ThewayIimagineusingthisisthatI'dputaspecifictag (oranewmeta-attribute) onanyresourcesIdidn'twanttostore sayaDONOTSTOREtag .Then beforesendingtoPDBor onthePDBside,therewouldbeaconfigurablelistoftagsthatshouldnotbestoredandwhenparsingthecatalogbeforeputtingitintothedatabasetheseresourceswouldberemoved. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4633 User resource fails with UTF-8 comment on 2nd run Change By: Eric Thompson Assignee: qa EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1883) Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB
Title: Message Title Kenneth Barber commented on PDB-1883 Re: Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB Depending on the solution, PuppetDB terminus might not be the right place to do all this work. We are just consumers of data from Puppet, I would ask if it's wiser to place any implementation there instead, since the catalog report interfaces are general, and we are just 1 consumer of that. Without knowing the solution however, end-to-end I'm not sure. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4771) Static compiler only looks for file content in production environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4771 Static compiler only looks for file content in production environment Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Assessment: Medium QA Highest Test Level Reason: nospecs,fullstackrequired,agent-masterinteractionacrossenvironmentsandfilebucket QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PUP-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title Eric Thompson commented on PUP-4633 Re: User resource fails with UTF-8 comment on 2nd run validated on debian6 at master puppet-agent SHA: d1076629d62f8b556589ddeb96accaedb81db67d [root@is5g4otqaq7zkkr ~]# puppet apply bubba.pp Notice: Compiled catalog for is5g4otqaq7zkkr.delivery.puppetlabs.net in environment production in 0.36 seconds Notice: /Stage[main]/Main/User[bubba]/ensure: created Notice: Applied catalog in 0.09 seconds [root@is5g4otqaq7zkkr ~]# puppet apply bubba.pp Notice: Compiled catalog for is5g4otqaq7zkkr.delivery.puppetlabs.net in environment production in 0.36 seconds Notice: Applied catalog in 0.02 seconds [root@is5g4otqaq7zkkr ~]# grep bubba /etc/passwd bubba:x:1000:1000:™:/home/bubba:/bin/bash
Jira (PUP-5012) Add feature flag to disable authconfig
Title: Message Title Jeff McCune created an issue Puppet / PUP-5012 Add feature flag to disable authconfig Issue Type: New Feature Assignee: Unassigned Created: 2015/08/07 10:31 AM Priority: Normal Reporter: Jeff McCune In support of SERVER-111, a feature flag needs to be added to core Puppet that will disable all of the internal authconfig, aka auth.conf, behavior. This is necessary to allow the tk-authorization service to handle authentication and authorization without conflicting with Puppet's authorization system. A trivial proof of concept for this feature flag is available at: https://github.com/jeffmccune/puppet/tree/task/4.2.0/SERVER-769_auth_conf_feature_flag diff --git a/lib/puppet/defaults.rb b/lib/puppet/defaults.rb index b4165a7..db059fa 100644
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Justin Stoller commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Sounds good, I've updated stable and QENG-2677 accordingly. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title John Duarte commented on PUP-4864 Re: Get pre-suites working for Fedora 22 Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4771) Static compiler only looks for file content in production environment
Title: Message Title Eric Thompson commented on PUP-4771 Re: Static compiler only looks for file content in production environment validated on ubuntu14.04 at master puppet-agent SHA: d1076629d62f8b556589ddeb96accaedb81db67d [root@is5g4otqaq7zkkr dev]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for is5g4otqaq7zkkr.delivery.puppetlabs.net Info: Applying configuration version '1438971031' Notice: setting up filebucket puppet Notice: /Stage[main]/Main/Notify[setting up filebucket puppet]/message: defined 'message' as 'setting up filebucket puppet' Notice: production! Notice: /Stage[main]/Main/Notify[production!]/message: defined 'message' as 'production!' Notice: /Stage[main]/Main/File[/tmp/testfile01]/ensure:
Jira (PDB-1883) Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB
Title: Message Title Kenneth Barber commented on PDB-1883 Re: Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB Can you provide some non-contrived examples? Extra points for manifest code and desired outcome, perhaps how you see it displayed later in the report/catalog (or how it's not, if we're that brutal). I'm also curious about filtering on fields versus entire resources, seems to me we could preserve some data, just hide certain private fields - at least that feels like a good granularity you would want to aim for with such a solution. Otherwise you might lose the graph connectivity, which is a shame. Also, what about hiding the data, but letting the consumer know it was hidden. This feels like a good distinction for a consumer of the data later on, that is - there is just a field/resource place holder saying that this particular piece of data was sensitive, so not shown perhaps. Its a shame I can't see a good generic way of doing this implicitly, some types have fields that contain both sensitive insensitive data depending on the context - however in pure ruby resource types that are custom, this is easier (like postgresql passwords, if maintained using a pure ruby resource). This problem smells of similar problems we've had with anonymization, whereby we try to forensically sniff out sensitive data, falling back to assuming if we don't know, perhaps it's all sensitive etc. etc. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Matthaus Owens commented on PUP-4864 Re: Get pre-suites working for Fedora 22 There will almost certainly be permissions issues with ship and repo, but it won't hurt to try and see what blows up. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1883) Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB
Title: Message Title Nick Walker created an issue PuppetDB / PDB-1883 Allow Blacklisting of Resources With Certain Tags That Should Not Be Stored In PuppetDB Issue Type: New Feature Assignee: Unassigned Created: 2015/08/07 10:25 AM Labels: tcse Priority: Normal Reporter: Nick Walker Sometimes I manage files (or other resources) that contain passwords and I'd like a way to prevent those resources from being stored in PuppetDB to prevent accidental exposure. The way I imagine using this is that I'd put a specific tag on any resources I didn't want to store say a DO NOT STORE tag. Then on the PDB side, there would be a configurable list of tags that should not be stored and when parsing the catalog before putting it into the database these resources would be removed. Add Comment
Jira (PUP-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4633 User resource fails with UTF-8 comment on 2nd run Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Probability Reason: usercommentfieldonposix QA Risk Assessment: Medium QA Risk Severity Reason: puppetfails QA Risk Probability: Low QA Risk Severity: Medium QA Highest Test Level Reason: couldprobablyliveinspec/integration QA Status: Reviewed Add Comment
Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-5011 Helper methods for enumerating manifest files in environments Issue Type: New Feature Assignee: Henrik Lindberg Components: Language Created: 2015/08/07 9:14 AM Priority: Normal Reporter: Jeremy Barlow We have found that in order for Puppet Server to be able to utilize the ClassInformationService.classes_per_environment method implemented for PUP-4819 that we would ideally need to have a couple of helper methods that we could use to construct the parameter passed into classes_per_environment. Ideally, we'd like to get this in for Puppet 4.3.0. The methods would be something like: environment_manifests() This would require no arguments and when called would return back a Hash with keys being the string name of each environment and the value being an Array of fully-qualified file names of the manifest files that can be referenced by that environment. environment_manifests_for_environment(env_name) The env_name would be a string representing the name of the environment for which manifests files should be found. The return payload from this call would be an Array of fully-qualified names of manifest files that can be referenced by that environment. – For both methods above, the list of manifest
Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Jeremy Barlow commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Henrik Lindberg - please reassign this elsewhere if you don't think it fits on the Language team. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-735) Status unchanged when Could not apply complete catalog
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-735 Status unchanged when Could not apply complete catalog Change By: Kylo Ginsberg Fix Version/s: PUP3.8.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5010) Fix acceptance tests for ubuntu-1504
Title: Message Title Kylo Ginsberg commented on PUP-5010 Re: Fix acceptance tests for ubuntu-1504 I merged to master and cherry-picked to stable. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4791) Improve docs around puppet-agent's vendored gem binary
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4791 Improve docs around puppet-agent's vendored gem binary Change By: Kylo Ginsberg Summary: Improvedocsaround puppet shouldalsohaveagemsub - command agent'svendoredgembinary Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2783) Puppet cannot restart agent after upgrade to puppet 3.4.3,
Title: Message Title Kylo Ginsberg commented on PUP-2783 Re: Puppet cannot restart agent after upgrade to puppet 3.4.3, This issue slipped through the cracks, but hasn't been reported elsewhere. I'm going to close this for now, but if the issue is present in current puppet releases, please re-open! Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3064) Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3064 Prevent race condition in Windows service code from prematurely exiting win32-service Service_Main Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4791) Improve docs around puppet-agent's vendored gem binary
Title: Message Title Kylo Ginsberg assigned an issue to Mike Hall Puppet / PUP-4791 Improve docs around puppet-agent's vendored gem binary Change By: Kylo Ginsberg Assignee: KyloGinsberg MikeHall Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title John Duarte commented on PUP-4864 Re: Get pre-suites working for Fedora 22 FYI, the puppet-agent package artifact for fedora-22 at SHA 93384d696af9bd23f62541a65bbffe4fcad32779 successfully completes all of the pre-suites when triggered with the following. SHA='93384d696af9bd23f62541a65bbffe4fcad32779' CONFIG=config/nodes/fedora-22-x86_64.yaml TESTS=tests bundle exec rake ci:test:aio Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4791) Improve docs around puppet-agent's vendored gem binary
Title: Message Title Kylo Ginsberg commented on PUP-4791 Re: Improve docs around puppet-agent's vendored gem binary I renamed this ticket accordingly. Ping Mike Hall. Not sure if you'd want to move this to the docs project as well? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2783) Puppet cannot restart agent after upgrade to puppet 3.4.3,
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-2783 Puppet cannot restart agent after upgrade to puppet 3.4.3, Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title Charlie Sharpsteen assigned an issue to Unassigned Puppet / PUP-2695 defining a class twice merges their behaviors Change By: Charlie Sharpsteen Assignee: AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
