Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title
Gavin Williams commented on an issue
Re: support HTTP(S) URL as the file 'source'
+1 from me... Would make working with Windows clients much easier, as there's no command line wget to use
Add Comment
Puppet / PUP-1072
support HTTP(S) URL as the file 'source'
Lots and lots of folks want to be able to do this: file { /tmp/example.txt: source = 'http://example.com/example.txt#39; } This would be good to support; obviously the metadata for the HTTP URI is much less available than via puppet file serving, but this would make a lot of people very, very happy.
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/groups/opt_out.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Richard Clark commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
confirmed, also seen on 3.3.X 3.4.2 upgrade
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
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/groups/opt_out.
Jira (PUP-1683) custom parser functions should be namespace-able
Title: Message Title redmine.exporter created an issue Puppet / PUP-1683 custom parser functions should be namespace-able Issue Type: New Feature Assignee: Unassigned Created: 13/Feb/14 4:04 AM Labels: redmine Priority: Normal Reporter: redmine.exporter If I define a function in module/foo/plugins/puppet/parser/bar.rb, and call it 'bar', I want to be able to access the function in puppet manifests as 'foo::bar'. Current documentation recommends putting plugins/functions/etc in modules, so it makes sense to be able to reference those functions by module namespace. Currently calling a function as foo::bar() results in a syntax error. Add Comment
Jira (PUP-1679) Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction
Title: Message Title Ethan Brown commented on an issue Re: Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction This has been started in https://github.com/puppetlabs/puppet/commit/857291ed0c64119dd13b44934ecab4d11b5f1e60 Add Comment Puppet / PUP-1679 Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction The built-in Ruby classes FileUtils.chmod and File.chmod do not behave correctly under Windows. We do however have a nice method Puppet::Util::Windows::Security.set_mode(mode, path) that does it's best job to simulate a POSIX mode and roundtrip it properly. All call sites that use the Ruby methods should be updated to use a new Puppet::FileSystem.ch... 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 (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber Assignee: KennethBarber RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber Assignee: KennethBarber 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/groups/opt_out.
Jira (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber ThistickettracksthefinalremovalofJDK1.6support.*Removethefunkyciphermanipulationstuffinjetty.clj*Lookforcodethatdispatchesonjvmversion,auditit*Removetestingagainst1.6 (.travis.ymlneedschanging) *Forolderdebianbaseddistros,wecouldaddtheJavaPackagemanuallybuiltpackagetothecontrolfileforthosedistrossopeoplehaveanoption(albeitamanualbuiltpackageisapain,butbetterthennothing),weneedtotestthishowever:https://gist.github.com/kbarber/7775906*Forolderdebian/ubuntudistrosaswell,ifwedecidetouseJavaPackagethenweshouldmodifyouracceptancetestssomehowtosupportthis-atthemomentifwemakethischangetheseacceptancetestswillbegintofail. 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/groups/opt_out.
Jira (PUP-1670) PR (2347): A way to validate file content syntax before replacing files
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1670 PR (2347): A way to validate file content syntax before replacing files Change By: Joshua Cooper Assignee: CharlieSharpsteen 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/groups/opt_out.
Jira (PUP-1407) PR (2238): puppet CA generates CRL that does not conform to RFC5280
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1407 PR (2238): puppet CA generates CRL that does not conform to RFC5280 Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1158) PR (2061) Augeas provider warns on parse errors in other files handled by same lens
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1158 PR (2061) Augeas provider warns on parse errors in other files handled by same lens Change By: Joshua Cooper Assignee: DominicCleal 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/groups/opt_out.
Jira (PUP-1629) WIndows 2008r2 fails to load() a file it previously store()d
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1629 WIndows 2008r2 fails to load() a file it previously store()d Change By: Joshua 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/groups/opt_out.
Jira (PUP-1327) PR (2060) owner of files created by nagios resource types
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1327 PR (2060) owner of files created by nagios resource types Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1681) Windows stat doesn't expose the correct mode
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1681 Windows stat doesn't expose the correct mode Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1366) yum provider doesn't respect items provided by a package, only the package name
Title: Message Title Sam Kottler assigned an issue to Sam Kottler Puppet / PUP-1366 yum provider doesn't respect items provided by a package, only the package name Change By: Sam Kottler Assignee: SamKottler 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/groups/opt_out.
Jira (PUP-1684) Mark some facts immutable
Title: Message Title redmine.exporter created an issue Puppet / PUP-1684 Mark some facts immutable Issue Type: New Feature Assignee: Unassigned Created: 13/Feb/14 9:50 AM Labels: redmine Priority: Normal Reporter: redmine.exporter So I think there's a benefit to be had from having the ability to flag certain facts derived from the client as immutable, and then be able to act differently should those facts change. Differently could be ceasing to provide a catalog to the potentially compromised server reporting a custom fact suddenly different, or sending an email because a dimm died and the server suddenly has less memory than it did before, or ... Certain facts are generated on the client. there's no real way around that. having the ability to tell the puppetmaster that should X, Y, or Z fact change something is drastically wrong and do something about it seems like a good tool to have in the shed, even if it's only used on occasion. Add Comment
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Thomas Raehalme commented on an issue Re: Some modules fail to install into target_dir I can confirm the same problem on CentOS 6.4 and puppet/puppet-server-3.4.2. 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/groups/opt_out.
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Thomas Raehalme commented on an issue Re: Some modules fail to install into target_dir Version 0.10.0 can be successfully installed. 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/groups/opt_out.
Jira (PUP-1120) PR (2169) Change default private key permissions to permit group read
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1120 PR (2169) Change default private key permissions to permit group read Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1451) PR (2257) Make public SSL files publicly readable
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1451 PR (2257) Make public SSL files publicly readable Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-713) PR (2050): (#4820) cron type should not allow specification of special parameter and normal hour/minute/day/etc parameters. - ffrank
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-713 PR (2050): (#4820) cron type should not allow specification of special parameter and normal hour/minute/day/etc parameters. - ffrank Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-649) PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-649 PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Thomas Raehalme commented on an issue Re: Some modules fail to install into target_dir Same error also with puppetlabs/firewall. Version 0.4.2 installs, but versions 0.5.0 and 1.0.0 do not. 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/groups/opt_out.
Jira (PUP-1668) Redmine Pages need pointers to JIRA
Title: Message Title Charlie Sharpsteen commented on an issue Re: Redmine Pages need pointers to JIRA So, there are two viable paths forward here: We can modify the Redmine templates so that a banner is displayed site-wide no matter which page is being looked at. We can edit the home page and project descriptions of public facing projects. Projects that have been migrated to JIRA can get a pointer to their new homes on JIRA. Projects that are defunct can get a EOL notice or get archived/pruned. Option 1 would require a quick custom patch to the Redmine code base which may not be desirable. Option 2 would require a bit more work, but would also avoid causing confusion in internal projects that are actually still active — such as the Operations Inventory and Presales Support Queues. Regardless of what we choose to do, we should probably look into pruning dead projects from Redmine. Doing some cleanup will make the archived information easier to maintain going forward. Add Comment Puppet / PUP-1668 Redmine Pages need pointers to JIRA Given that most people solve problems via Google, and the current first hits for google with the search 'puppet bug report' goto the old Redmine site, it would be very helpful if the redmine site could have a notation somewhere ( header perhaps ) that lets users know the site is depreciated and please go use the new Jira site.
Jira (PUP-1685) PR (2351): Change warning message to debug message - cabello
Title: Message Title gepetto-bot created an issue Puppet / PUP-1685 PR (2351): Change warning message to debug message - cabello Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Feb/14 11:34 AM Labels: github Priority: Normal Reporter: gepetto-bot Change warning message to debug message Author: Danilo Cabello danilo.cabe...@gmail.com Company: Instaclick Github ID: cabello Pull Request 2351 Discussion Pull Request 2351 File Diff Pull Request Description Since this is the expected
Jira (PUP-1686) PR (2352): (pup-1491)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot created an issue Puppet / PUP-1686 PR (2352): (pup-1491)(packaging) Remove Fedora 18 from default package builds - shrug Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Feb/14 11:38 AM Labels: github Priority: Normal Reporter: gepetto-bot (pup-1491)(packaging) Remove Fedora 18 from default package builds Author: Company: Github ID: shrug Pull Request 2352 Discussion Pull Request 2352 File Diff Pull Request Description Fedora 18 reached end-of-life on
Jira (FACT-329) PR (635): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug
Title: Message Title gepetto-bot created an issue Facter / FACT-329 PR (635): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 13/Feb/14 11:45 AM Labels: github Priority: Normal Reporter: gepetto-bot (fact-242)(packaging) Remove Fedora 18 from the default set of package builds Author: Company: Github ID: shrug Pull Request 635 Discussion Pull Request 635 File Diff Pull Request Description Fedora 18 reached
Jira (FACT-330) PR (636): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug
Title: Message Title gepetto-bot created an issue Facter / FACT-330 PR (636): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 13/Feb/14 11:47 AM Labels: github Priority: Normal Reporter: gepetto-bot (fact-242)(packaging) Remove Fedora 18 from the default set of package builds Author: Company: Github ID: shrug Pull Request 636 Discussion Pull Request 636 File Diff Pull Request Description Fedora 18 reached
Jira (PUP-1685) PR (2351): Change warning message to debug message - cabello
Title: Message Title gepetto-bot commented on an issue Re: PR (2351): Change warning message to debug message - cabello cabello commented: Actually, we noticed that alias is a reserved word, by changing the parameter name, the warning was gone, so I guess this is a important warning. :smile: Add Comment Puppet / PUP-1685 PR (2351): Change warning message to debug message - cabello h2. Change warning message to debug message * Author: Danilo Cabello danilo.cabe...@gmail.com * Company: Instaclick * Github ID: [cabello|https://github.com/cabello] * [Pull Request 2351 Discussion|https://github.com/puppetlabs/puppet/pull/2351] * [Pull Request 2351 File Diff|https://github.com/puppetlabs/puppet/pull/2351/files] h2. Pull Request ... 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-1685) PR (2351): Change warning message to debug message - cabello
Title: Message Title gepetto-bot commented on an issue Re: PR (2351): Change warning message to debug message - cabello Pull request [metaparam] Change warning message to debug message has been closed. Add Comment Puppet / PUP-1685 PR (2351): Change warning message to debug message - cabello h2. Change warning message to debug message * Author: Danilo Cabello danilo.cabe...@gmail.com * Company: Instaclick * Github ID: [cabello|https://github.com/cabello] * [Pull Request 2351 Discussion|https://github.com/puppetlabs/puppet/pull/2351] * [Pull Request 2351 File Diff|https://github.com/puppetlabs/puppet/pull/2351/files] h2. Pull Request ... 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/groups/opt_out.
Jira (HI-182) PR (180): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot created an issue Hiera / HI-182 PR (180): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 13/Feb/14 11:56 AM Labels: github Priority: Normal Reporter: gepetto-bot (hi-149)(packaging) Remove Fedora 18 from the default package builds Author: Company: Github ID: shrug Pull Request 180 Discussion Pull Request 180 File Diff Pull Request Description Fedora 18 reached end-of-life on
Jira (HI-181) PR (179): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot created an issue Hiera / HI-181 PR (179): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 13/Feb/14 11:55 AM Labels: github Priority: Normal Reporter: gepetto-bot (hi-149)(packaging) Remove Fedora 18 from the default package builds Author: Company: Github ID: shrug Pull Request 179 Discussion Pull Request 179 File Diff Pull Request Description Fedora 18 reached end-of-life on
Jira (PUP-1407) PR (2238): puppet CA generates CRL that does not conform to RFC5280
Title: Message Title Joshua Cooper commented on an issue Re: PR (2238): puppet CA generates CRL that does not conform to RFC5280 To verify, wipe out the master's ssl directory /etc/puppet/ssl, and install a puppetmaster without this change. Start the master, and it will generate a /etc/puppet/ssl/crl.pem. Dump this file using: # openssl crl -in /etc/puppet/ssl/ca/ca_crl.pem -noout -text Certificate Revocation List (CRL): Version 2 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: /CN=Puppet CA: puppetmaster.solar.lan Last Update: Jan 10 04:52:25 2014 GMT Next Update: Jan 9 04:52:26 2019 GMT CRL extensions: X509v3 CRL Number: 0 No Revoked Certificates. Signature Algorithm: sha1WithRSAEncryption Note there is only the one CRL extension for crlNumber. Next wipe out the ssl directory, install a new puppetmaster (or run from source bundle exec puppet master ...) and do the same thing, but you should see an additional extension for authority key identifier. The extension will be of the form: X509v3 Authority Key Identifier: 0B:46:40:EC:0D:8B:39:14:FB:5F:AB:56:3C:D2:82:98:8A:9E:EC:AC Next verify that the value of the extension matches the subject key identifier in the ca's certificate: # openssl x509 -in /etc/puppet/ssl/ca/ca_crt.pem -noout -text Finally, revoke a host certificate, e.g. for the puppetmaster # puppet cert revoke puppetmaster Next run # openssl crl -in /etc/puppet/ssl/ca/ca_crl.pem -noout -text And verify that the CRL serial number has been incremented, that the CRL lists the revoked certificate's serial number along with reason of key compromise, and that the CRL authority key identifier extension is the same. Add Comment
Jira (PUP-648) PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Title: Message Title gepetto-bot commented on an issue Re: PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx Pull request Add upgradeable and versionable features to pkgin provider has been closed. Add Comment Puppet / PUP-648 PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx h2. Add upgradeable and versionable features to pkgin provider * Author: * Company: * Github ID: [javiplx|https://github.com/javiplx] * [Pull Request 2023 Discussion|https://github.com/puppetlabs/puppet/pull/2023] * [Pull Request 2023 File Diff|https://github.com/puppetlabs/puppet/pull/2023/files] h2. Pull Request Description (web... 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/groups/opt_out.
Jira (MCO-184) PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot created an issue MCollective / MCO-184 PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug Issue Type: Task Assignee: Pieter Loubser Created: 13/Feb/14 12:26 PM Labels: github Priority: Normal Reporter: gepetto-bot (mco-166)(packaging) Remove Fedora 18 from the default package builds Author: Company: Github ID: shrug Pull Request 164 Discussion Pull Request 164 File Diff Pull Request Description (webhooks-id: 735db48a7f0b4bd08ff8363224efcad1)
Jira (MCO-185) PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot created an issue MCollective / MCO-185 PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug Issue Type: Task Assignee: Pieter Loubser Created: 13/Feb/14 12:27 PM Labels: github Priority: Normal Reporter: gepetto-bot (mco-166)(packaging) Remove Fedora 18 from the default package builds Author: Company: Github ID: shrug Pull Request 165 Discussion Pull Request 165 File Diff Pull Request Description Fedora 18 reached end-of-life on 1/14/14. This removes Fedora 18 from the list of default package builds. (webhooks-id: 62cdc1db704f05e76e310a8fed040e65)
Jira (PUP-648) PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Title: Message Title Peter Huene updated an issue Puppet / PUP-648 PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx Change By: Peter Huene h2. Addupgradeableandversionablefeaturestopkginprovider *Author:*Company:*GithubID:[javiplx|https://github . com/javiplx]*[PullRequest2023Discussion|https://github Thepkginpackageprovidershouldsupporttheupgradeableandversionablefeaturessincetheunderlyingpackagemanagersupportsthem . com/puppetlabs/puppet/pull/2023]*[PullRequest2023FileDiff|https://github.com/puppetlabs/puppet/pull/2023/files]h2.PullRequestDescription GH - ---(webhooks-id:46c4ef7724a8d0a4fd50d2b7a273c089) 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/groups/opt_out.
Jira (PUP-648) PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Title: Message Title Peter Huene updated an issue Puppet / PUP-648 PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx Change By: Peter Huene Addupgradeableandversionablefeaturestopkginprovider.Thepkginpackageprovidershouldsupporttheupgradeableandversionablefeaturessincetheunderlyingpackagemanagersupportsthem. GH- Seelinkedpullrequestforimplementation. 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/groups/opt_out.
Jira (PUP-648) PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Title: Message Title
Peter Huene commented on an issue
Re: PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Merged with commit ea489e8.
For functional review, a DragonFly BSD install with version less than 3.6 is needed. Version 3.6 replaced pkgsrc/pkgin with pkgng.
The following manifests should now work:
%code% package { 'vim': ensure = latest }
%code%
%code% package { 'vim': ensure = '7.3.762' }
%code%
Add Comment
Puppet / PUP-648
PR (2023): Add upgradeable and versionable features to pkgin provider - javiplx
Add upgradeable and versionable features to pkgin provider. The pkgin package provider should support the upgradeable and versionable features since the underlying package manager supports them. See linked pull request for implementation.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed
Jira (PUP-1687) PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne
Title: Message Title gepetto-bot created an issue Puppet / PUP-1687 PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 13/Feb/14 12:39 PM Labels: github Priority: Normal Reporter: gepetto-bot Revert Add initial support for building in a RHEL 7 mock Author: Melissa Company: Github ID: melissaanne Pull Request 2353 Discussion Pull Request 2353 File Diff Pull Request Description This reverts commit
Jira (PDB-448) Create a latest version route for REST services
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-448 Create a latest version route for REST services Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 12:45 PM Priority: Normal Reporter: Ryan Senior Currently when we cut a new version of the PuppetDB API, the URL of all of our services change, even if the contract/content of one or more of the individual services has not. This ticket is for creating a non-versioned endpoint that always uses the latest version. To take this a step further (maybe a separate ticket that should be split out) is to accept a header in the latest version path that indicates a version. This would allow users to always use latest, but with a small tweak use a different version for a specific service without changing URLs. Add Comment
Jira (PDB-449) PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-449 PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug Issue Type: Task Assignee: Unassigned Created: 13/Feb/14 12:49 PM Labels: github Priority: Normal Reporter: gepetto-bot (pdb-343)(packaging) Remove Fedora 18 from default package builds Author: Company: Github ID: shrug Pull Request 854 Discussion Pull Request 854 File Diff Pull Request Description Fedora 18 reached end-of-life on 1/14/14. This removes Fedora 18 from the list of default package builds. (webhooks-id: 815a02c450c2f40c2381c4eff41fd86a)
Jira (PDB-450) PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-450 PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug Issue Type: Task Assignee: Unassigned Created: 13/Feb/14 12:50 PM Labels: github Priority: Normal Reporter: gepetto-bot (pdb-343)(packaging) Remove Fedora 18 from default package builds Author: Company: Github ID: shrug Pull Request 855 Discussion Pull Request 855 File Diff Pull Request Description Fedora 18 reached end-of-life on 1/14/14. This removes Fedora 18 from the list of default package builds. (webhooks-id: 18bc571f270ae22c86ab9a12252536a9)
Jira (PDB-450) PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-450 PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 855 Discussion|https://github.com/puppetlabs/puppetdb/pull/855] * [Pull Request 855 File Diff|https://github.com/puppetlabs/puppetdb/pull/855/files] h2. Pull Request Description Fedora 1... 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 (PDB-449) PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-449 PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 854 Discussion|https://github.com/puppetlabs/puppetdb/pull/854] * [Pull Request 854 File Diff|https://github.com/puppetlabs/puppetdb/pull/854/files] h2. Pull Request Description Fedora 1... 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 (PDB-129) Make puppet node clean --unexport work with PuppetDB
Title: Message Title Jay Wallace commented on an issue Re: Make puppet node clean --unexport work with PuppetDB Referencing Nick Lewis: Possible workaround: I’m not fond of any solution that involves modifying the data in PuppetDB. I think similar functionality could be achieved through a function whose purpose is to collect deactivated exported resources and set ensure = absent, so that’s the solution I would lean toward. The one change that requires to PuppetDB would be to add back the ability to query for resources of deactivated nodes. Alternately, you could leave the nodes active and use the standard collection syntax with an ensure = absent resource override, if you have a way to identify the set of resources you want to do that for. Obviously that option depends on the particular case, since you may or may not have a single identifying characteristic for your deactivated nodes. Add Comment PuppetDB / PDB-129 Make puppet node clean --unexport work with PuppetDB The current node face has an --unexport option that tells clean to flag resources previously exported for a node to flip to ensure = absent (I think). We should see if the existing implementation already works with PuppetDB (does it simply store a revised catalog or something), or if we need to implement our own support for this. A good use case wo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-451) Versions for routes should be handled in a single place
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-451 Versions for routes should be handled in a single place Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 12:55 PM Priority: Normal Reporter: Ryan Senior This would involve creating a middleware for intercepting the version in a path and using that version as metadata for the request. This is basically just applying a pattern we're using at lower levels of the code at the route level. Add Comment This message
Jira (PDB-452) Update model to support environments
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-452 Update model to support environments Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:04 PM Priority: Normal Reporter: Ryan Senior Wire formats should be updated to include environment Catalog should include environment Fact payload should include environment Schema migration Add Comment
Jira (PDB-453) Update terminus to include environment information
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-453 Update terminus to include environment information Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:06 PM Priority: Normal Reporter: Ryan Senior Terminus data submission should: Include environment in submitted catalogs Include environment in submitted facts Add Comment
Jira (PDB-454) Update Query APIs to support environment
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-454 Update Query APIs to support environment Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:08 PM Priority: Normal Reporter: Ryan Senior Query API updates include: Resource queries Fact queries Node queries the environment of the last catalog/fact-set/report for the node Report/events? The ability to enumerate all environments we know about
Jira (PDB-455) Update terminus querying to include environments
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-455 Update terminus querying to include environments Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:09 PM Priority: Normal Reporter: Ryan Senior Terminus querying should include environment in resource queries Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-456) New REST endpoints scoped by environment
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-456 New REST endpoints scoped by environment Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:11 PM Priority: Normal Reporter: Ryan Senior New REST-y endpoints that are environment aware should be created come up with new endpoints for environments how do we thread environments into existing REST-y endpoints? Add Comment
Jira (PUP-1687) PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne
Title: Message Title gepetto-bot commented on an issue Re: PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne Pull request Revert Add initial support for building in a RHEL 7 mock has been closed. Add Comment Puppet / PUP-1687 PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne h2. Revert Add initial support for building in a RHEL 7 mock * Author: Melissa * Company: * Github ID: [melissaanne|https://github.com/melissaanne] * [Pull Request 2353 Discussion|https://github.com/puppetlabs/puppet/pull/2353] * [Pull Request 2353 File Diff|https://github.com/puppetlabs/puppet/pull/2353/files] h2. Pull Request Description --... 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/groups/opt_out.
Jira (PDB-457) Update import/export/anonymization to handle new wire formats
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-457 Update import/export/anonymization to handle new wire formats Issue Type: New Feature Assignee: Unassigned Created: 13/Feb/14 1:14 PM Fix Versions: 2.0.x Priority: Normal Reporter: Ryan Senior import/export should handle new wire formats anonymization should be environment-aware benchmark should handle new wire formats Add Comment
Jira (PDB-458) Investigate environment unknowns
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-458 Investigate environment unknowns Issue Type: New Feature Affects Versions: 2.0.x Assignee: Unassigned Created: 13/Feb/14 1:32 PM Priority: Normal Reporter: Ryan Senior Check how we can obtain the current environment Does report indicate environment? do we care if fact-set and catalog for a node have different environments, due to eventual consistency? Add Comment
Jira (PUP-1147) File purge actions should ignore unmanaged files created by File backup actions
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1147 File purge actions should ignore unmanaged files created by File backup actions So, the issue here is that we are telling Puppet to delete all unmanaged files in a directory while simultaneously telling Puppet to back up any deleted files by creating new unmanaged files in the same directory. The resulting behavior comes from the code executing as designed. Marking this as an improvement request since it will require changing the current definition of purge for File resources. Change By: Charlie Sharpsteen Component/s: TypesandProviders Labels: redmine type_file Issue Type: Bug Improvement Summary: Strangebehaviourwithfilebackupand File purge actionsshouldignoreunmanagedfilescreatedbyFilebackupactions Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1147) File purge actions should ignore unmanaged files created by File backup actions
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1147 File purge actions should ignore unmanaged files created by File backup actions Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics Round 1
Title: Message Title Ryan Senior commented on an issue Re: Scope 2.0 epics Round 1 Added tickets for environment tasks, next meeting we'll be discussing high availability Add Comment PuppetDB / PDB-330 Scope 2.0 epics Round 1 We want to do some more forward planning. Our proposal is to flesh out the scope of all the expected 2.0 epics which should allow us to plan out the future sprints to some degree, giving us some idea of how likely we can reach our targets. 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/groups/opt_out.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Joshua Cooper commented on an issue Re: puppet gem does not include platform specific gem dependencies Michelle Johansen I'm looking into this Add Comment Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies The puppet gem on windows has dependencies on win32-dir, etc, but these are not expressed in the gemspec file. So if you are developing a module, and attempt to `bundle install`, the transitive dependencies are not satisfied. The same issue exists in facter and hiera. 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/groups/opt_out.
Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title
Ethan Brown created an issue
Puppet / PUP-1688
When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Issue Type:
Bug
Assignee:
Unassigned
Created:
13/Feb/14 2:10 PM
Priority:
Normal
Reporter:
Ethan Brown
In spec/unit/type/file/mode_spec.rb there is a test that mentions a problem with
describe #sync with a symbolic mode do
let(:resource_sym) { Puppet::Type.type(:file).new :path = path, :mode = 'u+w,g-w' }
let(:mode_sym) { resource_sym.property(:mode) }
before { FileUtils.touch(path) }
it changes only the requested bits do
# lower nibble must be set to 4 for the sake of passing on Windows
Puppet::FileSystem.chmod(0464, path)
pp Puppet::Util::Windows::Security.get_mode(path).to_s(8)
pp Puppet::Util::Windows::Security.get_security_descriptor(path)
mode_sym.sync
stat = Puppet::FileSystem.stat(path)
pp Puppet::Util::Windows::Security.get_mode(path).to_s(8)
pp Puppet::Util::Windows::Security.get_security_descriptor(path)
(stat.mode 0777).to_s(8).should == 644
end
end
Under the current tests, this will output the following:
464
BUILTIN\Administrators
VAGRANT-2008R2\None
BUILTIN\Administrators: 0x1f0189
VAGRANT-2008R2\None: 0x12019f
Everyone: 0x120089
NT AUTHORITY\SYSTEM: 0x1f01ff
644
BUILTIN\Administrators
VAGRANT-2008R2\None
BUILTIN\Administrators: 0x1f019f
VAGRANT-2008R2\None: 0x120089
Everyone: 0x120089
NT
Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-1688
When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Change By:
Ethan Brown
Inspec/unit/type/file/mode_spec.rbthereisatestthatmentionsaproblemwith{code}describe#syncwithasymbolicmodedolet(:resource_sym){Puppet::Type.type(:file).new:path=path,:mode='u+w,g-w'}let(:mode_sym){resource_sym.property(:mode)}before{FileUtils.touch(path)}itchangesonlytherequestedbitsdo#lowernibblemustbesetto4forthesakeofpassingonWindowsPuppet::FileSystem.chmod(0464,path)ppPuppet::Util::Windows::Security.get_mode(path).to_s(8)ppPuppet::Util::Windows::Security.get_security_descriptor(path)mode_sym.syncstat=Puppet::FileSystem.stat(path)ppPuppet::Util::Windows::Security.get_mode(path).to_s(8)ppPuppet::Util::Windows::Security.get_security_descriptor(path)(stat.mode0777).to_s(8).should==644endend{code}Underthecurrenttests,thiswilloutputthefollowing:{code}464BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f0189VAGRANT-2008R2\None:0x12019fEveryone:0x120089NTAUTHORITY\SYSTEM:0x1f01ff644BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f019fVAGRANT-2008R2\None:0x120089Everyone:0x120089NTAUTHORITY\SYSTEM:0x1f01ff{code}Ifthelineofthetestthatinitiallysetsthemodeischangedtosetamodeof0466insteadof0464{code}Puppet::FileSystem.chmod( 0464 0466 ,path){code}Thefollowingisoutputinstead:{code}666BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f0189VAGRANT-2008R2\None:0x12019fEveryone:0x12019fNTAUTHORITY\SYSTEM:0x1f01ff666BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f019fVAGRANT-2008R2\None:0x120089Everyone:0x12019fNTAUTHORITY\SYSTEM:0x1f01ff{code}Notethatinsteadofsettingthemodeto0466,themodeisinitiallysetto0666.Furthermore,whentryingtosyncthepermissionchanges,themodeshouldbechangedto0646,butinsteadremainsat0666.Thisbehaviorisincorrect.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-1688
When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Change By:
Ethan Brown
Inspec/unit/type/file/mode_spec.rbthereisatestthatmentionsaproblemwith{code}describe#syncwithasymbolicmodedolet(:resource_sym){Puppet::Type.type(:file).new:path=path,:mode='u+w,g-w'}let(:mode_sym){resource_sym.property(:mode)}before{FileUtils.touch(path)}itchangesonlytherequestedbitsdo#lowernibblemustbesetto4forthesakeofpassingonWindowsPuppet::FileSystem.chmod(0464,path)ppPuppet::Util::Windows::Security.get_mode(path).to_s(8)ppPuppet::Util::Windows::Security.get_security_descriptor(path)mode_sym.syncstat=Puppet::FileSystem.stat(path)ppPuppet::Util::Windows::Security.get_mode(path).to_s(8)ppPuppet::Util::Windows::Security.get_security_descriptor(path)(stat.mode0777).to_s(8).should==644endend{code}Underthecurrenttests,thiswilloutputthefollowing:{code}464BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f0189VAGRANT-2008R2\None:0x12019fEveryone:0x120089NTAUTHORITY\SYSTEM:0x1f01ff644BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f019fVAGRANT-2008R2\None:0x120089Everyone:0x120089NTAUTHORITY\SYSTEM:0x1f01ff{code} If changing the lineofthe test thatinitiallysetsthemodeischanged to use set a differentinitial mode from0464to of 0466 the insteadof0464{code}Puppet::FileSystem.chmod(0464,path){code}The followingisoutputinstead : {code}666BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f0189VAGRANT-2008R2\None:0x12019fEveryone:0x12019fNTAUTHORITY\SYSTEM:0x1f01ff666BUILTIN\AdministratorsVAGRANT-2008R2\NoneBUILTIN\Administrators:0x1f019fVAGRANT-2008R2\None:0x120089Everyone:0x12019fNTAUTHORITY\SYSTEM:0x1f01ff{code}Notethatinsteadofsettingthemodeto0466,themodeisinitiallysetto0666.Furthermore,whentryingtosyncthepermissionchanges,themodeshouldbechangedto0646,butinsteadremainsat0666.Thisbehaviorisincorrect.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-266) Allow puppet to manage owner group file settings
Title: Message Title Ethan Brown commented on an issue Re: Allow puppet to manage owner group file settings Any mode application issues should be resolved in PUP-1688 before this ticket is addressed. Add Comment Puppet / PUP-266 Allow puppet to manage owner group file settings 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/groups/opt_out.
Jira (PUP-266) Allow puppet to manage owner group file settings
Title: Message Title Ethan Brown commented on an issue Re: Allow puppet to manage owner group file settings And so begins the legacy of JERP! Add Comment Puppet / PUP-266 Allow puppet to manage owner group file settings 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/groups/opt_out.
Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1688 When applying a mode of 0466 on Windows, a mode of 0666 is applied instead Change By: Ethan Brown Affects Version/s: 3.4.0 Affects Version/s: 3.4.1 Affects Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1688 When applying a mode of 0466 on Windows, a mode of 0666 is applied instead Change By: Ethan Brown Fix Version/s: 4.x 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/groups/opt_out.
Jira (PUP-1607) symbolic_modes.rb acceptance test is really slow
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1607 symbolic_modes.rb acceptance test is really slow Change By: Ethan Brown Fix Version/s: 3.6.0 Fix Version/s: 4.x 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/groups/opt_out.
Jira (PDB-271) Deprecate JDK 1.6. in docs
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-271 Deprecate JDK 1.6. in docs Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-266) Allow puppet to manage owner group file settings
Title: Message Title Ethan Brown commented on an issue Re: Allow puppet to manage owner group file settings FYI – other tickets should likely be added as blockers here for this feature. The modes specified in defaults.rb need to be cleaned up, and I believe that there are existing Github PRs and Redmine tickets somewhere that are of relevance here. Add Comment Puppet / PUP-266 Allow puppet to manage owner group file settings 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/groups/opt_out.
Jira (PUP-1210) authentication_authority key is not set when managing root's password using the puppet user provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1210 authentication_authority key is not set when managing root's password using the puppet user provider Change By: Kylo Ginsberg Story Points: 3 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/groups/opt_out.
Jira (HI-181) PR (179): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (179): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment Hiera / HI-181 PR (179): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (hi-149)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 179 Discussion|https://github.com/puppetlabs/hiera/pull/179] * [Pull Request 179 File Diff|https://github.com/puppetlabs/hiera/pull/179/files] h2. Pull Request Description Fedora 18 r... 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 (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Issue Type: Task Assignee: Unassigned Created: 13/Feb/14 3:01 PM Labels: github Priority: Normal Reporter: gepetto-bot The order of (keys m) and (vals m) is not guaranteed to be the same Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 857 Discussion Pull Request 857 File Diff Pull Request Description See http://dev.clojure.org/jira/browse/CLJ-1302 for more info (webhooks-id: b7a8208191d421c881ede30f834aadb8)
Jira (PUP-1686) PR (2352): (pup-1491)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (2352): (pup-1491)(packaging) Remove Fedora 18 from default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1686 PR (2352): (pup-1491)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pup-1491)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 2352 Discussion|https://github.com/puppetlabs/puppet/pull/2352] * [Pull Request 2352 File Diff|https://github.com/puppetlabs/puppet/pull/2352/files] h2. Pull Request Description Fedora ... 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-1687) PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne
Title: Message Title gepetto-bot commented on an issue Re: PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1687 PR (2353): Revert Add initial support for building in a RHEL 7 mock - melissaanne h2. Revert Add initial support for building in a RHEL 7 mock * Author: Melissa * Company: * Github ID: [melissaanne|https://github.com/melissaanne] * [Pull Request 2353 Discussion|https://github.com/puppetlabs/puppet/pull/2353] * [Pull Request 2353 File Diff|https://github.com/puppetlabs/puppet/pull/2353/files] h2. Pull Request Description --... 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 (PDB-450) PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment PuppetDB / PDB-450 PR (855): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 855 Discussion|https://github.com/puppetlabs/puppetdb/pull/855] * [Pull Request 855 File Diff|https://github.com/puppetlabs/puppetdb/pull/855/files] h2. Pull Request Description Fedora 1... 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 (FACT-329) PR (635): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (635): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-329 PR (635): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug h2. (fact-242)(packaging) Remove Fedora 18 from the default set of package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 635 Discussion|https://github.com/puppetlabs/facter/pull/635] * [Pull Request 635 File Diff|https://github.com/puppetlabs/facter/pull/635/files] h2. Pull Request Description ... 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 (MCO-184) PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment MCollective / MCO-184 PR (164): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (mco-166)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 164 Discussion|https://github.com/puppetlabs/marionette-collective/pull/164] * [Pull Request 164 File Diff|https://github.com/puppetlabs/marionette-collective/pull/164/files] h2. Pull Requ... 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 (MCO-185) PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment MCollective / MCO-185 PR (165): (mco-166)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (mco-166)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 165 Discussion|https://github.com/puppetlabs/marionette-collective/pull/165] * [Pull Request 165 File Diff|https://github.com/puppetlabs/marionette-collective/pull/165/files] h2. Pull Requ... 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 (PDB-449) PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment PuppetDB / PDB-449 PR (854): (pdb-343)(packaging) Remove Fedora 18 from default package builds - shrug h2. (pdb-343)(packaging) Remove Fedora 18 from default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 854 Discussion|https://github.com/puppetlabs/puppetdb/pull/854] * [Pull Request 854 File Diff|https://github.com/puppetlabs/puppetdb/pull/854/files] h2. Pull Request Description Fedora 1... 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 (FACT-330) PR (636): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (636): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-330 PR (636): (fact-242)(packaging) Remove Fedora 18 from the default set of package builds - shrug h2. (fact-242)(packaging) Remove Fedora 18 from the default set of package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 636 Discussion|https://github.com/puppetlabs/facter/pull/636] * [Pull Request 636 File Diff|https://github.com/puppetlabs/facter/pull/636/files] h2. Pull Request Description ... 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 (HI-182) PR (180): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (180): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug puppetcla commented: CLA signed by all contributors. Add Comment Hiera / HI-182 PR (180): (hi-149)(packaging) Remove Fedora 18 from the default package builds - shrug h2. (hi-149)(packaging) Remove Fedora 18 from the default package builds * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 180 Discussion|https://github.com/puppetlabs/hiera/pull/180] * [Pull Request 180 File Diff|https://github.com/puppetlabs/hiera/pull/180/files] h2. Pull Request Description Fedora 18 r... 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-1689) Windows Memory Leaks
Title: Message Title Ethan Brown created an issue Puppet / PUP-1689 Windows Memory Leaks Issue Type: Bug Affects Versions: 3.4.2 Assignee: Unassigned Created: 13/Feb/14 3:11 PM Fix Versions: 4.x Priority: Normal Reporter: Ethan Brown We noticed an increasing number of failures on the Windows 2008R2 spec box in Jenkins, and speculated this was due to memory pressure. The machine was bumped from 2GB to 4GB and the problems went away. It seems evident that despite our efforts to trigger Ruby garbage collection, that we are leaking memory that is causing issues when running these tests. This ticket is a bit vague, but an effort to better profile Puppet and search out memory allocation issues with a combination Windbg + debug versions of Ruby and/or the CRT is in order. See https://tickets.puppetlabs.com/browse/QA-836
Jira (PUP-1690) Enable easy deployment and configuration of package management via chocolatey on Windows
Title: Message Title Joshua Cooper created an issue Puppet / PUP-1690 Enable easy deployment and configuration of package management via chocolatey on Windows Issue Type: Epic Assignee: Unassigned Created: 13/Feb/14 3:55 PM Priority: Normal Reporter: Joshua 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/groups/opt_out.
Jira (PUP-1690) Chocolatey
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1690 Chocolatey Change By: Joshua Cooper Summary: EnableeasydeploymentandconfigurationofpackagemanagementviachocolateyonWindows Chocolatey EnableeasydeploymentandconfigurationofpackagemanagementviachocolateyonWindows 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/groups/opt_out.
Jira (PUP-401) Chocolatey package provider
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-401 Chocolatey package provider Change By: Joshua Cooper NeworexistingpackageproviderforWindowsthatreliesonchocolatey 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/groups/opt_out.
Jira (PUP-1691) Install chocolatey
Title: Message Title Joshua Cooper created an issue Puppet / PUP-1691 Install chocolatey Issue Type: New Feature Assignee: Unassigned Created: 13/Feb/14 3:58 PM Labels: windows chocolatey Priority: Normal Reporter: Joshua Cooper New or existing module for ensuring chocolatey itself is installed along with all dependencies, e.g. .NET. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1691) Install chocolatey
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1691 Install chocolatey Change By: Joshua Cooper Neworexistingmoduleforensuringchocolateyitselfisinstalledalongwithalldependencies,e.g..NET. Shouldalsoexposetheabilitytoconfigurechocolateyitself,e.g.whichfeedstopullfrom. 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Andrew Parker commented on an issue Re: Measure stat() calls Merged the benchmarking into stable (for 3.4.3) as 26e2bb9 Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access 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/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior puppetcla commented: CLA signed by all contributors. Add Comment PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior h2. The order of (keys m) and (vals m) is not guaranteed to be the same * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 857 Discussion|https://github.com/puppetlabs/puppetdb/pull/857] * [Pull Request 857 File Diff|https://github.com/puppetlabs/puppetdb/pull/857/files] h2. Pul... 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-1690) Chocolatey
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1690 Chocolatey Change By: Joshua Cooper Enable easydeployment versionable and configurationof upgradeableWindows packagemanagement via using chocolatey onWindows . 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/groups/opt_out.
Jira (PUP-1690) Chocolatey
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1690 Chocolatey Change By: Joshua Cooper Labels: windows 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/groups/opt_out.
Jira (PUP-401) Chocolatey package provider
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-401 Chocolatey package provider Change By: Joshua Cooper Issue Type: Bug NewFeature 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/groups/opt_out.
Jira (PUP-401) Chocolatey package provider
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-401 Chocolatey package provider Change By: Joshua Cooper NeworexistingpackageproviderforWindowsthatreliesonchocolatey .Thismayjustbegettinghttps://github.com/chocolatey/puppet-chocolateyontotheforge. 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/groups/opt_out.
Jira (PUP-401) Chocolatey package provider
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-401 Chocolatey package provider Change By: Joshua Cooper NeworexistingpackageproviderforWindowsthatreliesonchocolatey. Thismayjustbegetting Ithinkthecurrentcanonicalversionis https://github.com/chocolatey/puppet-chocolatey onto ,whichison theforge ashttp://forge . puppetlabs.com/rismoney/chocolatey. 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Andrew Parker commented on an issue Re: Measure stat() calls Merged performance fix for known_resource_types into stable (for 3.4.3) as 14f815 Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Henrik Lindberg commented on an issue Re: Measure stat() calls Fixes now on stable head reduced the amount of time for the two benchmarks many_modules, and defined_types to below what they were at the tag 3.4.2. These benchmark shows at least a 10% improvement. Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access 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/groups/opt_out.
Jira (PUP-751) Measure stat() calls
Title: Message Title Andrew Parker commented on an issue Re: Measure stat() calls I did some checks to make sure that this doesn't regress on any functionality that I could think of. The place to worry about is how the resource_type indirection handles reparsing. This should preserve the functionality from PUP-1322 , but more checks in that area would be good. There is an issue that I discovered, that I believe is not a regression. It is that when the initial import (the files pointed to by the manifest setting) have an error then the resource_type indirection still fails. This code path did not catch errors like the path that loads from modules. Add Comment Puppet / PUP-751 Measure stat() calls Better understanding of wasted filesystem access This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/243/ Add Comment PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior h2. The order of (keys m) and (vals m) is not guaranteed to be the same * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 857 Discussion|https://github.com/puppetlabs/puppetdb/pull/857] * [Pull Request 857 File Diff|https://github.com/puppetlabs/puppetdb/pull/857/files] h2. Pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (FACT-331) PR (637): Feature/facter 2/fact 322 remove special casing of empty string - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-331 PR (637): Feature/facter 2/fact 322 remove special casing of empty string - adrienthebo Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 13/Feb/14 4:17 PM Labels: github Priority: Normal Reporter: gepetto-bot Feature/facter 2/fact 322 remove special casing of empty string Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 637 Discussion Pull Request 637 File Diff Pull Request Description
Jira (PUP-1692) Allow types to specify required attributes
Title: Message Title Hunter Haugen created an issue Puppet / PUP-1692 Allow types to specify required attributes Issue Type: Improvement Assignee: Unassigned Created: 13/Feb/14 4:21 PM Priority: Normal Reporter: Hunter Haugen Currently with types in puppet, a developer can set a default value or not. If a efault is unset then the default is nil. As a developer, I often want types to be able to specify required attributes that do not have a default. Currently the only way to do this is in the global validate method which leads to inconsistent messages across modules. Could we get a way to make certain type attributes required? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-322) Remove special casing of the empty string
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-322 Remove special casing of the empty string Change By: Peter Huene Assignee: PeterHuene 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/groups/opt_out.
