Jira (PUP-5969) Include built-in resource types in resource profiling
Title: Message Title Matthaus Owens commented on PUP-5969 Re: Include built-in resource types in resource profiling Henrik Lindberg I haven't thought about this in about a year, so I imagine it can be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7337) PUP 4.9.4 interpolation doesn't work
Title: Message Title Matthaus Owens commented on PUP-7337 Re: PUP 4.9.4 interpolation doesn't work Henrik Lindberg I'm going to link it as related to https://tickets.puppetlabs.com/browse/PA-681 in that case Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Matthaus Owens commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() I've opened https://tickets.puppetlabs.com/browse/PA-681 and linked it to this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Matthaus Owens commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() Thomas Hallgren I think it probably makes more sense to add something to the puppet-agent packaging to HUP the server if it is present/running on package upgrades. I'll open a ticket in PA and link it to this one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Matthaus Owens commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() I was only able to reproduce this by starting puppetserver under puppet 4.7, and then updating it to 4.8 without restarting the server. I think the fix here is to HUP or restart puppetserver. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1054) Investigate OSX facter.jar problems
Title: Message Title Matthaus Owens commented on FACT-1054 Re: Investigate OSX facter.jar problems Michael Smith Would you prefer a new ticket or if i simply move this one? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1054) Investigate OSX facter.jar problems
Title: Message Title Matthaus Owens commented on FACT-1054 Re: Investigate OSX facter.jar problems Maggie Dreyer As Michael Smith noted, actually creating facter.jar on osx is desireable for running puppet-server from source for developers. So while FACT-1053 stopped the build errors, it won't help with the other thing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6684) Puppet agent run errors with `Could not run stack level too deep`
Title: Message Title Matthaus Owens assigned an issue to Daniel Lynch Puppet / PUP-6684 Puppet agent run errors with `Could not run stack level too deep` Change By: Matthaus Owens Assignee: Daniel Lynch Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6684) Puppet agent run errors with `Could not run stack level too deep`
Title: Message Title Matthaus Owens commented on PUP-6684 Re: Puppet agent run errors with `Could not run stack level too deep` Branan Riley These messages seem part of the failover work (and you touched this part of the code last). Do they make any sense to you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Matthaus Owens commented on PUP-6653 Re: Ruby types still loaded even when a PCore type is found /cc Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-6653 Ruby types still loaded even when a PCore type is found I've attached the build log from the jenkins job where it failed. Updating to the puppet-agent build with PUP-6650 fixed did not address the issue. Change By: Matthaus Owens Attachment: consoleText.txt Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Matthaus Owens commented on PUP-6653 Re: Ruby types still loaded even when a PCore type is found The module changes to support environment isolation have been reverted until this is resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Matthaus Owens commented on PUP-6042 Re: `puppet agent --test` does not override cached catalog behavior It would be sweet - use_cached_catalog would override the defaults present in -test. Failing that, it would be cool if puppet shouted loudly or failed if conflicting flags were present on the command line. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Matthaus Owens commented on PUP-6042 Re: `puppet agent --test` does not override cached catalog behavior I think this may have broken some file sync / direct puppet tests that leverage `puppet agent -t --use_cached_catalog` and assert that the config version hasn't changed. How do you recommend updating those tests to achieve the same effect? I guess I can just grab all of the test flags except --no-usecacheonfailure. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Matthaus Owens commented on PUP-6335 Re: Puppet OID listing should be shareable between Clojure and Ruby code The OIDs listed in oids.rb in puppet has only been updated 3 times since late 2013 (about once a year). For right now, it is probably sufficient to hold back the gag reflex and add some comments to both files indicating that when updating one, the other should also be updated. In order to actually lay down a file in puppet that was readable by puppetserver, puppetserver would need to know where the puppet code was laid down. It would require exposing a setting, and populating it at package time. Both of these aren't hard, but they don't seem worth the initial investment for a file that sees such infrequent changes. If we start to see more or more often changes to that data structure then we should certainly revisit this. Alternatively, if at some future date the location of puppet code on disk is exposed and populated as a setting, this task will be easily accomplished and the time investment would be totally worthwhile. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-6335 Puppet OID listing should be shareable between Clojure and Ruby code Change By: Matthaus Owens Sprint: Server Jade 2016- 08 07 - 10 27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-6335 Puppet OID listing should be shareable between Clojure and Ruby code Change By: Matthaus Owens Scope Change Category: Adopted Scope Change Reason: Out of sprint work, this is the next unblocked prioritized ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Matthaus Owens assigned an issue to Matthaus Owens Puppet / PUP-6335 Puppet OID listing should be shareable between Clojure and Ruby code Change By: Matthaus Owens Assignee: Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6399) puppet resource $type $thing shouldn't return non-zero if $thing doesn't exist
Title: Message Title Matthaus Owens created an issue Puppet / PUP-6399 puppet resource $type $thing shouldn't return non-zero if $thing doesn't exist Issue Type: Bug Affects Versions: PUP 4.2.3 Assignee: Unassigned Created: 2016/06/09 1:43 PM Priority: Normal Reporter: Matthaus Owens Puppet seems to behave very differently when querying some types from the command line for resources that don't exist. For example, on ubuntu 12.04... root@wzt7vze95hmfvb5:~# puppet resource service foo-bar Error: Could not run: Could not find init script or upstart conf file for 'foo-bar' root@wzt7vze95hmfvb5:~# echo $?
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Here is a simple test. puts "undef" == :undef puts :undef == "undef" puts "requiring puppet now" require 'puppet' puts "undef" == :undef puts :undef == "undef" On jruby 1.7.20, it returns... false false requiring puppet
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef A git bisect shows that https://github.com/puppetlabs/puppet/commit/1547756ad7caa5cb1f0add8161e51ac07f61bd67 is the commit that caused this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef This is still broken on stable with the fix for PUP-6321. Henrik Lindberg was your above output using apply or a master/agent? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Daniel Urist What version of puppet-agent is installed alongside your puppetserver? I presume from what I've seen that it is 1.5.0, but I'd love confirmation on that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Interesting that the behavior is different here between puppet apply and an agent run. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Eric0 Sorenson Kylo Ginsberg This looks related to PUP-6321 as it also affects undef. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Matthaus Owens Affects Version/s: SERVER 2.4.0 Affects Version/s: PUP 4.5.0 Component/s: Puppet Server Key: SERVER PUP - 1356 6336 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop recei
Jira (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title
Matthaus Owens created an issue
Puppet / PUP-6176
Behavior of undef in relationships has changed in master since 4.4.x
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/04/14 10:17 AM
Priority:
Normal
Reporter:
Matthaus Owens
Before (in puppet 4.4.1 and earlier), something like
puppet apply -e "user {'matthaus': ensure => present, notify => undef}"
Would work, but now it causes a compile error:
puppet apply -e "user {'matthaus': ensure => present, notify => undef}"
Error: No title provided and "" is not a valid resource reference on node wyclef-2.local
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Stefan Heijmans because the change in the PR I linked affects nearly all puppet http requests, it can't get merged as is. I think that leaves two possible workarounds for you. Carry the patch yourself from the PR in some manner Configure logback to the warn level for puppet-server. You could do that by changing the root level of INFO in logback.xml to WARN, or to only change puppet-server's loglevel add a line like to logback.xml Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ To add onto what Kevin Corcoran said, here is how puppet/syslog loglevels map to puppet-server/logback levels: Puppet/Syslog Puppet-Server/Logback - Trace Debug Debug InfoInfo Notice Info WarnWarn Error Error CriticalError Alert Error Emergency Error
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Stefan Heijmans I have a PR up with a fix for this. I was able to reproduce the issue with a variation on your file manifest. If you'd like to try out the patch from the PR, I'd love to know if it resolves the issue for you. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-6139 Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Change By: Matthaus Owens Affects Version/s: SERVER 2.3.1 Affects Version/s: SERVER 1.0.2 Component/s: Puppet Server Component/s: Puppet Server Key: SERVER PUP - 388 6139 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5482) Should a not found resource type be marked as such?
Title: Message Title
Matthaus Owens updated an issue
Puppet / PUP-5482
Should a not found resource type be marked as such?
Change By:
Matthaus Owens
Release Notes Summary:
A new setting has been added called always_retry_plugins. It defaults to true, which is generally the correct behavior for the agent. Puppetserver will set it to false to take advantage of some additional caching for failures during loading of types. Users that are using passenger will want to set this in their config.ru by adding a line such as { { code} Puppet[:always_retry_plugins] = false {code } } .The always_retry_plugins setting also replaces the always_cache_features setting, which is now deprecated. If users are setting always_cache_features to true, they will want to replace that with 'always_retry_plugins=false'.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5482) Should a not found resource type be marked as such?
Title: Message Title
Matthaus Owens updated an issue
Puppet / PUP-5482
Should a not found resource type be marked as such?
Change By:
Matthaus Owens
Release Notes Summary:
A new setting has been added called always_retry_plugins. It defaults to true, which is generally the correct behavior for the agent. Puppetserver will set it to false to take advantage of some additional caching for failures during loading of types. Users that are using passenger will want to set this in their config.ru by adding a line such as {{Puppet[:always_retry_plugins] = false}}.The always_retry_plugins setting also replaces the always_cache_features setting, which is now deprecated. If users are setting always_cache_features to true, they will want to replace that with 'always_retry_plugins=false'.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5482) Should a not found resource type be marked as such?
Title: Message Title Matthaus Owens commented on PUP-5482 Re: Should a not found resource type be marked as such? Kylo Ginsbergwill do. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4545) Too many restarts on interface changes for Fedora, RHEL, CentOS
Title: Message Title Matthaus Owens assigned an issue to Rick Sherman If users are seeing this they can drop a file with the following contents into /etc/NetworkManager/dispatcher.d/98-puppet so that puppet will restart on network changes. #!/bin/bash # # Restart puppet on network changes to pickup changes to /etc/resolv.conf if [ -f "/bin/systemctl" ] ; then [[ $2 =~ ^(up|down)$ ]] && /bin/systemctl try-restart puppet.service || : else [[ $2 =~ ^(up|down)$ ]] && /sbin/service puppet condrestart || : fi Puppet / PUP-4545 Too many restarts on interface changes for Fedora, RHEL,
Jira (PUP-5969) Include built-in resource types in resource profiling
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5969 Include built-in resource types in resource profiling Issue Type: Improvement Assignee: Unassigned Created: 2016/02/24 11:33 AM Priority: Normal Reporter: Matthaus Owens When adding profiling to the catalog indirector for static catalogs, I noticed that file resources were not included in the resource profiling that already existed. Notifies are similarly not included. Based on the comment/error messages in the evaluate method in parser/resource.rb (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/resource.rb#L73-L87), it seems likely that those resources are considered builtin and follow a different code path. It would be worthwhile to add profiling to whatever code path builtin resources take so that those resources can be profiled as well. Add Comment
Jira (PUP-5121) Add profiling for file inlining
Title: Message Title Matthaus Owens commented on PUP-5121 Re: Add profiling for file inlining I have a PR up at https://github.com/puppetlabs/puppet/pull/4702 that covers the majority of these metrics. The one missing element is it does not have a breakdown of postprocessing at all. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5885) Files with .. in the path anywhere cannot be used as file sources
Title: Message Title
Matthaus Owens created an issue
Puppet / PUP-5885
Files with .. in the path anywhere cannot be used as file sources
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/11 11:05 AM
Priority:
Normal
Reporter:
Matthaus Owens
The following resource does not work in puppet currently:
file {"/tmp/foo":
ensure => present,
source => 'puppet:///modules/foo..d/bar.txt',
}
Jira (PUP-5579) Puppet acceptance tests fail trying to stop puppet service
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5579 Puppet acceptance tests fail trying to stop puppet service Issue Type: Bug Assignee: Unassigned Attachments: jenkins_output_log.txt Created: 2015/12/04 1:53 PM Priority: Normal Reporter: Matthaus Owens The puppet server tests failed in one cell (centos 6 64-bit) this morning (http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppet-server_integration-system_no-conditional_full-2.1.x/22/) with an error stopping the puppet service. I don't know if this has been seen before in puppet's acceptance tests. A portion of the log is below, and the full log is attached. Checking the service on the machine returns the following: [root@j7kl5f3ljm8qwoi ~]# service puppet status puppet dead but subsys locked
Jira (PUP-4822) Regression PMT cannot connect to forge on OSX
Title: Message Title Matthaus Owens commented on PUP-4822 Re: Regression PMT cannot connect to forge on OSX Gandi was included in the most recent agent release. The full cert list included can be found at https://github.com/puppetlabs/puppet-ca-bundle/tree/1.0.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens commented on PUP-5386 Re: puppet and mco services not installed on SPARC / X86 Solaris 11 John Duarte Should I resolve this or leave it for you to resolve? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens commented on PUP-5386 Re: puppet and mco services not installed on SPARC / X86 Solaris 11 According to William Hopper, all is well here. The fix was merged into puppet-agent stable. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens assigned an issue to qa Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Status: Ready for Merge Test Assignee: Matthaus Owens qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens assigned an issue to Matthaus Owens Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Assignee: Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens assigned an issue to Matthaus Owens Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Assignee: Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Sprint: RE 2015-10-21 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Scope Change Reason: Blocking solaris 11 support. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens commented on PUP-5386 Re: puppet and mco services not installed on SPARC / X86 Solaris 11 Josh Cooper I opened a CPR ticket to track the vanagon defect, but I don't know about the puppet-agent bit. I'm not too fussed about where this ticket goes. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5386) puppet and mco services not installed on SPARC / X86 Solaris 11
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5386 puppet and mco services not installed on SPARC / X86 Solaris 11 Change By: Matthaus Owens Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1247) Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified.
Title: Message Title Matthaus Owens commented on FACT-1247 Re: Facter does not correctly compile on Ubuntu Vivid because the java dependencies are not correctly specified. The jar file is now present in stable builds... previous: dpkg --contents /opt/jenkins-builds/puppet-agent/1.2.5/artifacts/deb/vivid/PC1/puppet-agent_1.2.5-1vivid_i386.deb | grep jar now: dpkg --contents /opt/jenkins-builds/puppet-agent/bb3022fd4c4d7b4ab7132196/artifacts/deb/vivid/PC1/puppet-agent_1.2.5.78.gbb3022f-1vivid_i386.deb | grep jar -rw-r--r-- root/root 1908 2015-10-06 05:11 ./opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.jar Add Comment
Jira (FACT-1186) Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
Title: Message Title
Matthaus Owens commented on FACT-1186
Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
John Duarte Oh. Okay. Then...
pkg list | grep puppet | awk '{print $1}' | xargs pkg uninstall
should work.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1186) Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
Title: Message Title Matthaus Owens commented on FACT-1186 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Facter John Duarte But i think something like the following will be more appropriate: pkg list puppet-agent && pkg uninstall puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1186) Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
Title: Message Title
Matthaus Owens commented on FACT-1186
Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Facter
John Duarte Just the first line needs to change, the second should be fine.
pkg list | grep puppet-agent | awk '{print $1}' | xargs pkg uninstall
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Matthaus Owens commented on PUP-5264 Re: Agent service status wrong on CentOS 6 So the service provider on centos 6 relies on the status command to decide if the service is running. Because your puppet service is returning 2, puppet thinks it isn't running and tries to start it. So figuring out why the status command is returning 2 here is the key. Dead but subsys locked probably means the pidfile is empty. What are the contents of /var/run/puppetlabs/agent.pid ? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Matthaus Owens commented on PUP-5264 Re: Agent service status wrong on CentOS 6 Dirk Heinrichs I'm unable to reproduce this on a fresh centos 6 install. Can you add the output of `service puppet status` (as well as the return code) please? Also a run of `/opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=true --verbose --trace --debug` would be helpful to see what's going on. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1188) Get pre-suites working for AIX 5.3 (PowerPC) for Facter
Title: Message Title Matthaus Owens commented on FACT-1188 Re: Get pre-suites working for AIX 5.3 (PowerPC) for Facter John Duarte Yes, the rpms will be copied into the repos directory when the other rpm/deb repos are created. This will happen as a natural side effect of having AIX in the jenkins pipelines. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1241) Prefer puppet-agent's dmidecode to system
Title: Message Title Matthaus Owens created an issue Facter / FACT-1241 Prefer puppet-agent's dmidecode to system Issue Type: Bug Assignee: Unassigned Created: 2015/09/23 11:29 AM Priority: Normal Reporter: Matthaus Owens Puppet-agent has it's own version of dmidecode available. We should prefer this version to the system version. I think this mostly involves ensuring that we have /opt/puppetlabs/puppet/bin in our path first when searching for dmidecode and virt-what. Once this change is made, we can safely remove the dmidecode dependency from puppet-agent. Note: virt-what and dmidecode are only available on linux platforms. Add Comment This message was sent by Atlassian JIRA (v6.4.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens assigned an issue to qa Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Change By: Matthaus Owens Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Matthaus Owens Sprint: RE 2015-10-07 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens assigned an issue to Orion Poplawski Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Matthaus Owens Assignee: Ryan McKern Orion Poplawski Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Orion Poplawski I'm unable to reproduce this issue. Are these packages from fedora? Using Puppet Labs' puppet-agent packages on fedora 22 I don't see any old processes sticking around, it restarts just fine. I don't know what /usr/bin/start-puppet-agent is that is mentioned in the output above, but it could be preventing systemd from correctly identify the pid of the main process. Here is the output from my tests. [root@vgryvwpwlkjx7kt ~]# systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2015-09-16 13:13:32 PDT; 3min 13s ago Main PID: 9248 (puppet) CGroup: /system.slice/puppet.service └─9248 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize Sep 16 13:13:32 vgryvwpwlkjx
Jira (PUP-5251) Packages pushed
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5251 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed. Dependencies:
Jira (PUP-5248) Smoke test packages
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5248 Smoke test packages Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. When a
Jira (PUP-5241) Is the code ready for release?
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5241 Is the code ready for release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%221.2.5%22
Jira (PUP-5252) Docs pushed
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5252 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5242) Reconcile git commits and JIRA tickets
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5242 Reconcile git commits and JIRA tickets Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier release (stable), but the ticket's fixVersion is not updated.
Jira (PUP-5243) Update version number in source
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5243 Update version number in source Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PUP-5250) Push tag
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5250 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian J
Jira (PUP-5247) Tag the release and create packages
Title: Message Title
Matthaus Owens created an issue
Puppet / PUP-5247
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/09/15 11:29 AM
Priority:
Normal
Reporter:
Matthaus Owens
Tag and create packages
Developer provides the SHA - Kylo Ginsberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-5244) Merge master into stable
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5244 Merge master into stable Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (PUP-5245) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5245 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PUP-5246) Prepare long form release notes and short form release story
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5246 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5240) puppet-agent 1.2.5 2015-09-16 Release
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5240 puppet-agent 1.2.5 2015-09-16 Release Issue Type: Task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens puppet-agent 1.2.5 2015-09-16 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PUP-5253) Send out announcements
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5253 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependencies:
Jira (PUP-5249) Go/no-go meeting (before 4pm)
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5249 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Kylo Ginsberg Nicholas Fagerlund Eric Sorenson John Duarte Melissa Stone
Jira (PUP-5254) Close all resolved tickets in Jira
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5254 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/09/15 11:29 AM Priority: Normal Reporter: Matthaus Owens Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%221.2.5%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-5071) Problems with puppet-agent Debian uninstall
Title: Message Title Matthaus Owens commented on PUP-5071 Re: Problems with puppet-agent Debian uninstall Awesome Christopher Wood, thanks for confirming. I'll go ahead and close this out then. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5071) Problems with puppet-agent Debian uninstall
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5071 Problems with puppet-agent Debian uninstall Change By: Matthaus Owens Fix Version/s: puppet-agent 1.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Change By: Matthaus Owens Scope Change Reason: I was near this code already with solaris 11 work so I just did it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Change By: Matthaus Owens Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Issue Type: Bug Affects Versions: puppet-agent 1.2.4 Assignee: Matthaus Owens Created: 2015/09/11 11:38 AM Priority: Normal Reporter: Matthaus Owens The ca cert bundle that comes with el4 does not have the forge root cert, which results in errors such as: [root@b8bm4bwebgqq9x4 ~]# /opt/puppetlabs/puppet/bin/puppet module search apt Notice: Searching https://forgeapi.puppetlabs.com ... Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com
Jira (PUP-5194) Investigate CI failures Sept 3 re puppetserver not starting
Title: Message Title Matthaus Owens commented on PUP-5194 Re: Investigate CI failures Sept 3 re puppetserver not starting Kylo GinsbergI'm pretty sure this is due to the master->stable merge yesterday. There are 2 commits that weren't on puppet stable that affect install.rb behavior (and add a flag). It looks as though install.rb stops parsing flags once it finds a flag it doesn't recognize, and because --no-check-prereqs appears before the --siteruby flag, it is not honored. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5124) Puppet does not wait for resources before parsing provider
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-5124 Puppet does not wait for resources before parsing provider Change By: Matthaus Owens Component/s: vagrant Workflow: Release Engineering Scrum Team Workflow Key: CPR PUP - 211 5124 Project: Community Package Repository Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5071) Problems with puppet-agent Debian uninstall
Title: Message Title Matthaus Owens commented on PUP-5071 Re: Problems with puppet-agent Debian uninstall John Miller I don't have a timeline for the next agent release here but @kylo might have a better idea. It looks like 1.2.1 suffers from the same script problem for jessie. If you want to try out a fixed build while waiting for an official release, our nightlies repositories have builds. http://nightlies.puppetlabs.com/puppet-agent-latest/ has an apt repo config for jessie at http://nightlies.puppetlabs.com/puppet-agent-latest/repo_configs/deb/pl-puppet-agent-latest-jessie.list Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5071) Problems with puppet-agent Debian uninstall
Title: Message Title Matthaus Owens commented on PUP-5071 Re: Problems with puppet-agent Debian uninstall Kylo Ginsberg This was a vanagon bug with systemd on jessie/debian. Fixed in a recent vanagon release and will be fixed in the next agent release. I've linked an associated RE bug. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5051) install.rb should support installations where facter/hiera may not be present
Title: Message Title Matthaus Owens commented on PUP-5051 Re: install.rb should support installations where facter/hiera may not be present Yea i think just resolving it is probably fine. if we've seen the agent pass against master, this should be fine. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1167) No ipaddress fact available for solaris 10
Title: Message Title Matthaus Owens commented on FACT-1167 Re: No ipaddress fact available for solaris 10 Here is debug output: root@builder-s10sparc2:~# /opt/puppetlabs/puppet/bin/facter -d ipaddress 2015-08-19 17:33:05.941748 INFO puppetlabs.facter - executed with command line: -d ipaddress. 2015-08-19 17:33:05.946625 INFO leatherman.ruby:136 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2". 2015-08-19 17:33:05.967031 INFO leatherman.ruby:157 - using ruby version 2.1.6 2015-08-19 17:33:06.050228 INFO puppetlabs.facter - requested queries: ipaddress. 2015-08-19 17:33:06.050726 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.0.2". 2015-08-19 17:33:06.053062 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts. 2015-08-19 17:33:06.053494 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory 2015-08-19 17:33:06.053705 DEBUG puppetlabs.facter - skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory
Jira (FACT-1167) No ipaddress fact available for solaris 10
Title: Message Title Matthaus Owens created an issue Facter / FACT-1167 No ipaddress fact available for solaris 10 Issue Type: Bug Assignee: Unassigned Created: 2015/08/19 5:10 PM Priority: Normal Reporter: Matthaus Owens Most of the networking facts work fine for solaris 10, but there is no ipaddress fact currently. root@builder-s10sparc2:~# /opt/puppetlabs/puppet/bin/facter ipaddress root@builder-s10sparc2:~# /opt/puppetlabs/puppet/bin/facter networking
Jira (FACT-1122) NXOS builds failing on stable of puppet-agent
Title: Message Title Matthaus Owens commented on FACT-1122 Re: NXOS builds failing on stable of puppet-agent So to bring this to more of a close, TERM is passed along on the ssh connection via vanagon. The failure case here was when TERM was set to xterm-256color and the success case was just xterm. When TERM is xterm-256color, it looks like python --version passes along escape sequences or control characters that make cmake choke. Vanagon should probably be unsetting TERM before rolling a build. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5051) install.rb should support installations where facter/hiera may not be present
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5051 install.rb should support installations where facter/hiera may not be present Issue Type: Improvement Assignee: Matthaus Owens Created: 2015/08/18 12:51 PM Priority: Normal Reporter: Matthaus Owens There are often cases where it is desirable to build puppet without having facter or hiera in place, while still ensuring that they will be in place at runtime. This comes into play in a cross-compile situation where the ruby being used to install may not be the ruby that will run puppet and also in the situation where native facter hasn't been compiled yet. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1124) Facter segfaults on el4
Title: Message Title Matthaus Owens commented on FACT-1124 Re: Facter segfaults on el4 Kylo Ginsberg We need to ticket the work on our end I believe. Then there should be a ticket or tickets to block on. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'
Title: Message Title
Matthaus Owens commented on PUP-4941
Re: Reserve keywords 'application', 'consumes', and 'produces'
on el6, I'm not seeing any warnings generated. I get a syntax error with the future parser, and no change with 3.x parser.
[root@jixh53ns9hrbnpc ~]# puppet apply -e 'class application { notify {$osfamily:}} include application' --parser=future
Error: Could not parse for environment production: Syntax error at 'application' at line 1:7 on node jixh53ns9hrbnpc.delivery.puppetlabs.net
Error: Could not parse for environment production: Syntax error at 'application' at line 1:7 on node jixh53ns9hrbnpc.delivery.puppetlabs.net
and
[root@jixh53ns9hrbnpc ~]# puppet apply -e 'class application { notify {$osfamily:}} include application'
Notice: Compiled catalog for jixh53ns9hrbnpc.delivery.puppetlabs.net in environment production in 0.03 seconds
Notice: RedHat
Notice: /Stage[main]/Application/Notify[RedHat]/message: defined 'message' as 'RedHat'
Jira (FACT-1154) $::rubysitedir pointing to wrong directory.
Title: Message Title Matthaus Owens commented on FACT-1154 Re: $::rubysitedir pointing to wrong directory. Ah yes. Good times. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora
Title: Message Title Matthaus Owens updated an issue Facter / FACT-1152 facter partitions don't work on Centos 4/5, sles10, fedora Change By: Matthaus Owens Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1155) Failing facter tests on solaris 10 i386
Title: Message Title Matthaus Owens commented on FACT-1155 Re: Failing facter tests on solaris 10 i386 I got green builds of agent on solaris off of a recently promoted facter today. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4864) Get pre-suites working for Fedora 22
Title: Message Title Matthaus Owens commented on PUP-4864 Re: Get pre-suites working for Fedora 22 There will almost certainly be permissions issues with ship and repo, but it won't hurt to try and see what blows up. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1156) Solaris 10 builds throw warnings, core dump when built without Debug
Title: Message Title Matthaus Owens updated an issue Facter / FACT-1156 Solaris 10 builds throw warnings, core dump when built without Debug Change By: Matthaus Owens Scope Change Reason: Found solaris work, blocking agent builds. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1156) Solaris 10 builds throw warnings, core dump when built without Debug
Title: Message Title Matthaus Owens updated an issue Facter / FACT-1156 Solaris 10 builds throw warnings, core dump when built without Debug Change By: Matthaus Owens Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
