Jira (PUP-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title
Alexander Pyhalov commented on PUP-8077
Re: terminus is undefined in lib/puppet/indirector/indirection.rb
Now I'm puzzled even more:
With
def terminus_class unless @terminus_class Puppet.debug("In terminus_class self.terminus_setting is # {self.terminus_setting}
") if setting = self.terminus_setting Puppet.debug("setting is # {setting}
") self.terminus_class = Puppet.settings[setting] puts("after Puppet.settings") Puppet.debug("terminus_class is # {self.terminus_class}
") else Puppet.debug("No terminus class nor terminus setting was provided for indirection # {self.name}") raise Puppet::DevError, "No terminus class nor terminus setting was provided for indirection #{self.name}
" end end Puppet.debug(" in terminus_class @terminus_class is # {@terminus_class}
") @terminus_class end
I receive
Debug: in Puppet::Network::HTTP::API::IndirectedRoutes before allow_remote_requests test indirection is # Debug: In terminus_class self.terminus_setting is node_terminus Debug: setting is node_terminus In value_sym param=node_terminus v=plain Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Finished adding entry 'production' (ttl = 0 sec) ^CNotice: Caught INT; exiting
It seems the master is about to return from value("node_terminus") and never does it
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
Jira (PUP-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title
Alexander Pyhalov commented on PUP-8077
Re: terminus is undefined in lib/puppet/indirector/indirection.rb
Hi. I'm trying to investigate puppet master hang. The root issue is the following. When I puppet agent connects to master (both 4.10.6 or 4.10.8), it receives no reply and both (master and agent hang). It looks the following way (I've added some debug printing to existing methods). From master side:
{{Notice: Starting Puppet master version 4.10.8 Debug: in terminus() terminus_name is ca Debug: in terminus() terminus_name is ca Debug: Routes Registered: Debug: Route /^\/puppet\// Debug: Route /^\/puppet-ca\// Debug: Route /.*/ Debug: /usr/ruby/2.3/lib/ruby/vendor_ruby/2.3.0/puppet/network/http/webrick/rest.rb:48:in `synchronize' /usr/ruby/2.3/lib/ruby/vendor_ruby/2.3.0/puppet/network/http/webrick/rest.rb:48:in `service' /usr/ruby/2.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service' /usr/ruby/2.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run' /usr/ruby/2.3/lib/ruby/vendor_ruby/2.3.0/puppet/network/http/webrick.rb:33:in `block (2 levels) in listen' /usr/ruby/2.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread' Debug: Processing request Debug: Processed request GET /puppet/v3/node/buildzone.oi-build.r61.net Debug: Evaluating match for Route /^\/puppet\// Debug: Request.routing_path = /puppet/v3/node/buildzone.oi-build.r61.net Debug: Evaluating match for Route /v3/ Debug: Request.routing_path = v3/node/buildzone.oi-build.r61.net Debug: processing route # Debug: (?-mix:v3) Debug: Evaluating match for Route /^\/environments$/ Debug: Request.routing_path = /node/buildzone.oi-build.r61.net Debug: Did not match path "/node/buildzone.oi-build.r61.net"EOL Debug: Evaluating match for Route /^\/environment\/[^\/]+$/ Debug: Request.routing_path = /node/buildzone.oi-build.r61.net Debug: Did not match path "/node/buildzone.oi-build.r61.net"EOL Debug: Evaluating match for Route /.*/ Debug: Request.routing_path = /node/buildzone.oi-build.r61.net Debug: processing route # Debug: (?-mix:.*) Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Finished adding entry 'production' (ttl = 0 sec) Info: access[/puppet/v3/environments]: allowing 'method' find Info: access[/puppet/v3/environments]: allowing * access Info: access[^/puppet/v3/catalog/([^/]+)$]: allowing 'method' find Info: access[^/puppet/v3/catalog/([^/]+)$]: allowing $1 access Info: access[^/puppet/v3/node/([^/]+)$]: allowing 'method' find Info: access[^/puppet/v3/node/([^/]+)$]: allowing $1 access Info: access[^/puppet/v3/report/([^/]+)$]: allowing 'method' save Info: access[^/puppet/v3/report/([^/]+)$]: allowing $1 access Info: access[/puppet/v3/file]: allowing * access Info: access[/puppet/v3/status]: allowing 'method' find Info: access[/puppet/v3/status]: allowing * access Info: access[/puppet-ca/v1/certificate_revocation_list/ca]: allowing 'method' find Info: access[/puppet-ca/v1/certificate_revocation_list/ca]: allowing * access Info: access[/puppet-ca/v1/certificate/ca]: adding authentication any Info: access[/puppet-ca/v1/certificate/ca]: allowing 'method' find Info: access[/puppet-ca/v1/certificate/ca]: allowing * access Info: access[/puppet-ca/v1/certificate/]: adding authentication any Info: access[/puppet-ca/v1/certificate/]: allowing 'method' find Info: access[/puppet-ca/v1/certificate/]: allowing * access Info: access[/puppet-ca/v1/certificate_request]: adding authentication any Info: access[/puppet-ca/v1/certificate_request]: allowing 'method' find Info: access[/puppet-ca/v1/certificate_request]: allowing 'method' save Info: access[/puppet-ca/v1/certificate_request]: allowing * access Info: access[/]: adding authentication any Debug: in Puppet::Network::HTTP::API::IndirectedRoutes before allow_remote_requests
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Larissa Lane commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread Thanks for the updated description Maggie Dreyer 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-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: Geoff Nichols Sprint: Platform OS 2017-10-31 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-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Casey Williams updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: Casey Williams Summary: Facter acceptance tests error fail printing a boost::optional on Solaris 10 x86_64 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-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Moses Mendoza Release Notes: New Feature 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-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Moses Mendoza Team: Platform OS Core 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-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Moses Mendoza Release Notes Summary: Puppet now supports the payload_gpgcheck option to yum. 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Change By: Moses Mendoza Team: Platform OS Core 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Change By: Moses Mendoza Sprint: Platform OS Community PR Core KANBAN 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-7292) Allow to set password warning days for user type
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-3262) By default, the cadir should be separated from the ssldir
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-3262 By default, the cadir should be separated from the ssldir Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: It would be good to have something which automatically backs up this directory as we see a support case where someone has deleted their CAdir every few weeks. Lacking that no putting the CAdir in the same place as the ssldir would be a good step. While we have worked to change the docs to say customers should move this dir there is advice elsewhere on the internet saying to delete it.Customers who do not have a backup are faced with a pretty big task of rekeying all of their agents. While bolt can help with this if the customer has setup ssh keys(many do not or do not want to), tasks in PE can't because they rely on this same SSL infrastructure. CS Severity: 4 - Major CS Business Value: 5 - $$ CS Frequency: 1 - 1-5% of Customers Add Comment
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Moses Mendoza Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22 , Platform Core KANBAN 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-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Change By: Moses Mendoza Team: Platform Core 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Moses Mendoza Team: Platform OS Core 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Moses Mendoza Team: Platform OS Core 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Team: Platform OS Core 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Release Notes Summary: Puppet now correctly uses the `-V` flag to set volsize property when creating a zfs volume. Previously it would pass this property via `-o`, which was incorrect and failed. 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Sprint: Platform Core KANBAN 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Assignee: Eric Sorenson 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza commented on PUP-3713 Re: Allow zfs to create a zvol merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/b4038629e300ab73147b5a62ea9ed1f0b9c45107 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Release Notes: Bug Fix 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.3 Fix Version/s: PUP 4.10.9 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-3713) Allow zfs to create a zvol
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Moses Mendoza Team: Platform OS Core 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-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7987 Add support to defined top scope variables to the Pal API Change By: Eric Sorenson Fix Version/s: BOLT 0.6.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 (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: This issue can cause troubleshooting a failed upgrade to take most of a day. This is a poor experience for our customers especially those who consider PE a critical service. It also leads to a very poor support experience when customers have to wait 4 hours to get final results that the upgrade failed. CS Severity: 4 - Major CS Business Value: 5 - $$ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8068) Use Puppet.lookup to resolve executor
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-8068 Use Puppet.lookup to resolve executor Change By: Eric Sorenson Fix Version/s: BOLT 0.6.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-8040) Puppet does not initialize I18N locale per thread
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8040
Puppet does not initialize I18N locale per thread
Change By:
Maggie Dreyer
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-choose-text-domain-and-locale-for-translation- The locale should be negotiated at every module load, contrary to what this says: https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/gettext/config.rb#L83-L84 (watch out for performance implications) but the translation repositories should only needed to be loaded once. We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, [ticket to be filed]). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3630) Configurable facts blacklist
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3630 Configurable facts blacklist Change By: Russell Mull Fix Version/s: PDB 5.1.2 Fix Version/s: PDB 4.4.2 Fix Version/s: PDB 4.2.3.6 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Release Notes Summary: Puppet will now accept a regex to match against a fact value for the `defaultfor` method of providers. (Associated puppet-docs PR has been opened) 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Release Notes: New Feature 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Labels: help_wanted puppethack 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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6452 Allow defaultfor to accept regex Change By: Moses Mendoza Fix Version/s: PUP 5.4.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-6452) Allow defaultfor to accept regex
Title: Message Title Moses Mendoza commented on PUP-6452 Re: Allow defaultfor to accept regex merged to master at https://github.com/puppetlabs/puppet/commit/e182a5bef16c9f73ad3d0b262a667fcd3f0fc22b 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-8071) Class documentation for PBinaryType is copy/pasted and incorrect
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8071 Class documentation for PBinaryType is copy/pasted and incorrect Change By: Thomas Hallgren Release Notes: Not Needed 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-8071) Class documentation for PBinaryType is copy/pasted and incorrect
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8071 Class documentation for PBinaryType is copy/pasted and incorrect Change By: Thomas Hallgren QA Risk Assessment: Needs Assessment No Action 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-8071) Class documentation for PBinaryType is copy/pasted and incorrect
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8071 Class documentation for PBinaryType is copy/pasted and incorrect Change By: Thomas Hallgren Method Found: Needs Assessment Inspection 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-8071) Class documentation for PBinaryType is copy/pasted and incorrect
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8071 Class documentation for PBinaryType is copy/pasted and incorrect Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-8071) Class documentation for PBinaryType is copy/pasted and incorrect
Title: Message Title Thomas Hallgren commented on PUP-8071 Re: Class documentation for PBinaryType is copy/pasted and incorrect Merged to 5.3.x at 1d35d06. 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-8070) cannot extract partial result from errors in plans
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8070 cannot extract partial result from errors in plans Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-8046) Tasks with an ensure parameter cause plan failure
Title: Message Title Jean Bond updated an issue Puppet / PUP-8046 Tasks with an ensure parameter cause plan failure Change By: Jean Bond Labels: resolved-issue-added 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 (PDB-3727) (maint) Update version determination
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3727 (maint) Update version determination Issue Type: Bug Assignee: Unassigned Created: 2017/10/19 1:14 PM Priority: Normal Reporter: gepetto-bot With the move to the new ezbake packaging, we've fixed a long-standing bug where we had packages with the same name but different content as we didn't include the codename in the release field. This however breaks the method of puppetdb installations, so update the version determination. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Eric Delaney commented on PUP-8039 Re: Puppet 4.10.x: Only warn once when gettext cannot be found Tested with SUITE_VERSION=1.10.8.55.g8cc295f SERVER_VERSION=2.8.0 SHA=8cc295fa39ff6fa53d3045c5f1ecd8ea312e1db7 passes 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 (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Charlie Sharpsteen CS Priority: Needs Priority 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Eric Sorenson commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Yes, that would be completely insane. The current behavior w/ normal 4.x functions is also insane, and if we can fix both at once so much the better. 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-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title Eric Sorenson assigned an issue to Alexander Pyhalov Puppet / PUP-8077 terminus is undefined in lib/puppet/indirector/indirection.rb Change By: Eric Sorenson Assignee: Eric Sorenson Alexander Pyhalov 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-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title Eric Sorenson commented on PUP-8077 Re: terminus is undefined in lib/puppet/indirector/indirection.rb Can you explain a bit more what the error you saw was, and why this change fixes it? This part of the codebase is central to how puppet works and hasn't changed in many years so I'm surprised there would be a new problem with it. I'm going to put this ticket in "Needs Info" and assign it to you, please put it back in "open" and assign to me after adding the requested information. 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-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-8077
terminus is undefined in lib/puppet/indirector/indirection.rb
Change By:
Eric Sorenson
It seems that code in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/indirection.rb#L177 is incorrect.I suppose, {code} def allow_remote_requests?terminus.allow_remote_requests? end {code} should have been something like {code} def allow_remote_requests?term = terminus(cache_class)term.allow_remote_requests?end {code} Found this while debugging more complex issue with Puppet master on OpenIndiana.
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-1253) systemd service provider should support masking
Title: Message Title John Florian commented on PUP-1253 Re: systemd service provider should support masking FYI, systemd < 235 is affected by https://github.com/systemd/systemd/issues/6412 which causes systemctl unmask to fail if the service unit being enabled/started is a template instance. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Moses Mendoza Release Notes Summary: The " base " service provider for the Service resource would previously fail with a stacktrace if the `ps` command produced process line for any output that did given service contained UTF-8 characters and puppet was not conform running in UTF-8, causing service checks to the character encoding that the Puppet agent was using fail . Bytes that don't compose puppet will now attempt to convert the PS output to UTF-8, and on failure force valid interpretation by replacing invalid UTF-8 are now removed from `ps` characters with replacement characters. This allows puppet to correctly match the running UTF-8 service in PS output before to the result is searched for matching command names managed service name . 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Charlie Sharpsteen Release Notes Summary: The "base" provider for the Service resource would fail if the `ps` command produced any output that did not conform to the character encoding that the Puppet agent was using. Any bytes Bytes that don't compose to valid UTF-8 are now removed from `ps` output before and the result is searched for matching command names. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Charlie Sharpsteen Release Notes Summary: The "base" provider for the Service resource would fail if the `ps` command produced any output that did not conform to the character encoding that the Puppet agent was using. Any bytes that don't compose to valid UTF-8 are now scrubbed removed from `ps` output before and the result is searched for matching command names. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Charlie Sharpsteen Release Notes Summary: The "base" provider for the Service resource would fail if the `ps` command produced any output that did not conform to the character encoding that the Puppet agent was using. Bytes that don't compose to valid UTF-8 are now removed from `ps` output before and the result is searched for matching command names. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Charlie Sharpsteen Release Notes Summary: The "base" provider for the Service resource would fail if the `ps` command produced any output that did not conform to the character encoding that the Puppet agent was using. Any bytes that don't compose to valid UTF-8 are now scrubbed from `ps` output before and the result is searched for matching command names. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Moses Mendoza Release Notes: Not Needed Bug Fix 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/74ff444293ac19d6150e5d694e8610b60d5c4343 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Moses Mendoza Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22 , Platform Core Hopper 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Moses Mendoza Fix Version/s: PUP 5.y Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.3 Fix Version/s: PUP 4.10.9 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
Jira (PUP-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Change By: Moses Mendoza Release Notes Summary: Puppet now correctly defaults to using DNF for the package provider on Fedora 26. 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Moses Mendoza Release Notes Summary: Previously, puppet could not manage the equivalent of the "zoned" property on FreeBSD, because the equivalent property name is "jailed". This has been fixed. 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-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Change By: Moses Mendoza Release Notes: Bug Fix 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Moses Mendoza Release Notes: Bug Fix 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Moses Mendoza Release Notes Summary: Previously, puppet would fail to persist mount options when remounting a mount resource on AIX. This has been fixed. 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Moses Mendoza Release Notes: Bug Fix 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-1781) Facter acceptance tests error on Solaris 10 x86_64
Title: Message Title Casey Williams commented on FACT-1781 Re: Facter acceptance tests error on Solaris 10 x86_64 Looks like this is somehow now happening everywhere: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_pkg-van-ship_daily-master/197/console There were new tests added to facter recently that cause Catch to try and fail to print a boost::optional. Here's an example from the most recent run on el7: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_pkg-van-ship_daily-master/BUILD_TARGET=el-7-x86_64,SLAVE_LABEL=beaker/197/console This seems easy enough to fix; I want to do a few test builds, but I should have a PR up today. 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Release Notes Summary: Previously, puppet was unable to effectively manage the SELinux file context without restarting the puppet service due to an infinitely cached default context for each file. Now puppet will clear this cache after obtaining it. This does come with a performance cost for managed files on an selinux-enabled host. If users discover that the performance cost is too great for their individual environment, setting selinux_ignore_defaults => true in the file resource or as a default for file resources will disable the behavior that incurs the performance cost - namely, whether puppet will try to manage SELinux labels 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-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Maggie Dreyer assigned an issue to Eric Delaney Puppet / PUP-8039 Puppet 4.10.x: Only warn once when gettext cannot be found Change By: Maggie Dreyer Assignee: Maggie Dreyer Eric Delaney 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Release Notes: Bug Fix 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-7292) Allow to set password warning days for user type
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: Moses Mendoza Fix Version/s: PUP 5.4.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-7292) Allow to set password warning days for user type
Title: Message Title Moses Mendoza commented on PUP-7292 Re: Allow to set password warning days for user type merged to master at https://github.com/puppetlabs/puppet/commit/e9a2db43912f72a0ded0067c8d77cbe0e962dc7c 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-7292) Allow to set password warning days for user type
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: Moses Mendoza Team: Platform OS Core 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-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney commented on PUP-8029
Re: Concatenated strings causing breakages with Japanese
[centos@ericdelaney puppet]$ find lib -type f -print | xargs grep '_(' | grep '<<'
lib/puppet/face/module/uninstall.rb: Puppet.notice _("Preparing to uninstall '%{name}'") % { name: name } << (options[:version] ? " (#{colorize(:cyan, options[:version].sub(/^(?=\d)/, 'v'))})" : '') << " ..."
lib/puppet/face/module/list.rb:str << ' ' + colorize(:red, _('invalid'))
lib/puppet/face/module/list.rb: str << ' ' + colorize(:red, _('invalid'))
lib/puppet/forge/errors.rb: message = _(<<-EOS).chomp % { uri: @uri, response: @response }
lib/puppet/forge/errors.rb: message << _("\n The message we received said '%{message}'") % { message: @message } if @message
lib/puppet/module_tool/errors/installer.rb: message << _("Could not install module '%{module_name}' (%{version})") % { module_name: @module_name, version: @requested_version }
lib/puppet/module_tool/errors/installer.rb: message << _(" Module '%{module_name}' (%{version}) is already installed") % { module_name: @module_name, version: @installed_version }
Jira (PUP-8029) Concatenated strings causing breakages with Japanese
Title: Message Title
Eric Delaney commented on PUP-8029
Re: Concatenated strings causing breakages with Japanese
/puppet/syntax_checkers/base64.rb
if (cleaned_text.bytes.to_a.size * 8) % 6 != 0
msg2 = _("padding is not correct")
else
msg2 = _("contains letters outside strict base 64 range (or whitespace)")
end
msg = _("Base64 syntax checker: Cannot parse invalid Base64 string - %{msg2}") % { msg2: msg2 }
Add Comment
Jira (PUP-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Jean Bond commented on PUP-8056 Re: Error type docs show new from hash - does not work as intended Resolved issue added for Bolt docs, but it looks like this will also need release notes in Puppet 5.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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Team: Platform OS Core 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Fix Version/s: PUP 4.10.9 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.3 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Moses Mendoza commented on PUP-2169 Re: Not possible to manage SELinux file contexts via puppet in a sane way merged to puppet/4.10.x at https://github.com/puppetlabs/puppet/commit/3eff4193ed5620ae88feaf5850f1d94f625225c4 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-7966) Enable Coverity scanning on puppetlabs/puppet
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-7966 Enable Coverity scanning on puppetlabs/puppet Change By: Daniel Dreier Sprint: WHO 2017-02-23 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-7966) Enable Coverity scanning on puppetlabs/puppet
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-7966 Enable Coverity scanning on puppetlabs/puppet Change By: Daniel Dreier Sprint: WHO 2017-02-23 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-7966) Enable Coverity scanning on puppetlabs/puppet
Title: Message Title Timur Kiykioglu updated an issue Puppet / PUP-7966 Enable Coverity scanning on puppetlabs/puppet Change By: Timur Kiykioglu Team: Web/Hosted Operations Sprint: WHO 2017-02-23 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-1782) Facter.flush not working as expected in Facter 3.x
Title: Message Title Martin Ewings updated an issue Facter / FACT-1782 Facter.flush not working as expected in Facter 3.x Change By: Martin Ewings Method Found: Needs Assessment Customer Feedback 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-6355) Review page: Troubleshooting Puppet for Windows
Title: Message Title Michael Lombardi commented on PUP-6355 Re: Review page: Troubleshooting Puppet for Windows Unfortunately, my current knowledge of puppet + beartraps isn't strong enough to answer the comment-questions in the doc. For example: > and Windows nodes subsequently can't connect to the master? -> Everything else looks good to me though! 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-1782) Facter.flush not working as expected in Facter 3.x
Title: Message Title Sean Millichamp created an issue Facter / FACT-1782 Facter.flush not working as expected in Facter 3.x Issue Type: Bug Affects Versions: FACT 3.6.6 Assignee: Unassigned Created: 2017/10/19 9:12 AM Priority: Normal Reporter: Sean Millichamp Calling Facter.flush to clear out resolved values during unit testing does not seem to work in Facter 3.6. Facter.clear does, but then affects the ability to get correct coverage reports from tools like SimpleCov, as Facter.clear reloads the entire fact, not just clearing the value. I have put a very simple reproducer here: https://github.com/seanmil/facter_flush_reproducer If you run it initially with Facter 3.6.6 two of the tests fail, due to Facter.flush not clearing out a previously resolved value from the prior test run. If you then uncomment gem 'facter' from the Gemfile and re-run it with Facter 2.5.1 available all tests pass, showing Facter.flush working as expected. Add Comment
Jira (PUP-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title Alexander Pyhalov created an issue Puppet / PUP-8077 terminus is undefined in lib/puppet/indirector/indirection.rb Issue Type: Bug Affects Versions: PUP 4.10.6 Assignee: Eric Sorenson Components: Community Created: 2017/10/19 9:09 AM Environment: SunOS ... 5.11 illumos-69e7133115 i86pc i386 i86pc Solaris ruby 2.3.5p376 (2017-09-14 revision 59905) [i386-solaris2.11] Priority: Minor Reporter: Alexander Pyhalov It seems that code in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/indirection.rb#L177 is incorrect. I suppose, def allow_remote_requests? terminus.allow_remote_requests? end should have been something like def allow_remote_requests? term = terminus(cache_class) term.allow_remote_requests? end Found this while debugging more complex issue with Puppet master on OpenIndiana.
Jira (PDB-3726) (maint) Update rust-opensll and hyper dependencies
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3726 (maint) Update rust-opensll and hyper dependencies Issue Type: Bug Assignee: Unassigned Created: 2017/10/19 8:49 AM Priority: Normal Reporter: gepetto-bot This commit also fixes up a CI issue that was created as part of a previous revert. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3725) puppetdb.conf tweak to remove old values
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3725 puppetdb.conf tweak to remove old values Issue Type: Bug Assignee: Unassigned Created: 2017/10/19 7:06 AM Priority: Normal Reporter: gepetto-bot Make sure puppetdb.conf contains correct entries depending on the terminus version Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-588) Removing calling_module breaks perfectly valid usage
Title: Message Title Joerg Jaspert created an issue Hiera / HI-588 Removing calling_module breaks perfectly valid usage Issue Type: Bug Assignee: Unassigned Created: 2017/10/19 5:19 AM Priority: Major Reporter: Joerg Jaspert Hi removing the calling_module pseudo variable in favor of "use the module layer" is very short sighted and actively breaks perfectly nice and valid configs, please undo. First off - as long as the hiera thingie runs in compat v3 mode, it should work, no matter what puppet version, as its part of v3. Then, even when using v4 or later, it should work. The module layer is NOT an option to replace what calling_module gave. The module layer is for the module author, which, in many cases, is NOT the one maintaining the local puppet. Using calling_module variable in hiera enables a LOCAL module layer of config option, that is entirely independent of the things that the module author wants to do. My practical example: I do have a 53layer hierarchy here, with widespread use of calling_module included. The biggest user of that are the firewalls and sudo modules, in which, as you may guess, we locally configure the firewall and sudo entities for the machine. Which are highly dependent on our local environment. So nothing at all the module author ever wants (or needs to) resemble. Their hierarchy basically boils down to "nodename, osfamily, common" and is fine for configuring things like executable and config file path entries. Our hierarchy includes tons of layers of local definitions derived from variables (function of machine, network name machine is in, custom facts adapted to our env, etc. pp). This is NOT at all representable with the 3 shallow levels now offered. It does not belong into the module, as its not from the module author, it is not
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Added this to PUP-8072 epic "ScriptMerge" as we there want to break out the bolt functions from puppet to bolt and it will be unfriendly to then require that every module with plans need to make a dependency on the bolt supplied "special internal" module. 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-8076) language specification needs to be updated with changes from feature_puppet-tasks
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8076 language specification needs to be updated with changes from feature_puppet-tasks Issue Type: Task Assignee: Unassigned Created: 2017/10/19 4:45 AM Priority: Normal Reporter: Henrik Lindberg As we have made changes to the language and introduced new data types we must update the language specification to be on par with the implementation. While there are currently some subtasks associated with tickets for features on the feature branch, those may not be complete which means that: a review must be made of what we added must be done, adding tickets for spec work where required complete the specification update tickets (This work is basically due to "scrambling to be finished for puppet conf") Add Comment
Jira (PUP-8075) tickets merged from feature branch should be made up to date
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8075 tickets merged from feature branch should be made up to date Issue Type: Task Assignee: Unassigned Created: 2017/10/19 4:41 AM Priority: Normal Reporter: Henrik Lindberg The tickets for commits on the feature_puppet-tasks branch should be made up to date wrt. puppet release version and release notes. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8074) Make trial merge of feature_puppet-tasks branch and run acceptance
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8074 Make trial merge of feature_puppet-tasks branch and run acceptance Issue Type: Task Assignee: Unassigned Created: 2017/10/19 4:37 AM Priority: Normal Reporter: Henrik Lindberg Before merge, a green acceptance run of the merged result is needed. Technically, the feature branch should be up to date with master being merged into the feature branch and a merge into master should be a simple operation. It therefore seems that an acceptance run on a build of puppet from the feature branch should be enough. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8073) (Re)move the execution functions from puppet (to a "module" in bolt)
Title: Message Title Henrik Lindberg commented on PUP-8073 Re: (Re)move the execution functions from puppet (to a "module" in bolt) Marking as blocked by BOLT-185 since the addition to bolt should be made before removing the functions from puppet. First adding them to bolt means that when added they will not be in effect until they are removed from puppet. (In contrast, done in the reverse order things would break). 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-8073) (Re)move the execution functions from puppet (to a "module" in bolt)
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8073 (Re)move the execution functions from puppet (to a "module" in bolt) Issue Type: Task Assignee: Unassigned Created: 2017/10/19 4:24 AM Priority: Normal Reporter: Henrik Lindberg The functions: run_task run_plan run_script run_command file_upload Should move from the puppet repo to bolt. This ticket is about removing the functions in puppet. There is a corresponding ticket for Bolt to add them there. Both these tickets must be done at the same time. Add
