Jira (FACT-746) ipaddress fact doesn't function properly with dummy interfaces (linux)
Title: Message Title Björn Henkel created an issue Facter / FACT-746 ipaddress fact doesn't function properly with dummy interfaces (linux) Issue Type: Bug Affects Versions: FACT 2.2.0 Assignee: Eric Sorenson Created: 23/Oct/14 11:17 PM Environment: Linux, RHEL 6.5 Priority: Normal Reporter: Björn Henkel There is the old Bug #3713 that describes the issue. The ipaddress of the dummy device is returned as by the ipaddress fact, which is not what one expects. > ifconfig dummy0 Link encap:Ethernet HWaddr 36:D9:A2:FF:6D:92 inet addr:10.6.0.143 Bcast:10.6.0.255 Mask:255.255.255.0 inet6 addr: fe80::34d9:a2ff:feff:6d92/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:210 (210.0 b) eth0 Link encap:Ethernet HWaddr E4:11:5B:AB:D3:06 inet addr:192.168.102.86 Bcast:192.168.102.255 Mask:255.255.255.0 inet6 addr: fe80::e611:5bff:feab:d306/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5879523 errors:0 dropped:0 overruns:0 frame:0 TX packets:4151717 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:611191340 (582.8 MiB) TX bytes:5553146297 (5.1 GiB) lo Link encap:Local Loopback inet addr:127
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. OK, we got a new build through with a specific fix for PUP-3500 and a tweak to PUP-3244 's new acceptance test, plus all the fixes I don't have visiblity for in the rest of the pe components that are being integrated. That brought our failures down to 41 total, across 6 tests. 24 are all on redhat platforms, and are related to selinux seluser settings on the environments dir and contents of pe-puppet-dashboard dir. This type of failure began showing up (middle of?) last week, does anyone know what, perhaps module changes, might be causing this? 14 are the check_woy_cache_works.rb test that has been plaguing us, but this time it's across the board. Puppet server doesn't seem to restart after configuration changes. I'll look into this in the morning. Remaining three look to be related to SERVER-38, except one failure is coming back from a node classifier call: /classifier-api/v1/classified/nodes/j69mmigph5wx69q.delivery.puppetlabs.net. Reason: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint \"event_commits_pkey\" Detail: Key (id)=(8b2a42e83adfdd8b92e46903a3bf9aba4d540340) already exists. Dan Lidral-Porter does that look familiar to you? I failed to turn up anything in Jira for it. We've had failures within this test that we couldn't see the details of before, and I'm guessing we're getting more visibility on this thanks to you closing NC-280, so it may not be brand new. http://jenkins-enterprise.delivery.puppetlabs.net/view/Build%20Board%20-%20FOSS/job/PE%20Puppet%20Acceptance%20Tests/lastCompletedBuild/testReport/ 14 failures => tests/node/check_woy_cache_works.rb (every platform) puppet server fails to start (or, at any rate, we can't curl it with 120 attempts) 8 failures => tests/ticket_5477_master_not_dectect_sitepp.rb (every redhat platform) An agent run is seeing unexpected selinux seluser changes to reports in pe-puppet-dashboard: Notice: /File[/var/log/pe-puppet-dashboard/failed_reports/report_20141023180225.yaml]/seluser: seluser changed 'unconfined_u' to 'system_u' Notice: /File[/var/log
Jira (PUP-3527) 'puppet resource service ' falsely reports "ensure => absent"
Title: Message Title
Kylo Ginsberg commented on an issue
Re: 'puppet resource service ' falsely reports "ensure => absent"
One other note: I reproduced this as far back as 3.1.0.
Add Comment
Puppet / PUP-3527
'puppet resource service ' falsely reports "ensure => absent"
If not changing the ensure setting it reports correctly: {code} > sudo bundle exec puppet resource service com.teamviewer.service service { 'com.teamviewer.service': ensure => 'stopped', enable => 'false', } {code} But if changing the ensure attribute (maybe any attribute?) it returns incorrectly: {code} > sudo bundle exec puppet resou...
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-3527) 'puppet resource service ' falsely reports "ensure => absent"
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-3527
'puppet resource service ' falsely reports "ensure => absent"
Issue Type:
Bug
Assignee:
Unassigned
Created:
23/Oct/14 9:46 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
If not changing the ensure setting it reports correctly:
> sudo bundle exec puppet resource service com.teamviewer.service
service { 'com.teamviewer.service':
ensure => 'stopped',
enable => 'false',
}
Jira (PUP-3130) Remove "hidden" $_timestamp fact
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-3130 Remove "hidden" $_timestamp fact Change By: Josh Cooper Assignee: Josh Cooper 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-3370) Remove serialization of indirector requests
Title: Message Title Josh Cooper commented on an issue Re: Remove serialization of indirector requests Merged in 76397bf Add Comment Puppet / PUP-3370 Remove serialization of indirector requests Commit https://github.com/puppetlabs/puppet/commit/1cbe2ad7 added the ability to serialize an indirector request so that requests could be transported over mcollective. This functionality was never implemented, and never will be. We need to remove this code. 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-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title
Josh Cooper commented on an issue
Re: Regression when pluginsyncing external facts on Windows
Merged in commit 86e44a0.
Add Comment
Puppet / PUP-2907
Regression when pluginsyncing external facts on Windows
Ticket PUP-2705 restored the ability for pluginsync to preserve permissions for external facts synced to {{facts.d}}. However, on Windows, it generates a deprecation warning, which users cannot fix: {noformat} C:\work\puppet> bundle exec puppet agent -t ... Info: Retrieving pluginfacts Warning: Copying owner/mode/group from the source file on Windo...
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-3514) Future parser not showing line/column for error
Title: Message Title
Henrik Lindberg commented on an issue
Re: Future parser not showing line/column for error
This problem is the same for all errors that come from the simplistic semantic checks in the future parser. We have a different ticket (PUP-1546) about improving those error messages (the parser does not have the same nice infrastructure (yet) to use the 4x issue system and its messages can not include semantic information about the type of _expression_ etc. That will change at some point during 4x.
The implementation of the error method is simply dead wrong - it behaves like the 3x version and ends up calling to_s on an AST model that is contructed !!! as the result of invoking operations on the AST Factory!!! when it believes it is getting file, line etc. it is instead creating a program to extract those - that is the output you are seeing! Amazed that we do not have unit testing to cover those errors.
The fix of the problem is quite simple (I already have it working), but adding tests for all the corner cases is a lot more work. Will add one for the specific case though to catch a regression of the fundamental problem that the parser's error method was misbehaving.
Andy Parker do you want this targeted for 3.7.3? (I think it is pretty bad) - I did the work off stable
Add Comment
Puppet / PUP-3514
Future parser not showing line/column for error
We had a manifest that contains this: {code} File ['/etc/pam.d/sshd'] { {code} Obviously the space there is a mistake but the future parser gave me this back: {noformat} Error: Could not parse for environment production: _expression_ is not valid as a resource, resource-default, or resource-override at (slice () 'file'):(slice () 'line'):(slice ...
Jira (PUP-3524) Switch from YAML and PSON to JSON
Title: Message Title
Henrik Lindberg commented on an issue
Re: Switch from YAML and PSON to JSON
One note that I also sent out on puppet dev.
I would like us to add a Binary datatype upfront instead of doing the base64 encoding in the puppet code. Instead, it is the serialization formats responsibility to transform it into a form that can be transported. A JSON in text form can then do the base64 encoding. A MsgPack / JSON can instead use the binary directly.
Even if our first cut of this always performs a base64 encoding the user logic does not have to change.
Thus, instead of calling base64(content) and setting the encoding in the File resource, a Binary is created directly with a binary(encoding, content) function.
BTW: MsgPack is essentially binary-JSON with compression. We can easily support a msgpack/json format in addition to text/json. Where the text/json for file content is either a String or Hash, where the hash is
{ encoding => base64encodedString }
and the Msgpack is either String or a Hash with
{ encoding => MsgPackBinary }
Without any other changes, the only place we support the Binary is in File's content so that serialization/deserialization needs to be special. When we have typed parameters, the serialization is instead driven by the type.
Add Comment
Jira (PUP-3526) re-structure CA REST API
Title: Message Title Christopher Price updated an issue Puppet / PUP-3526 re-structure CA REST API Change By: Christopher Price Sprint: SERVER next sprint candidates 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-3526) re-structure CA REST API
Title: Message Title Christopher Price moved an issue Puppet / PUP-3526 re-structure CA REST API Change By: Christopher Price Component/s: Puppet Server Component/s: Puppet Server Workflow: Puppet Enterprise Platform Workflow Key: PE PUP - 4020 3526 Project: Puppet Enterprise [Internal] 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
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Henrik Lindberg commented on an issue Re: Hiera should support alternate environments Current status is that 4.0 was pushed out to end of the year, and the current plan includes providing a good way to plug in the "hiera data in modules"-module. We know that handling one hiera per environment is high on the wish list but I am uncertain if it will make it into 4.0. We have infrastructure and cleanup things that stand in the way - the system is creating way too many instances of Environment at the moment and this needs to be fixed in order to tie more things to the environment (like a hiera) - it may be that the work on wiring "hiera-data-in-modules" solves part of this problem and we may be able to support one hiera per environment because of that, but that work is not completed yet - so no promises; it may require a lot more work. Or, put differently, we know that is we do this the naive way we will create a performance problem. In 4.0 - we are also removing the non directory environments - the old environments are a blocker to allowing hiera per environment. garrett honeycutt while that was perhaps not the answer you wanted, it is the state of things - and it is not in any way forgotten. If it does not make it into 4.0, it can be done in a 4.x release as we should then have the foundation to base it on. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.
Jira (PUP-3525) Puppetmaster needs a RESTful way to flush environment caches
Title: Message Title Eric Sorenson created an issue Puppet / PUP-3525 Puppetmaster needs a RESTful way to flush environment caches Issue Type: New Feature Assignee: Unassigned Created: 23/Oct/14 5:09 PM Priority: Normal Reporter: Eric Sorenson Users are experiencing problems with changes they make to Puppet modules on the filesystem not showing up immediately, either from catalog compilation or other endpoints like ''resource_types". We're moving towards a world where the environment_timeout is really a bi-state setting: either "I'm in a constantly-changing dev environment, don't cache at all" or "I'm running in production, cache forever until I deploy new code", but we're not quite at the point where the latter use-case is done end-to-end. All of that is prelude to saying, it would be greatly helpful to have a REST action that could cause a master to expire all of its environment caches so subsequent hits for catalogs, resource_types, etc go to the filesystem. The user would knowingly incur the performance penalty because they know they're getting stale data and want it to be fresh. Add Comment
Jira (PUP-3524) Switch from YAML and PSON to JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3524 Switch from YAML and PSON to JSON Issue Type: Epic Assignee: Unassigned Created: 23/Oct/14 5:02 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker I'd like to move us away from PSON and onto a standard format. YAML is out of the question because it is either slow and unsafe (all of the YAML vulnerabilities) or extremely slow and safe (safe_yaml). MessagePack might be nice. It is pretty well specified, has a fairly large number of libraries written for it, but it doesn't do much to help us solve the wild west of encoding in puppet. In MessagePack there aren't really any enforcements of string encodings and everything is treated as an array of bytes. In order to keep consistency across various puppet projects we'll be going with JSON. JSON requires that everything is valid UTF-8, which gives us a nice deliberateness to handling data. JSON is pretty fast (not as fast as MessagePack) and there are a lot of libraries if it turns out that the built in json isn't fast enough (puppet-server could use jrjackson, for instance). Add Comment
Jira (PUP-3475) Plan transition to JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3475 Plan transition to JSON Change By: Andy Parker Security: Internal 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-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price updated an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Change By: Christopher Price Sprint: SERVER next sprint candidates 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-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price created an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Issue Type: Task Assignee: Unassigned Components: Puppet Server Created: 23/Oct/14 4:58 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Christopher Price In SERVER-22, there was a lot of discussion about environment caching and how the cached values can look different from one request to the next if they are routed to different JRuby instances / passenger workers. One of the outcomes of that discussion was the proposal that we create some kind of mechanism in Puppet Server that is akin to the passenger "graceful reload", where the JRuby instances would be killed off one at a time at some point when they were not being used to fulfill a request. This would be in support of a user workflow where someone would set the environment timeout to be infinite, and then they would need to manually trigger a reload whenever they modified a file on disk. I actually think that, since we have threads now, we can do something much smarter... e.g., have a notification that gets fired when we notice a file change on disk, and mark all of the JRuby instances stale automatically, and start flushing them out. With no user interaction. In order to do this we probably need to b
Jira (PUP-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Christopher Price updated an issue Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Change By: Christopher Price Sprint: SERVER next sprint candidates 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 (PUP-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Christopher Price moved an issue Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Change By: Christopher Price Component/s: Puppet Server Component/s: Puppet Server Workflow: Puppet Enterprise Platform Workflow Issue Type: Bug Improvement Key: PE PUP - 5386 3522 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3521) puppet incorrectly swallows some errors
Title: Message Title Christopher Price updated an issue Puppet / PUP-3521 puppet incorrectly swallows some errors Change By: Christopher Price Sprint: SERVER next sprint candidates 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-3521) puppet incorrectly swallows some errors
Title: Message Title Christopher Price moved an issue Puppet / PUP-3521 puppet incorrectly swallows some errors Change By: Christopher Price Component/s: Puppet Server Component/s: Puppet Server Workflow: Puppet Enterprise Platform Workflow Key: PE PUP - 5941 3521 Project: Puppet Enterprise [Internal] 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 gr
Jira (PUP-3520) Move the Puppet extension OIDs definitions
Title: Message Title Christopher Price updated an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Christopher Price Sprint: SERVER next sprint candidates 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-3520) Move the Puppet extension OIDs definitions
Title: Message Title Christopher Price moved an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Christopher Price Component/s: Puppet Server Component/s: Puppet Server Workflow: Puppet Enterprise Platform Workflow Issue Type: Bug Improvement Key: PE PUP - 4802 3520 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-46) Hiera should support alternate environments
Title: Message Title garrett honeycutt commented on an issue Re: Hiera should support alternate environments Puppet Labs, could you please provide a status update on this request and where it fits into your road map? Thank you! Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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-3289) Remove deprecated serialization and dynamic facts settings
Title: Message Title William Hopper updated an issue Puppet / PUP-3289 Remove deprecated serialization and dynamic facts settings Change By: William Hopper Sprint: Platform Client 2014-10-29 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-3289) Remove deprecated serialization and dynamic facts settings
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3289 Remove deprecated serialization and dynamic facts settings Change By: William Hopper Assignee: Andy Parker William Hopper 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-3519) Scope URL rework
Title: Message Title Christopher Price updated an issue Puppet / PUP-3519 Scope URL rework Change By: Christopher Price Sprint: SERVER next sprint candidates 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-3519) Scope URL rework
Title: Message Title Christopher Price created an issue Puppet / PUP-3519 Scope URL rework Issue Type: Task Assignee: Unassigned Components: Puppet Server Created: 23/Oct/14 3:15 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Adrien Thebo commented on an issue Re: Rubyize yumhelper.py to remove dependency on python Updated the parsing logic to handle wrapped entries; hopefully this will be good to go. Add Comment Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py. This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet. 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-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Adrien Thebo Sprint: Week 2014-6-4 to 2014-6-11 , Platform Client 2014-10-29 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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Britt Gresham Assignee: Britt Gresham 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-728) OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Title: Message Title Eric Thompson updated an issue Facter / FACT-728 OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x Change By: Eric Thompson QA Contact: Eric Thompson QA Status: Reviewed 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-728) OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Title: Message Title
Eric Thompson commented on an issue
Re: OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
verified on win8.1 at SHA 36d11d8 with:
C:\Windows\system32>ver
Microsoft Windows [Version 6.3.9600]
PS C:\cygwin64\bin> .\facter os
{"name"=>"windows", "family"=>"windows", "release"=>{"major"=>"8", "minor"=>"1", "full"=>"8.1"}}
Add Comment
Jira (FACT-728) OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-728 OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x Change By: Eric Thompson Assignee: Eric Thompson 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-3518) Configure facter to log using the puppet logging mechanism.
Title: Message Title Andy Parker created an issue Puppet / PUP-3518 Configure facter to log using the puppet logging mechanism. Issue Type: Improvement Assignee: Unassigned Created: 23/Oct/14 2:16 PM Priority: Normal Reporter: Andy Parker Normally facter doesn't log anything, however there are a few situations where it does and the information that it logs is very useful. One case of this is when a string is not encoded properly. Right now, if a fact returns a string that is not encoded correctly. > be puppet agent -t --certname localhost --server localhost Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts
Jira (PUP-2613) Change source_permissions default to :ignore
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Adrien Thebo Assignee: Adrien Thebo 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-2558) Remove instrumentation system
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2558 Remove instrumentation system Change By: Eric Thompson QA Contact: Erik Dasher Eric Thompson QA Status: Reviewed 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-2923) Add assumeyes attribute to yumrepo
Title: Message Title
Adrien Thebo commented on an issue
Re: Add assumeyes attribute to yumrepo
Verified in e481f76:
yumrepo { 'updates-testing-source':
ensure => 'present',
descr => 'Fedora $releasever - Test Updates Source',
enabled => '1',
failovermethod => 'priority',
gpgcheck=> '1',
gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch',
metalink=> 'https://mirrors.fedoraproject.org/metalink?repo=updates-testing-source-f$releasever&arch=$basearch',
skip_if_unavailable => 'False',
assumeyes => 1,
Jira (PUP-2923) Add assumeyes attribute to yumrepo
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2923 Add assumeyes attribute to yumrepo Change By: Adrien Thebo Assignee: Adrien Thebo 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-1062) Add virtualenv support to the pip package provider
Title: Message Title
Gene Wood updated an issue
Puppet / PUP-1062
Add virtualenv support to the pip package provider
Change By:
Gene Wood
Now that [ #6527 |https://projects.puppetlabs.com/issues/6527] is merged into master, it is possible to easily add support for virtualenvs and fully complete #3572 PUP-1088 .A ` {{ virtualenv ` }} argument could be added to the ` {{ package ` }} type in order to instrument ` {{ pip ` }} to install the requested package into the given virtualenv directory.For example: {code} package { "my-python-package": ensure => latest, provider => pip, virtualenv => "/path/to/virtualenv } {code} The content of the virtualenv parameter will be passed directly to the ` {{ --environment ` }} parameter of the ` {{ pip install ` }} commandSome references:* [ http://pypi.python.org/pypi/pip ](http://pypi.python.org/pypi/pip) * [ http://www.pip-installer.org/en/latest/index.html#using-pip-with-virtualenv ](http://www.pip-installer.org/en/latest/index.html#using-pip-with-virtualenv) * [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip.rb ](https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip.rb)
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, vis
Jira (PDB-995) PSON retirement from Puppet
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-995 PSON retirement from Puppet Change By: Kenneth Barber Sprint: PuppetDB 2014-11-19 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-995) PSON retirement from Puppet
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-995 PSON retirement from Puppet Issue Type: Bug Affects Versions: 3.0.0 Assignee: Unassigned Created: 23/Oct/14 1:48 PM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber The PSON support from Puppet 4.0 (master) has been removed, however our tests have not picked up on this. I'm going to fix the test coverage properly during my ezbake work anyway (I had already started to go down this road). We'll need to fix this bug before we release 3.0.0. The fix is most probably to just switch these calls to `#to_data_hash` instead of the pson version which utilises JSON instead I believe, but I'm not 100%. Add Comment
Jira (PUP-3517) The exec resource type should support setting the umask
Title: Message Title Eric Sorenson moved an issue Puppet / PUP-3517 The exec resource type should support setting the umask Change By: Eric Sorenson Workflow: Engineering Platform Workflow Issue Type: Story Improvement Key: ROAD PUP - 235 3517 Project: Roadmap Puppet 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-3517) The exec resource type should support setting the umask
Title: Message Title Eric Sorenson commented on an issue Re: The exec resource type should support setting the umask Moved from roadmap since this is a specific feature enhancement for Puppet. Add Comment Puppet / PUP-3517 The exec resource type should support setting the umask In meeting with State Farm, they expressed that they have to work hard to compensate for the lack of umask support in 'exec'. I can't think of a good reason not to support it, and I can think of plenty of good reasons to do so. 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-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1106 Resource refreshes don't check for failed dependencies Change By: Adrien Thebo Sprint: Platform 2014-09-17 , Platform Client 2014-10-29 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-2923) Add assumeyes attribute to yumrepo
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2923 Add assumeyes attribute to yumrepo Change By: Adrien Thebo Sprint: Platform Client 2014-10-29 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-2923) Add assumeyes attribute to yumrepo
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2923 Add assumeyes attribute to yumrepo Change By: Adrien Thebo Story Points: 1 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-2558) Remove instrumentation system
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2558 Remove instrumentation system Change By: Eric Thompson Assignee: Eric Thompson 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-3267) Remove puppet kick and related agent functionality
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3267 Remove puppet kick and related agent functionality Change By: Eric Thompson Assignee: Eric Thompson QA Contact: Erik Dasher Eric Thompson QA Status: Reviewed 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-3267) Remove puppet kick and related agent functionality
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3267 Remove puppet kick and related agent functionality Change By: Eric Thompson Assignee: Eric Thompson 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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Moses Mendoza commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Thanks Joshua Partlow. I'll follow along after and do the next steps to get it into all the builds.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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.go
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Joshua Partlow commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Moses Mendoza I'll be merging this into pe-puppet once foss stable passes
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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-bug
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Britt Gresham commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
I don't believe anyone is tasked with that yet.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Moses Mendoza commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Is someone tasked with cherry-picking this into pe-puppet? If not, I can do so.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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/puppe
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Britt Gresham commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Merged in a9bdc75
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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/op
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Britt Gresham Assignee: Britt Gresham 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-96) Deprecate 'facter --puppet'
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-96 Deprecate 'facter --puppet' Change By: Kylo Ginsberg Fix Version/s: FACT 2.3.0 Fix Version/s: FACT 2.4.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-3370) Remove serialization of indirector requests
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3370 Remove serialization of indirector requests Change By: Adrien Thebo Assignee: Andy Parker Adrien Thebo 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-3370) Remove serialization of indirector requests
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3370 Remove serialization of indirector requests Change By: Adrien Thebo Sprint: Platform Client 2014-10-29 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-477) Support for NCSA (or Apache access_log) logging in jetty
Title: Message Title Kenneth Barber commented on an issue Re: Support for NCSA (or Apache access_log) logging in jetty We're now using tk-wj9 0.9.0, so we are now able to do this whenever we are ready. Add Comment PuppetDB / PDB-477 Support for NCSA (or Apache access_log) logging in jetty It would be nice to add NCSA style logging to PuppetDB for request logs. This would help users debug queries and help with analyzing query load via logstash/splunk/webalizer and other tools like that. NCSA == apache style logging for you younger dudes. This will also need possibly logrotate changes to deal with the new log. Ref: https://wiki.ecli... 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-477) Support for NCSA (or Apache access_log) logging in jetty
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-477 Support for NCSA (or Apache access_log) logging in jetty Change By: Kenneth Barber Story Points: 3 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 (PUP-3503) yum provider calls rpm for each managed package
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: yum provider calls rpm for each managed package
Yep, that's the key. A package name like alsa-lib.i686 won't be returned by pre-fetch because the prefetch command returns %{NAME} which does not include the architecture. So, instances probably only returns a alsa-lib resource, which contains the details of whatever package happened to show up last with that name.
The list of packages, "alsa-lib.i686", "alsa-lib.x86_64", "alsa-lib", don't cause conflicts because the package resource enforces uniqueness based on title (and the name parameter, which defaults to the value of title). Since each of those resources has a different title, which rpm and yum happen to accept as a sort of alternative package name, there are no duplicate resource conflicts.
In any case, this ties into issues like PUP-1364 where we need better handling around multi-arch packages. Using a resource title like "alsa-lib.i686" just happens to work and is more of a hack than a well architected implementation.
Add Comment
Puppet / PUP-3503
yum provider calls rpm for each managed package
When managing packages with package/yum, the provider calls rpm for each package, even if nothing has changed and the provider's cache should be hot. With a handful of packages this is not really a problem, but at a client's site we have added 1200 packages, which translates into approx. three minutes runtime just for checking the current state. I'v...
This
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title AJ Roetker updated an issue Puppet / PUP-3505 Future parser handling undef's incorrectly Change By: AJ Roetker Trying to run the future parser with PE I ran in to the following errorhttps://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case.The error I got wasError: Failed to apply catalog: Parameter environment failed on Exec[/opt/staging/pe_repo/puppet-enterprise-3.4.0-rc1-1641-g71eeb3f-debian-7-amd64-agent.tar.gz]: Invalid environment setting 'production' at /opt/puppet/share/puppet/modules/pe_staging/manifests/file.pp:95Wrapped exception:Invalid environment setting 'production'Wrapped exception:Invalid environment setting 'production' Reproduction steps in PE:Install peSet parser = future in puppet.confRestart puppetserverWait 30 secrun the agent with -tdv 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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2609 Don't allow source_permissions to be set to anything other than ignore on Windows Change By: Rob Reynolds Assignee: 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 (FACT-728) OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Title: Message Title
Rob Reynolds commented on an issue
Re: OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Merged into master at 6bbe9f91a2
Add Comment
Facter / FACT-728
OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
To figure out what version of Windows we're running, we parse the kernel version string. Currently, Facter only knows what to do with versions up to 6.2. Windows 8.1 uses version 6.3.9600, which Facter doesn't know what to do with and so falls back to reporting the kernel version as the operating system release as so: {noformat} os => {"name"=>"window...
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-3201) Validation thinks that an Undef instance is of type Runtime
Title: Message Title Andy Parker updated an issue Puppet / PUP-3201 Validation thinks that an Undef instance is of type Runtime Change By: Andy Parker Flagged: Impediment 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-3227) Upgrade conflict: puppetmaster-common and puppet-common
Title: Message Title Andy Parker updated an issue Puppet / PUP-3227 Upgrade conflict: puppetmaster-common and puppet-common Change By: Andy Parker Flagged: Impediment 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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Flagged: Impediment 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-3401) Type system does not handle Pattern correctly
Title: Message Title Andy Parker updated an issue Puppet / PUP-3401 Type system does not handle Pattern correctly Change By: Andy Parker Flagged: Impediment 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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Affects Version/s: PUP 3.7.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 (PUP-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Change By: Andy Parker Flagged: Impediment 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-3268) Remove non-directory environment support
Title: Message Title
Joshua Partlow commented on an issue
Re: Remove non-directory environment support
Regarding settings, PUP-3507 discusses hooks and environment settings. Related to that, we should be able to remove the use of env in parse_config.
Add Comment
Puppet / PUP-3268
Remove non-directory environment support
Directory environments are taking over as the way to control environments in puppet. The old environment support needs to be removed. This includes removing (not an exhaustive list): * settings * many assumptions in the code about how environments are retrieved ({{Puppet::Node::Environment.new}}, etc.) * sections other than {{user}}, {{agent}},...
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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Andy Parker Flagged: Impediment 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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Andy Parker Affects Version/s: PUP 3.7.1 Affects Version/s: PUP 3.7.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 (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3505 Future parser handling undef's incorrectly Change By: Henrik Lindberg Flagged: Impediment 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-3505) Future parser handling undef's incorrectly
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3505 Future parser handling undef's incorrectly Change By: Henrik Lindberg Story Points: 1 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-3505) Future parser handling undef's incorrectly
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3505 Future parser handling undef's incorrectly Change By: Henrik Lindberg Sprint: Platform Server 2014-10-29 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-3505) Future parser handling undef's incorrectly
Title: Message Title Henrik Lindberg commented on an issue Re: Future parser handling undef's incorrectly Test and PR with fix now in place. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-3516
Puppet breaks on 32-bit Windows XP
Change By:
Daniele Sluijters
The new win32-eventlog version that Puppet is using is looking for {{Wow64DisableWow64FsRedirection}}. However, that only exists in {{kernel.dll}} on Windows XP 64bit Edition and Vista and upwards.This currently results in Puppet exploding on 'normal' Windows XP :{noformat}C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9.3-x86-mingw32/lib/ffi/library.rb:261:in `attach_function': Function 'Wow64DisableWow64FsRedirection' not found in [kernel32.dll] (FFI::NotFoundError) from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/functions.rb:42:in `' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/functions.rb:4:in `' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/windows/functions.rb:3:in `' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/eventlog.rb:3:in `require_relative' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.6.1/lib/win32/eventlog.rb:3:in `' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:60:in `require' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:60:in `rescue in require' from C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:35:in `require' from C:/Programme/Puppet Labs/Puppet/service/daemon.rb:7:in `'{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-3516 Puppet breaks on 32-bit Windows XP Issue Type: Bug Affects Versions: PUP 3.7.2, PUP 3.7.1, PUP 3.7.0 Assignee: Unassigned Created: 23/Oct/14 9:01 AM Labels: windows Priority: Critical Reporter: Daniele Sluijters The new win32-eventlog version that Puppet is using is looking for Wow64DisableWow64FsRedirection. However, that only exists in kernel.dll on Windows XP 64bit Edition and Vista and upwards. This currently results in Puppet exploding: C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9.3-x86-mingw32/lib/ffi/library.rb:261:in `attach_function': Function 'Wow64DisableWow64FsRedirection' not found in [kernel32.dll] (FFI::NotFoundError)
Jira (PUP-3515) see if acceptance can run on a solaris10 master
Title: Message Title Eric Thompson created an issue Puppet / PUP-3515 see if acceptance can run on a solaris10 master Issue Type: Bug Assignee: Andy Parker Components: Server Created: 23/Oct/14 8:43 AM Priority: Minor Reporter: Eric Thompson 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...@googleg
Jira (FACT-727) Provide meaningful operating system fact values for Arista EOS
Title: Message Title Josh Cooper updated an issue Facter / FACT-727 Provide meaningful operating system fact values for Arista EOS Change By: Josh Cooper Story Points: 1 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-728) OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x
Title: Message Title Josh Cooper updated an issue Facter / FACT-728 OS release values not correctly reported for Windows kernel versions 6.3.x or 6.4.x Change By: Josh Cooper Story Points: 1 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-2782) Yumrepo target attribute does not work
Title: Message Title
Tim Meusel commented on an issue
Re: Yumrepo target attribute does not work
this is maybe related, the following doesn't provide a valid manifest with a target attribute:
# puppet resource yumrepo puppetlabs-products
yumrepo { 'puppetlabs-products':
ensure => 'present',
baseurl => 'http://yum.puppetlabs.com/el/7/products/$basearch',
descr=> 'Puppet Labs Products El 7 - $basearch',
enabled => '1',
gpgcheck => '1',
gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs',
priority => '2',
}
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title
Daniele Sluijters created an issue
Puppet / PUP-3514
Future parser not showing line/column for error
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Henrik Lindberg
Created:
23/Oct/14 6:05 AM
Priority:
Normal
Reporter:
Daniele Sluijters
We had a manifest that contains this:
File ['/etc/pam.d/sshd'] {
Obviously the space there is a mistake but the future parser gave me this back:
Error: Could not parse for environment production: _expression_ is not valid as a resource, resource-default, or resource-override at (slice () 'file'):(slice () 'line'):(slice ([] '/etc/pam.d/sshd') 'pos')
Jira (PUP-3513) Puppet failing to autoload provider
Title: Message Title Adam Scarborough updated an issue Puppet / PUP-3513 Puppet failing to autoload provider Change By: Adam Scarborough Priority: Normal Major 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-3513) Puppet failing to autoload provider
Title: Message Title Adam Scarborough created an issue Puppet / PUP-3513 Puppet failing to autoload provider Issue Type: Bug Affects Versions: PUP 3.7.2, PUP 3.7.1, PUP 3.6.2 Assignee: Unassigned Created: 23/Oct/14 3:09 AM Environment: puppet 3.7.1, ubuntu 12.04, ruby 1.8.7 Priority: Normal Reporter: Adam Scarborough Receiving the following error: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/domain: Could not autoload puppet/provider/domain/asadmin: no such file to load – puppet/provider/asadmin on node when attempting to pull from master: the providers exists in: /puppet/modules/glassfish/lib/puppet/provider/asadmin.rb /puppet/modules/glassfish/lib/puppet/provider/domain/asadmin.rb Both of these can be verified to have been pluginsynced to the node: /var/lib/puppet/lib/puppet/provider/asadmin.rb /var/lib/puppet/lib/puppet/provider/domain/asadmin.rb so i'm slightly confused as to how these can be pluginsynced yet the master cannot find them and throws a 400?
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title
Tim Meusel commented on an issue
Re: Yumrepo target attribute does not work
Same issue here on Puppet 3.7.1 and 3.7.2:
yumrepo{'puppetrepo-products':
name => 'puppetrepo-products',
descr => 'Puppet Labs Products El 7 - $basearch',
ensure=> 'present',
baseurl => 'http://myownmirror',
gpgkey=> 'http://myownmirror',
enabled => '1',
gpgcheck => '1',
target=> '/etc/yum.repo.d/puppetlabs.repo',
}
yumrepo{'puppetrepo-deps':
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Tim Meusel updated an issue Puppet / PUP-2782 Yumrepo target attribute does not work Change By: Tim Meusel Affects Version/s: PUP 3.7.1 Affects Version/s: PUP 3.7.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 (PUP-3417) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Rob Reynolds, yes, the smoke test list could be made more clear that other than windows/osx/solaris, smoke testing the other platforms would most likely be to test gem or tar, if you wanted to test that. Actually solaris would presumably be a tar. Add Comment Puppet / PUP-3417 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be li... 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, v
