Jira (PUP-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider
Title: Message Title Thomas Mueller commented on PUP-6552 Re: Regression: Redhat / Debian / Ubuntu can't specify 'init' provider Paul Anderson, Ben Hines: at least for RHEL7 and others with systemd I would not recommend to use init/redhat provider. There are some gotchas with SysV init-scripts and systemd. If a SysV service gets started outside of systemd, systemd alsways thinks it is stopped (because it doesn't know about) and report a wrong state. Standard init scripts on RHEL/Fedora source /etc/rc.d/init.d/functions.sh to automatically redirect to systemctl because of this - had some fun finding out that some 3rd party init scripts missing this. I would think about only setting provider where it is actually required (with maybe a selector https://docs.puppet.com/puppet/latest/lang_conditional.html#selectors). 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Eric Sorenson commented on PUP-6960 Re: Puppet language error during agent run (success during apply) Looks like Greg Swift ran into this too: https://www.botbot.me/freenode/theforeman-dev/2016-10-24/?msg=75395515=4 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title
Eric Sorenson commented on PUP-6960
Re: Puppet language error during agent run (success during apply)
Hunter Haugen suggested that a more reliable way to use resource references inside of types is like this, from the 'transition' module:
https://github.com/puppetlabs/puppetlabs-transition/blob/master/lib/puppet/type/transition.rb#L119
I had to use something like this in order to get at the resource:
newparam(:ca) do
validate do |value|
ca_resource = resource.catalog.resource(value.to_s)
if ca_resource && !ca_resource.is_a?(Puppet::Type::Ca)
raise ArgumentError, "Expected Ca resource, got #{ca_resource.class} #{ca_resource.inspect}"
end
end
end
This does (mostly) work, though I'm not sure it's the best way to do it. It is mysterious to me why nobody has seen/reported this error before, to us or upstream.
Jira (PUP-6962) Create Jenkins jobs for running puppet test tiers
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6962 Create Jenkins jobs for running puppet test tiers Change By: Geoff Nichols Sprint: AP Grooming 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-6850) Make commit formatting check robust
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6850 Make commit formatting check robust Change By: Josh Cooper Fix Version/s: PUP 4.7.1 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-6831) Change reverse.each to more efficient reverse_each
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6831 Change reverse.each to more efficient reverse_each Change By: Josh Cooper Labels: maintenance 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-6831) Change reverse.each to more efficient reverse_each
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-6831 Change reverse.each to more efficient reverse_each Change By: Josh Cooper Assignee: Josh Cooper 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-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider
Title: Message Title Ben Hines commented on PUP-6552 Re: Regression: Redhat / Debian / Ubuntu can't specify 'init' provider In my case i can change to 'redhat' to fix this, but reading this bug report, it sounds like Moses Mendoza is saying 'init' is no longer going to be supported on redhat. I suspect that's inaccurate. It's still listed on in the documentation: https://docs.puppet.com/puppet/latest/types/service.html#service-providers init Standard init-style service management. This seems like a major regression. If 'init' is just not going to be supported on redhat/debian/ubuntu it should probably just be removed... 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-5830) Remove crazy symlink behavior
Title: Message Title Moses Mendoza commented on PUP-5830 Re: Remove crazy symlink behavior Michael Smith mentioned he might be able to pick up some warnings / logs for these in puppet-maint 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-3640) Puppet 5.0 Changes
Title: Message Title Moses Mendoza commented on PUP-3640 Re: Puppet 5.0 Changes Chris Price looking at this to target for possible upcoming puppet 5 in spring 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-3640) Green: Puppet 5.0 Changes
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3640 Green: Puppet 5.0 Changes Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 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-3640) Puppet 5.0 Changes
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3640 Puppet 5.0 Changes Change By: Moses Mendoza Summary: Green: Puppet 5.0 Changes 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-3640) Puppet 5.0 Changes
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3640 Puppet 5.0 Changes Change By: Moses Mendoza Labels: maintenance 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Glenn Sarti assigned an issue to Unassigned Puppet / PUP-6474 Incorporate gettext_setup gem into puppet Change By: Glenn Sarti Assignee: Glenn Sarti 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-6840) Establish revert policy for failing changes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6840 Establish revert policy for failing changes Change By: Josh Cooper Fix Version/s: PUP 4.9.0 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-6797) service should check for smf service first
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6797 service should check for smf service first Change By: Moses Mendoza Story Points: 2 Fix Version/s: PUP 4.9.0 Sprint: AP 2016-12-14 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-6792) SMF should recursively enable services
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6792 SMF should recursively enable services Change By: Moses Mendoza Story Points: 2 Fix Version/s: PUP 4.9.0 Sprint: AP 2016-12-14 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-6793) pkg provider should be default for Solaris 12
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6793 pkg provider should be default for Solaris 12 Change By: Moses Mendoza Story Points: 2 Fix Version/s: PUP 4.9.0 Sprint: AP 2016-12-14 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-6796) Support setting/checking shell in user_role_add
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6796 Support setting/checking shell in user_role_add Change By: Moses Mendoza Story Points: 2 Fix Version/s: PUP 4.9.0 Sprint: AP 2016-12-14 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-6795) Solaris does not support gzipped man pages
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6795 Solaris does not support gzipped man pages Change By: Moses Mendoza Story Points: 2 Fix Version/s: PUP 4.9.0 Sprint: AP 2016-12-14 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-6792) SMF should recursively enable services
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6792 SMF should recursively enable services merged to master at https://github.com/puppetlabs/puppet/commit/a4bdc43722396455ddca08f72d9fe8aa0b332894 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-6797) service should check for smf service first
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6797 service should check for smf service first merged to master at https://github.com/puppetlabs/puppet/commit/a4bdc43722396455ddca08f72d9fe8aa0b332894 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-6795) Solaris does not support gzipped man pages
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6795 Solaris does not support gzipped man pages merged to master at https://github.com/puppetlabs/puppet/commit/a4bdc43722396455ddca08f72d9fe8aa0b332894 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-6793) pkg provider should be default for Solaris 12
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6793 pkg provider should be default for Solaris 12 merged to master at https://github.com/puppetlabs/puppet/commit/a4bdc43722396455ddca08f72d9fe8aa0b332894 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-6796) Support setting/checking shell in user_role_add
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6796 Support setting/checking shell in user_role_add merged to master at https://github.com/puppetlabs/puppet/commit/a4bdc43722396455ddca08f72d9fe8aa0b332894 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-6796) Support setting/checking shell in user_role_add
Title: Message Title Moses Mendoza commented on PUP-6796 Re: Support setting/checking shell in user_role_add note from PR: strictly speaking, the `user_role_add` provider inherits behavior that enables setting/checking shell, but it is implicit and fragile. 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza commented on PUP-4742 Re: Bring semantic_puppet library into Puppet sorry - wrong 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-4742
Bring semantic_puppet library into Puppet
Change By:
Moses Mendoza
Comment:
This has now caused CI to fail to build packages somehow - the packaging step is failing for puppet-agent/master: https://jenkins.puppetlabs.com/job/platform_puppet-agent_pkg-van-ship_daily-master/437/BUILD_TARGET=ubuntu-16.04-amd64,SLAVE_LABEL=beaker/console {code}09:48:44 Downloading file 'fast_gettext-1.1.0.gem' from url 'http://buildsources.delivery.puppetlabs.net/fast_gettext-1.1.0.gem'09:48:44 Verifying file: fast_gettext-1.1.0.gem against sum: 'fc0597bd4d84b749c579cc39c7ceda0f'09:48:44 An error was encountered evaluating block. Retrying..09:48:44 Downloading file 'gettext-setup-0.8.gem' from url 'http://buildsources.delivery.puppetlabs.net/gettext-setup-0.8.gem'09:48:44 Block failed maximum number of 1 tries09:48:44 with error Error: 404. Unable to get source from http://buildsources.delivery.puppetlabs.net/gettext-setup-0.8.gem09:48:44 Exiting...09:48:44 /var/lib/jenkins/workspace/platform_puppet-agent_pkg-van-ship_daily-master/BUILD_TARGET/ubuntu-16.04-amd64/SLAVE_LABEL/beaker/.bundle/gems/ruby/2.3.0/gems/vanagon-0.8.2/lib/vanagon/utilities.rb:155:in `retry_with_timeout'{code}This seems odd because the puppet component pipeline succesfully built packages
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
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Moses Mendoza Comment: sorry - wrong 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza commented on PUP-4742 Re: Bring semantic_puppet library into Puppet This has now caused CI to fail to build packages somehow - the packaging step is failing for puppet-agent/master: https://jenkins.puppetlabs.com/job/platform_puppet-agent_pkg-van-ship_daily-master/437/BUILD_TARGET=ubuntu-16.04-amd64,SLAVE_LABEL=beaker/console 09:48:44 Downloading file 'fast_gettext-1.1.0.gem' from url 'http://buildsources.delivery.puppetlabs.net/fast_gettext-1.1.0.gem' 09:48:44 Verifying file: fast_gettext-1.1.0.gem against sum: 'fc0597bd4d84b749c579cc39c7ceda0f' 09:48:44 An error was encountered evaluating block. Retrying.. 09:48:44 Downloading file 'gettext-setup-0.8.gem' from url 'http://buildsources.delivery.puppetlabs.net/gettext-setup-0.8.gem' 09:48:44 Block failed maximum number of 1 tries 09:48:44 with error Error: 404. Unable to get source from http://buildsources.delivery.puppetlabs.net/gettext-setup-0.8.gem 09:48:44 Exiting... 09:48:44 /var/lib/jenkins/workspace/platform_puppet-agent_pkg-van-ship_daily-master/BUILD_TARGET/ubuntu-16.04-amd64/SLAVE_LABEL/beaker/.bundle/gems/ruby/2.3.0/gems/vanagon-0.8.2/lib/vanagon/utilities.rb:155:in `retry_with_timeout'
Jira (PUP-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title Maggie Dreyer commented on PUP-6188 Re: Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings This passed CI at https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/276/. 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-6970) Add event list/calendar to Console for scheduling and forecasting
Title: Message Title Tim Purkerson created an issue Puppet / PUP-6970 Add event list/calendar to Console for scheduling and forecasting Issue Type: New Feature Assignee: Unassigned Created: 2016/12/02 9:48 AM Priority: Normal Reporter: Tim Purkerson Would like to add the potential for an event list/calendar to the Console where you can schedule events or provide forecasting. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6969) Add intentional changes with stats to the Events page
Title: Message Title Tim Purkerson created an issue Puppet / PUP-6969 Add intentional changes with stats to the Events page Issue Type: New Feature Assignee: Unassigned Created: 2016/12/02 9:45 AM Priority: Normal Reporter: Tim Purkerson Would like to be able to see past events (intentional changes) with stats like how many nodes affected/changed for this intentional change. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza commented on PUP-4742 Re: Bring semantic_puppet library into Puppet PA pipeline didn't trigger overnight, so kicked here: https://jenkins.puppetlabs.com/job/platform_puppet-agent_init-van-int_suite-daily-master/339/ 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Moses Mendoza commented on PUP-6777 Re: regression: incompatible character encodings: UTF-8 and ASCII-8BIT thanks for the note Angel L. Mateo 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-6968) puppet replaces line endings when creating files from epp template
Title: Message Title aft62562 created an issue Puppet / PUP-6968 puppet replaces line endings when creating files from epp template Issue Type: Bug Affects Versions: PUP 4.8.0 Assignee: Unassigned Components: Windows Created: 2016/12/02 8:06 AM Environment: Windows Server 2008 SP2 32bit Priority: Normal Reporter: aft62562 On Windows puppet replaces Windows line endings by Linux line endings when creating files from epp templates. This corresponds to https://tickets.puppetlabs.com/browse/PUP-927 which addressed the same issue for erb templates.
Jira (PUP-6494) exec resources leak the command string when execution fails
Title: Message Title Thomas Mueller commented on PUP-6494 Re: exec resources leak the command string when execution fails Brian Conner idea for a workaround: create a custom fact node_is_adjoined (boolean) and create the script which is called by exec only if it is false and remove the script if it is true. (still its a param). Or pre-create the ad computer object with a preshared-secret (maybe the mac address of the node, something derivable on the node itself but not known to the whole world) and use the computer account itself to join. 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-6494) exec resources leak the command string when execution fails
Title: Message Title Thomas Mueller commented on PUP-6494 Re: exec resources leak the command string when execution fails Brian Conner my comment was based on Josh Cooper's comment ", can we just not echo the executed command if the command fails?" and me thinking he meant that the command should by default not printed anymore when it fails. Most of the time it will be essential to know the exact command and only for (IMHO) very few cases where for example secrets are passed it's not desired. Another issue with passing a password in CLI is that it is available to everybody logged in with rights to view run "ps ef" (but as you running an AD join there wont be much users around). But the whole password/secrets story with Puppet is still bit tricky as things get probably stored at different places (PuppetDB, Agent cached catalog, log output, cached catalog on the server maybe, ...). I'd look forward to use this Sensitive type (and types in general). Unfortunatly still preparing the Puppet 4 upgrade. : / 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-6494) exec resources leak the command string when execution fails
Title: Message Title Henrik Lindberg commented on PUP-6494 Re: exec resources leak the command string when execution fails Brian Conner Using Sensitive is a half step - while the value is in clear text in the catalog, the fact that it is a sensitive value is kept and logic using it can do its best not to spill the secret. What we are also working on with a slightly longer fuse is the ability to have encrypted data, or handle to remote service like conjur. There is still the issue with a clear text value being needed at some point in the computation and the risk of spilling that secret. The pattern for that will follow that of Sensitive - that is, that you ask for the clear text value and use it in a very controlled manner. To get to that place we need to get a number of more general features in first - one that is now an experimental features "rich data in catalog" that can be played with, but is not production ready. The reason for this feature is that our current catalog can only send a particular set of data values to the agent. Best we can do at the moment is using the Sensitive data type. 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-6494) exec resources leak the command string when execution fails
Title: Message Title Brian Conner commented on PUP-6494 Re: exec resources leak the command string when execution fails Josh, that is a possibility, however, won't the password still be on the agent catalog, which isn't desired? Thomas, the command that prompted this ticket was adcli join, with the password. Any failing exec where the password has to be passed inline as a variable(eyaml or not) will do this. Henrik, I like this idea. Perhaps that could be further implemented on the agent side as well so that the password is a harmless hash on the stored catalog? I believe conjur does something along these lines, I did see it discussed elsewhere in the Puppet tickets. 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Angel L. Mateo commented on PUP-6777 Re: regression: incompatible character encodings: UTF-8 and ASCII-8BIT I'm having this same problem with puppet running on ubuntu server. I'm using now puppet-agent 4.8.1, but 4.8.0 has the problem too. 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Henrik Lindberg commented on PUP-6960 Re: Puppet language error during agent run (success during apply) From what I can tell it looks like there is a bug in the resource type "ca". I base that on: when using puppet apply, the values from the compilation are used in the resources created in the catalog. thus an attribute holding a reference to a Resource points to the actual resource when serializing that in a catalog, it gets serialized as something like "Ca[id]", a string the receiving end must know what to do with that string - this is for instance done automatically for the relationship meta parameters, but for other attributes that does not occur automatically. 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-6494) exec resources leak the command string when execution fails
Title: Message Title Henrik Lindberg commented on PUP-6494 Re: exec resources leak the command string when execution fails If the exec resource provider honoured the Sensitive bit, the command string could be given as a Sensitive value and it could then say "redacted" in the output. (Just an idea). 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-6950) scope.function_getparam does not work in ERB templates (future parser)
Title: Message Title Henrik Lindberg commented on PUP-6950 Re: scope.function_getparam does not work in ERB templates (future parser) Do look at the blog post I linked - it explains exactly how the queuing and lazy evaluation of "user defined resource type" kind of resources work. It is a very brittle design to rely on resources having been evaluated in a particular order. Classes on the other hand are stable, and they are evaluated directly, together with the classes they include in turn. You can certainly loop in your ERB. If you have the information in a variable in the class that holds the input of the 'severname' => 'ip' mapping, use that instead of trying to look that information up from the created resources. Then things will happen in the natural order. 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-6950) scope.function_getparam does not work in ERB templates (future parser)
Title: Message Title
Rowan Ruseler commented on PUP-6950
Re: scope.function_getparam does not work in ERB templates (future parser)
Henrik Lindberg, thanks once again.
What I notice is when I create a scope.lookupvar('foo::server'), it does load the 'server_name'. Kinda confused then why the scope.function_ does not. Or it does, but the servers::information is not yet been evaluated?
So I assume that this is what you wrote about 'order of evaluation'.
do as little as possible class servers::information has more server(s) then one, so I am unable to do that (well, my knowledge stops here - I can not find any documentation on how to do that). Can I create something like $server_name = "$ {server_id}
" within the ERB? That it looks up what specific 'server_id' - foo/foo2/etc and gets the correct value?
server { 'foo':
ip_address => "127.0.0.1",
}
server { 'foo2':
Jira (PUP-6494) exec resources leak the command string when execution fails
Title: Message Title Thomas Mueller commented on PUP-6494 Re: exec resources leak the command string when execution fails I see value in having the command shown on error by default. I'd normally want to know what exact command failed. I'd rather like some show_echo (or whatever name) param like the file types show_diff. So a user can define a resouce default or set it on specific resources. 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.
