Jira (PUP-2719) Windows mount provider (smb/cifs)
Title: Message Title
Paul Ttterman commented on an issue
Re: Windows mount provider (smb/cifs)
The implementation is in the attachment.
Sample usage is something like:
mapped_drive { 'I:' ensure = present, remote = '\\server\share', }
Doesn't seem to support username and password. I don't have the need or time to fix that. If I were to do this again, I would go with the powershell module: https://forge.puppetlabs.com/puppetlabs/powershell
Add Comment
Puppet / PUP-2719
Windows mount provider (smb/cifs)
Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop
Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a ca revoke
Title: Message Title Geoff Williams commented on an issue Re: puppet (enterprise) doesn't restart web server after doing a ca revoke spec tests ~line 90 ./spec/unit/indirector/ssl_file_spec.rb Add Comment Puppet / PUP-2939 puppet (enterprise) doesn't restart web server after doing a ca revoke Very very occasionally someone will have an emergency and need to revoke a certificate with puppet ca revoke. On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack. In today's last ever puppet advanced course we taught students to restart apache after doing a revoke -- lets make their lives easie... 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Nicholas Albion commented on an issue Re: Windows mount provider (smb/cifs) The provider implementation is attached, but I did not find the type implementation - I suppose it would be trivial... Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. 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-2931) Puppet CA sometimes resets certificate serial counter
Title: Message Title Mihkel Ader commented on an issue Re: Puppet CA sometimes resets certificate serial counter Looking at the Puppet source code, it is pretty obvious why this happens. The serial file is opened using exclusive_open(), which uses flock, which does not work reliably on NFS. And later on the serial file is truncated, rewound and then rewritten, leaving a window where another process can read the serial file as empty and defaults to 1 as the next serial. Suggestions: 1. Use a more robust locking mechanism 2. Perform some sanity tests before defaulting to 1 as the next serial Add Comment Puppet / PUP-2931 Puppet CA sometimes resets certificate serial counter We are running our Puppet masters on CentOS 6 with Passenger and stock Apache. Puppet CA's data files reside on NFS storage. Autosigning is turned on. Sometimes the serials of issued client certificates reset to 0x0001 with serious consequences - when someone revokes the duplicate 0x0001 client's certificate, the CA revokes its own cert too. Revoking ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2940) Installing and using puppet with Centos7
Title: Message Title Mark Bell created an issue Puppet / PUP-2940 Installing and using puppet with Centos7 Issue Type: Bug Affects Versions: 3.6.2, 3.6.0, 3.5.0 Assignee: Andy Parker Components: Server Created: 16/Jul/14 2:17 AM Environment: RHEL7/CENTOS7 Labels: rhel7 centos7 Priority: Major Reporter: Mark Bell Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9.3 to get this far as the service would not
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Run Facter acceptance against ruby 2.0 x64
Once this is in, the jenkins job will need to be updated with a new matrix for testing and the windows2003.yaml needs to be deleted from source. https://github.com/puppetlabs/facter/blob/master/acceptance/config/nodes/windows-2003.yaml
Add Comment
Facter / FACT-569
Run Facter acceptance against ruby 2.0 x64
Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's {{install_from_git}} method accepts a {{:rev}} parameter so it should be possible to specify the revision to checkout, e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2941) Autorequire does not properly support Class resources as first-class citizens
Title: Message Title redmine.exporter created an issue Puppet / PUP-2941 Autorequire does not properly support Class resources as first-class citizens Issue Type: New Feature Assignee: Unassigned Created: 16/Jul/14 6:46 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Attempting to autorequire a class inside a custom type results in the autorequire being ignored. Since Classes are supposed to be treated as first-class resources, they should be autorequire-able like any other resource type. Add Comment
Jira (PUP-2942) puppet parser validate -
Title: Message Title Mike Rochford created an issue Puppet / PUP-2942 puppet parser validate - Issue Type: Bug Affects Versions: 3.4.2 Assignee: Kylo Ginsberg Components: Client Created: 16/Jul/14 7:32 AM Environment: operatingsystem = OracleLinux operatingsystemmajrelease = 6 operatingsystemrelease = 6.3 Priority: Normal Reporter: Mike Rochford 'puppet parser validate' does not catch miss spelling of warning. example $ cat warn_test.pp warn(Look I am a warning) $ puppet parser validate warn_test.pp $ puppet apply warn_test.pp Error: Unknown function warn at /tmp/warn_test.pp:1 on node hostname Error: Unknown function warn at /tmp/warn_test.pp:1 on node hostname $ /example
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Ethan Brown commented on an issue Re: Remove windows-pr gem as a Windows dependency FYI Rob Reynolds you missed merging the 2 corresponding PRs for puppet-win32-ruby #41 and #42... so I've moved this back to 'ready for merge'. It's also OK at this time to merge in the changes for PUP-2881, which are PRs #47 and #48. Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1214) File resources: Make source/content parameters and the file/template functions consistent.
Title: Message Title
Mansab Uppal commented on an issue
Re: File resources: Make source/content parameters and the file/template functions consistent.
It would be nice to have the relative path enabled for file function as-well to pickup the value using content attribute (just like template). I have been searching around but did not find any satisfying solution.
I have been trying to do something like this:
Replace this:
content = template('module_name/dummy_folder/template.conf.erb'),
with:
content = file('module_name/dummy_folder/file.conf'),
Add Comment
Puppet / PUP-1214
File resources: Make source/content parameters and the file/template functions consistent.
We have four main ways we can specify file content in a file resource. 1. The source parameter 2. The content parameter 3. The file function 4. The template function These behave inconsistently in the following ways. The source parameter, file function and template function all can take an array. For source/file, the first file that exists wil...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title
Markus Schuster commented on an issue
Re: Not possible to manage SELinux file contexts via puppet in a sane way
Thank you for your hint! Your module is a much nicer way to manage SELinux file contexts - unfortunately it doesn't really solve my issue as it only calls semanage itself but that file context rule cache stays.
I've modified my setest.pp a bit:
setest.pp
file { '/srv/setest-before':
ensure = directory,
}
- selinux_fcontext { 'setest':
ensure = 'present',
filespec = '/srv/setest[^/]*',
seltype = 'home_root_t',
}
- file { '/srv/setest-after':
ensure = directory,
}
Run it...
puppet apply --modulepath=/root/modules setest.pp
And unfortunately the exact same behavior as before:
# ls -lZ /srv/
drwxr-xr-x. root root system_u:object_r:var_t:s0 setest-after
drwxr-xr-x. root root system_u:object_r:var_t:s0 setest-before
Add Comment
Puppet / PUP-2169
Not possible to manage SELinux file contexts via puppet in a sane way
There's currently
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Markus Schuster updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Markus Schuster Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-708) Storage for structured facts
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenn Hussey Sprint: 20140702to20140716 ,20140716to20140730 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-745) Structured facts: dangling reference cleanup jobs
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-745 Structured facts: dangling reference cleanup jobs Change By: Kenn Hussey Sprint: 20140702to20140716 ,20140716to20140730 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-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval Change By: Kenn Hussey Sprint: 20140702to20140716 ,20140716to20140730 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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) Merged into puppet-win32-ruby 1.9.3-x86 at 376ce99. Merged into puppet-win32-ruby 2.0.0-x64 at 2cc2d9e. Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. 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-50) Query support for structured facts for /facts - exact matches
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-50 Query support for structured facts for /facts - exact matches Change By: Kenn Hussey Sprint: 20140716to 20140730 to20140813 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-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Rob Reynolds commented on an issue Re: Remove windows-pr gem as a Windows dependency Merged puppet-win32-ruby 2.0.0-x64 at af98991d Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... 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-2757) Apply parses everything twice
Title: Message Title
Joshua Partlow commented on an issue
Re: Apply parses everything twice
Merged to master in a50a64b
Add Comment
Puppet / PUP-2757
Apply parses everything twice
When the runtime creates {{Puppet::Resource}} instances, an attempt is made to lookup its type. This means that code will attempt to lookup the type in {{known_resource_types}}. If {{known_resource_type}} is nil, the runtime will issue a call to {{initial_import}} which is the starting point of parsing and evaluating code. The {{Puppet::Resource#envron...
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-2824) Make $title and $name Reserved Words
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2824 Make $title and $name Reserved Words Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2526) puppet agent retry failed http requests
Title: Message Title Andy Parker updated an issue Puppet / PUP-2526 puppet agent retry failed http requests Change By: Andy Parker Component/s: Community 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-2824) Make $title and $name Reserved Words
Title: Message Title
Joshua Partlow commented on an issue
Re: Make $title and $name Reserved Words
Merged to master in 570bc41
Add Comment
Puppet / PUP-2824
Make $title and $name Reserved Words
If one creates a class with {{$name}} or {{$title}} in it and assigns them default values, if a user later tries to instantiate this class using the default values, Puppet will generate an error. Consider the following: The setup: {code} # manifests/init.pp class pup514 { define bark(String $name = 'No Name', Integer $phone = 0) { notice N...
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-2526) puppet agent retry failed http requests
Title: Message Title Andy Parker assigned an issue to Peter Drake As commented in the pull request. I'd like some more information about the exact failures that are being seen that this issue is supposed to resolve. Ideally this would be output from puppet or information about the actual network requests that were done. Puppet / PUP-2526 puppet agent retry failed http requests Change By: Andy Parker Assignee: PeterDrake 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-2860) Optimize startup of puppet apply (future parser)
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2860 Optimize startup of puppet apply (future parser) Change By: Joshua Partlow Assignee: JoshuaPartlow 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-1244) Yum provider using version-release to validate installation.
Title: Message Title Andy Parker updated an issue Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Andy Parker Component/s: Community 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-1244) Yum provider using version-release to validate installation.
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Andy Parker Assignee: JasonAntman AndyParker 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-2940) Installing and using puppet with Centos7
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2940 Installing and using puppet with Centos7 Change By: Charlie Sharpsteen Assignee: AndyParker MarkBell 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-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Andy Parker assigned an issue to Josh Cooper Josh Cooper is going to try out the current MSI and confirm that this is no longer a problem. Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state Change By: Andy Parker Assignee: EricSorenson JoshCooper 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-617) Facter README.md should express semver/support
Title: Message Title Adrien Thebo updated an issue Facter / FACT-617 Facter README.md should express semver/support Change By: Adrien Thebo Component/s: Community 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-617) Facter README.md should express semver/support
Title: Message Title Andy Parker commented on an issue Re: Facter README.md should express semver/support There were some small comments on the PR, but nothing that should block it going it. Merged into master in 9cdb526. Add Comment Facter / FACT-617 Facter README.md should express semver/support The puppet readme (https://github.com/puppetlabs/puppet/blob/master/README.md) explains the maintenance we have for versions of puppet and that it is semantically versioned. We recently encountered an issue with Facter where users were surprised that we did not ship a security release for a previous major version of facter. The previous assumption may hav... 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-2940) Installing and using puppet with Centos7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with Centos7 Puppet is working out of the box for me on CentOS 7. However, your error looks very similar to parts of PUP-2164 , specifically my summary comment. After yum install ruby but prior to installing RVM, did you run gem update --system or apply the puppetlabs/ruby module? Add Comment Puppet / PUP-2940 Installing and using puppet with Centos7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an
Jira (PUP-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Andy Parker updated an issue Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state Change By: Andy Parker Component/s: Community 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 (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title Adrien Thebo updated an issue Hiera / HI-257 Dynamic hierarchy based on fact/variable Change By: Adrien Thebo Component/s: Community 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 (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title Andy Parker assigned an issue to Andy Parker Hiera / HI-257 Dynamic hierarchy based on fact/variable Change By: Andy Parker Assignee: AndyParker 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 (HI-279) Hiera README.md should express semver
Title: Message Title Andy Parker updated an issue Hiera / HI-279 Hiera README.md should express semver Change By: Andy Parker Fix Version/s: 1.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 (HI-279) Hiera README.md should express semver
Title: Message Title Andy Parker commented on an issue Re: Hiera README.md should express semver Merged into master in 60f9d2d4 Add Comment Hiera / HI-279 Hiera README.md should express semver The puppet readme (https://github.com/puppetlabs/puppet/blob/master/README.md) explains the maintenance we have for versions of puppet and that it is semantically versioned. We recently encountered an issue with Facter where users were surprised that we did not ship a security release for a previous major version of facter. The previous assumption may hav... 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Anderson Mills assigned an issue to Anderson Mills Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Anderson Mills Assignee: AndersonMills 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-2943) Add --ignore-changes to PMT for upgrade and uninstall
Title: Message Title Brandon High created an issue Puppet / PUP-2943 Add --ignore-changes to PMT for upgrade and uninstall Issue Type: Task Assignee: Brandon High Components: PMT Created: 16/Jul/14 11:33 AM Priority: Normal Reporter: Brandon High 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
Jira (PUP-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Josh Cooper commented on an issue Re: Puppet Agent windows services accidentally comes of out Paused state Merged in commit 75e4c86 to be released in 3.7.0. Add Comment Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state The Windows Puppet Agent service will not stay in a paused stated, instead it will go back into a running state after a short period of time. This is an issue in the Win32-Service ruby code. Raised bug https://github.com/djberg96/win32-service/issues/11 and is fixed in version 0.8.3. Because the Pause feature is so rarely used, there is no point in... 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-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state Change By: Josh Cooper Fix Version/s: 3.7.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-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Josh Cooper commented on an issue Re: Puppet Agent windows services accidentally comes of out Paused state To verify this bug: 1. install puppet from an MSI 2. make sure the service has started, e.g. net start puppet 3. pause the service: sc pause puppet 4. interrogate the service: sc interrogate puppet 5. make sure the service stays paused: sc query puppet, and it should report: C:\Windows\system32sc query puppet SERVICE_NAME: puppet TYPE : 10 WIN32_OWN_PROCESS STATE : 7 PAUSED (STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN) 6. Wait awhile (like 15 mins) and ensure the service remains paused 7. Launch the event viewer, and make sure the Application event log reports Service pausing. and no longer mentions PUP-1471. Add Comment Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state The Windows Puppet Agent service will not stay in a paused stated, instead it will go back into a running state after a short period of time. This is an issue in the Win32-Service ruby code. Raised bug https://github.com/djberg96/win32-service/issues/11 and is fixed in version 0.8.3. Because the Pause feature is so rarely used, there is no point in...
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Andy Parker updated an issue Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. Change By: Andy Parker Component/s: Community 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 (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Andy Parker commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Trevor Vaughan, we've closed out the PR because it had several issues in the way the feature was implemented. The PR comments have more details. I'm going to leave this ticket open because the request is still valid. If work continues, please tie it back to this ticket as well. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Brett Lentz commented on an issue Re: Not possible to manage SELinux file contexts via puppet in a sane way That's correct. semanage doesn't change the filesystem, but it should affect new files after the regex is in place. There might be a race condition that's causing the setest-after to not get the new context. I'll look into that. However, there's a second issue that once the fcontext applies, we still need to do a 'restorecon' on the path to reset the labels on objects created before the new regex is in place. I'm uncertain if the module should run restorecon automatically in all cases, but I can look at adding it as an option. It might also help mitigate the above mentioned race condition. Add Comment Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way There's currently no sane way to manage SELinux file contexts using puppet. The only way is to call 'semanage' via a 'exec' resource. But then the next issue comes up: Puppet seems to keep some file context rule cache, built once at startup. I wasn't able to find a way to invalidate this cache without restarting the whole puppet agent. Even when calling '... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2933) Could not parse for environment testing: Illegal fully qualified name in file
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2933
Could not parse for environment testing: Illegal fully qualified name in file
Change By:
Charlie Sharpsteen
I'mgettingrror400onSERVER:Couldnotparseforenvironmenttesting:Illegalfullyqualifiednameinfile/etc/puppet/manifests/site.ppatline10:28onnodeucla-ws-xx1.xx..xxxPuppetisnotproperlyparsingincludemodule::class--Logs--nfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d_authjsondump.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbDebug:Failedtoloadlibrary'msgpack'forfeature'msgpack'Debug:Puppet::Network::Format[msgpack]:featuremsgpackismissingDebug:catalogsupportsformats:psondotyamlb64_zlib_yamlrawError:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:Couldnotparseforenvironmenttesting:Illegalfullyqualifiednameinfile/etc/puppet/manifests/site.ppatline10:28onnode-ws-t01.xx..eduWarning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrunAndhereismydefault.pp.Line10ismcollective-agents::facts{ quote code }nodedefault{includemcollective-agentsincludemcollective-agents::factsincludepuppet-cron#includedisco#includeqguard#includepuppet-upgradeincludeucla_base}{ quote code }IfIcommentthelineI'mabletorunpuppet.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and
Jira (PUP-2818) Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled
Title: Message Title Josh Cooper commented on an issue Re: Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled As a result of task scheduler changes in PUP-2881, we gracefully detect when the task scheduler service is not running. Closing this. Add Comment Puppet / PUP-2818 Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled This ticket should represent more of a verification of behavior in the latest 0.3.0 taskscheduler gem after upgrading to the latest version during x64 FFI work. According to user reports, a crash occurs at the following line of puppet-win32-ruby: https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3-p484.3/ruby/lib/ruby/gems/1.9.1/gems/win32-ta... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1371) puppet requires local config changes for init scripts to work
Title: Message Title
Richard Raseley commented on an issue
Re: puppet requires local config changes for init scripts to work
I've also encountered this issue with a FOSS master on Centos 6.5 and it made me sad. =[
Overriding the default PID file configurations worked for me, but is a sub-optimal user experience.
Add Comment
Puppet / PUP-1371
puppet requires local config changes for init scripts to work
When puppet is configured to manage it's own services it fails, due to broken init scripts for EL6 {noformat} Notice: /Stage[main]/Puppet::Server/Service[puppetmaster]/ensure: ensure changed 'stopped' to 'running' Info: /Stage[main]/Puppet::Server/Service[puppetmaster]: Unscheduling refresh on Service[puppetmaster] Notice: /Stage[main]/Puppet/Servic...
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
Jira (PUP-2933) Could not parse for environment testing: Illegal fully qualified name in file
Title: Message Title Charlie Sharpsteen commented on an issue Re: Could not parse for environment testing: Illegal fully qualified name in file Nikolay Georgieff: Is your puppet master configured to use parser=future? Using hyphens in class names was deprecated in 2.7 and the future parser has dropped support for these names. Classes such as mcollective-agents will need to be re-named to mcollective_agents in order to function with the new parser. Add Comment Puppet / PUP-2933 Could not parse for environment testing: Illegal fully qualified name in file I'm getting rror 400 on SERVER: Could not parse for environment testing: Illegal fully qualified name in file /etc/puppet/manifests/site.pp at line 10:28 on node ucla-ws-xx1.xx..xxx Puppet is not properly parsing include module::class -- Logs -- nfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2933) Could not parse for environment testing: Illegal fully qualified name in file
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2933 Could not parse for environment testing: Illegal fully qualified name in file Change By: Charlie Sharpsteen Assignee: NikolayGeorgieff 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-2919) Remove conditional pending tests on windows x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2919 Remove conditional pending tests on windows x64 Change By: Josh Cooper Sprint: Week2014-7- 23 9 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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Josh Cooper assigned an issue to Ethan Brown Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) Change By: Josh Cooper Assignee: EthanBrown 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-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper assigned an issue to Rob Reynolds Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Josh Cooper Assignee: RobReynolds 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-1639) Some modules fail to install into target_dir
Title: Message Title Jeffery Smith commented on an issue Re: Some modules fail to install into target_dir As a work around, I did this: sudo su - (become root) mkdir /var/lib/puppet/etc_puppet cd /etc/puppet tar cf - * | (cd /var/lib/puppet/etc_puppet ; tar xvf -) mv /etc/puppet /etc/puppet.save ln -s /var/lib/puppet/etc_puppet /etc/puppet Now I am able install modules without errors. Add Comment Puppet / PUP-1639 Some modules fail to install into target_dir puppet module install puppetlabs/apache -i puppet/forge-modules Notice: Preparing to install into /home/www/puppet/forge-modules ... Notice: Created target directory /home/www/puppet/forge-modules Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file or directory - /home/www/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
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-1639 Some modules fail to install into target_dir Change By: Alex Dreyer Assignee: AlexDreyer 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-1639) Some modules fail to install into target_dir
Title: Message Title Alex Dreyer commented on an issue Re: Some modules fail to install into target_dir This is caused by having symlinks in modules. PUP-2912 will provide a check to help prevent this from happening. Add Comment Puppet / PUP-1639 Some modules fail to install into target_dir puppet module install puppetlabs/apache -i puppet/forge-modules Notice: Preparing to install into /home/www/puppet/forge-modules ... Notice: Created target directory /home/www/puppet/forge-modules Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file or directory - /home/www/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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title
Ethan Brown commented on an issue
Re: Upgrade win32-taskscheduler (or replace)
Found a small issue with how we're handling HRESULTs, that has been discovered during acceptance tests runs on Windows 2003.
https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/puppet-4/job/Puppet-Acceptance-Windows-4.0-vcloud-and-github/72/label=acc-coord,platform=win2003r2/testReport/junit/(root)/tests_resource_scheduled_task/should_modify_rb/
Host 'm4xhy723nu65abm' exited with 1 running: env PATH=/opt/puppet-git-repos/hiera/bin:$
Unknown macro: {PATH}
RUBYLIB=`cygpath -w /opt/puppet-git-repos/hiera/lib`;`cygpath -w /opt/puppet-git-repos/hiera-puppet/lib`;$
Unknown macro: {RUBYLIB}
cmd.exe /c puppet resource scheduled_task pl6470 ensure=present command=c:\\windows\\system32notepad2.exe arguments=args-pl6470 Last 10 lines of output were: [mNotice: /Scheduled_task[pl6470]/command: command changed 'c:\windows\system32\notepad.exe' to 'c:\windows\system32\notepad2.exe'[0m [mNotice: /Scheduled_task[pl6470]/arguments: arguments changed '' to 'args-pl6470'[0m [1;31mError: Could not run: Failed to call #Win32::TaskScheduler::COM::Task:0x1524630::GetAccountInformation with HRESULT: -2147216625.: No account information could be found in the Task Scheduler security database for the task indicated. [0m
Although the 0x800# style error values we're catching are the correct errors, when they are being propagated, we're actually receiving the 2s complement value, which is not what our constant defines in Ruby.
For instance, 0x8004130F is SCHED_E_ACCOUNT_INFORMATION_NOT_SET, but the non 2s complement value in Ruby is 2147750671. The value returned from the FFI call is -2147216625, which is the 2s complement equivalent of 0x8004130F.
Therefore any error COM HRESULT error constants starting with 0x8 should be modified to use the 2s complement version instead.
Add Comment
Jira (PUP-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title
Andy Parker commented on an issue
Re: Validation of Exec-Attribute user limits usability with non-root user.
Merged into master in 9c7cb1
Add Comment
Puppet / PUP-2732
Validation of Exec-Attribute user limits usability with non-root user.
Our customer will only use Puppet if all necessary operations are possible running Puppet without root privileges. Actually Puppet agent validates the user attribute of exec ressource that way, that it's fully unsupported if running without root user. Doing so, the following error message is printed and execution aborted: {code} Error: Failed to apply c...
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-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title
Andy Parker commented on an issue
Re: Validation of Exec-Attribute user limits usability with non-root user.
For a functional review we should try this out on windows (it shouldn't allow specifying the user there). On linux machines see what happens when the user requested doesn't exist on the system.
Add Comment
Puppet / PUP-2732
Validation of Exec-Attribute user limits usability with non-root user.
Our customer will only use Puppet if all necessary operations are possible running Puppet without root privileges. Actually Puppet agent validates the user attribute of exec ressource that way, that it's fully unsupported if running without root user. Doing so, the following error message is printed and execution aborted: {code} Error: Failed to apply c...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown assigned an issue to Rob Reynolds Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) Change By: Ethan Brown Assignee: RobReynolds 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-2919) Remove conditional pending tests on windows x64
Title: Message Title Ethan Brown assigned an issue to Rob Reynolds Puppet / PUP-2919 Remove conditional pending tests on windows x64 Change By: Ethan Brown Assignee: RobReynolds 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-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Ethan Brown commented on an issue Re: Remove windows-pr gem as a Windows dependency Note that we need this to run through acceptance jobs to validate that the code / gemsets are in agreement with each other (based on the contents of puppet-win32-ruby). Further, we should verify the gemset in the packaged MSI to ensure that the changes have been propagated there as well. Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... 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,
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Joshua Partlow - ready for merge is fine. I've created QENG-956 for the Beaker 1.16 release and added it as a blocker to this ticket. Once that's resolved, we can merge PR 2871. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. 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-2935) Error deserializing JSON in CentOS
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Error deserializing JSON in CentOS
This appears to be related to Ruby 1.8.7 in some way as the same problem manifests on Ubuntu 12.04.
Add Comment
Puppet / PUP-2935
Error deserializing JSON in CentOS
With that environment, if I execute: {code} # puppet apply --catalog client1-catalog.json Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}] {code} If I execute in Ubuntu 14.04 with Puppet 3.6.2 ruby-json 1.8.0-1build...
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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) Merged updated PR at 47505bec Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. 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-2818) Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled
Title: Message Title Ethan Brown commented on an issue Re: Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled Clarification. We don't gracefully detect that the service is not running, but we correctly deal with errors now and surface the underlying COM HRESULT properly, which the old gem code did not. Instead of a crash, a user now sees the error for The Task Scheduler Service is not running. which is self-evident. Add Comment Puppet / PUP-2818 Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled This ticket should represent more of a verification of behavior in the latest 0.3.0 taskscheduler gem after upgrading to the latest version during x64 FFI work. According to user reports, a crash occurs at the following line of puppet-win32-ruby: https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3-p484.3/ruby/lib/ruby/gems/1.9.1/gems/win32-ta... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-2919) Remove conditional pending tests on windows x64
Title: Message Title Rob Reynolds commented on an issue Re: Remove conditional pending tests on windows x64 Merged into master at 2cfd4ac Add Comment Puppet / PUP-2919 Remove conditional pending tests on windows x64 We added conditional pending tests when running on windows and ruby 2, see https://jira.puppetlabs.com/browse/PUP-2784?focusedCommentId=80646page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-80646. These tests need to be re-enabled once win32-taskscheduler is updated to run on x64. 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-603) Facter acceptance should use our github mirror
Title: Message Title Ethan Brown updated an issue Facter / FACT-603 Facter acceptance should use our github mirror Change By: Ethan Brown 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 (FACT-603) Facter acceptance should use our github mirror
Title: Message Title Rob Reynolds updated an issue Facter / FACT-603 Facter acceptance should use our github mirror Change By: Rob Reynolds Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2944) yum provider should use osfamily instead of operatingsystem fact
Title: Message Title redmine.exporter created an issue Puppet / PUP-2944 yum provider should use osfamily instead of operatingsystem fact Issue Type: Bug Assignee: Unassigned Created: 16/Jul/14 4:59 PM Labels: redmine Priority: Normal Reporter: redmine.exporter The yum provider for the package type uses the operatingsystem fact to specify the defaultfor and should be using the osfamily fact so that we do not have to duplicate effort listing all the RedHat derivatives in both places. Add Comment This message was
Jira (PUP-2897) undefined method `exist?' for Puppet::FileSystem:Module
Title: Message Title
Den Mat commented on an issue
Re: undefined method `exist?' for Puppet::FileSystem:Module
I was getting the same issue:
Using vagrant and docker with this in the Dockerfile:
RUN yum install -y puppet-3.4.3-1.el6 facter-1.7.5-1.el6
produced these errors:
Notice: /Stage[main]/Puppetmaster::Install/Package[gcc]/ensure: created
Debug: /Stage[main]/Puppetmaster::Install/Package[gcc]: The container Class[Puppetmaster::Install] will propagate my refresh event
Error: Could not back up /etc/sysconfig/puppet: Unsupported checksum type md5
Error: Could not back up /etc/sysconfig/puppet: Unsupported checksum type md5
Error: /Stage[main]/Puppetmaster::Client::Linux/File[/etc/sysconfig/puppet]/content: change from {md5}c1d4a401f7c4587b47aab3a8053a854f to {md5}caa3a269208ab9421b9cadfb1299f056 failed: Could not back up /etc/sysconfig/puppet: Unsupported checksum type md5
Debug: Executing '/bin/rpm -q ruby-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Changing the Dockerfile to run with the following:
RUN yum install -y puppet-3.6.2-1.el6 facter-2.1.0-1.el6
Runs as expected. My manifest installs puppetdb from the puppetlabs/puppetdb module at the latest version. This seems to bring in the latest version of puppet (installs latest as a rpm dependency I believe). So having a different version inside my puppet manifest (setting puppet to 3.4.3 for instance) breaks (probably could fix this with ordering but haven't tested).
My solution will be to role out 3.6.x faster.
Add Comment
Puppet / PUP-2897
Jira (PUP-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Kylo Ginsberg commented on an issue Re: if initctl --version doesn't list a matching string, upstart service provider fails badly. Sven Mueller sorry for the delayed response (gmail was dropping some jira tickets in my spam folder - arh!). This looks like a legit bug. Thanks for the patch idea above, though I agree with your comment above. I think the easiest way to move this forward would be if you put together a pull request against puppet with the above patch (ideally with a spec test), so it can get some dedicated attention during PR triage. Is that something you're up for? Regardless, thanks for raising the issue! Add Comment Puppet / PUP-2790 if initctl --version doesn't list a matching string, upstart service provider fails badly. We are running puppet during the installation process, using Debian installers late_command option. At this point, calling status avahi-daemon returns: - cut here - Warning: Fake initctl called, doing nothing. - cut here - (As does any other call to initctl, such as initctl list) Unfortunately, I was unable to determine if this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1519) Package resource should allow ensure=1.0 or ensure=0.10 as well as 'latest', 'installed' and specific version number
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Package resource should allow ensure=1.0 or ensure=0.10 as well as 'latest', 'installed' and specific version number
This was discussed on puppet-dev also: https://groups.google.com/forum/#!msg/puppet-dev/f2bPw9liasg/pfWFUja_-XwJ
Add Comment
Puppet / PUP-1519
Package resource should allow ensure=1.0 or ensure=0.10 as well as 'latest', 'installed' and specific version number
It would be helpful if the 'ensure' parameter to the Package resrouce could also specify 'at least version **x**' and 'no later than version **y**' as well as 'latest version', 'installed' (IE, any version) or a specific version number. EG: {code} package { 'foo': ensure='1.0' } {code} would act as 'latest' if the current package was uninstal...
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
