Jira (PUP-8383) /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777'
Title: Message Title BellaX created an issue Puppet / PUP-8383 /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Catalog Application Created: 2018/01/23 10:03 PM Priority: Normal Reporter: BellaX Puppet Version: 5.3.3 Puppet Server Version: PE 2017.3 OS Name/Version: Ubuntu 16.4 'puppet agent -t' changed /opt/puppetlabs/puppet/cache/facts.d]/mode to 0777. This happens on nodes with no custom code yet. Here is the command line output: Info: Using configured environment 'production' Info: Retrieving pluginfacts Notice: /File[/opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Info: Retrieving plugin Info: Loading facts Info: Caching catalog for puppet.local Info: Applying configuration version '1516773686' Notice: Applied catalog in 11.56 seconds
Jira (FACT-1812) Bump facter version to 3.6.9
Title: Message Title Geoff Nichols created an issue Facter / FACT-1812 Bump facter version to 3.6.9 Issue Type: Task Assignee: Branan Riley Created: 2018/01/23 7:57 PM Fix Versions: FACT 3.6.9 Priority: Normal Reporter: Geoff Nichols 1) Check that the version number in source for facter is correct version for facter should be 3.6.9 check CMakeLists.txt for the project(FACTER VERSION X.Y.Z) variable check lib/Doxyfile for the PROJECT_NUMBER variable check locales/FACTER.pot for the Project-Id-Version variable Add Comment
Jira (PUP-8382) Bump puppet version to 4.10.10
Title: Message Title Geoff Nichols created an issue Puppet / PUP-8382 Bump puppet version to 4.10.10 Issue Type: Task Assignee: Branan Riley Created: 2018/01/23 7:57 PM Fix Versions: PUP 4.10.10 Priority: Normal Reporter: Geoff Nichols 1) Check that the version number in source for puppet is correct version for puppet should be 4.10.10 check lib/puppet/version.rb for the PUPPETVERSION variable check .gemspec for version variable Add Comment
Jira (PUP-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper commented on PUP-8368 Re: Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Patch works: $ ./ruby --version ruby 2.4.3p205 (2017-12-14 revision 61247) [x64-mingw32] $ ./ruby tcp.rb 証明書をリクエストできませんでした: getaddrinfo: そのようなホストは不明です。 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from
Jira (PUP-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title Maggie Dreyer commented on PUP-8226 Re: Warning in manifest causing invalid byte sequence error on Redhat 7 server Fix is in jruby-utils at https://github.com/puppetlabs/jruby-utils/pull/61 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Josh Cooper commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices Rick Sherman based on your comment "We're going to close this PR in favor of moving both apply and resource functionality directly into puppet device" I assume we can close the ticket too? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1329) composite namevars should be more robust
Title: Message Title Josh Cooper commented on PUP-1329 Re: composite namevars should be more robust Edwin Wiles It's possible to use title_patterns and a name namevar at the same time, see https://github.com/puppetlabs/puppetlabs-java_ks/blob/master/lib/puppet/type/java_ks.rb#L47-L62 and https://github.com/puppetlabs/puppetlabs-java_ks/blob/master/lib/puppet/type/java_ks.rb#L184-L207. Closing this ticket as won't fix. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8355) Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8355
Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results
Change By:
Josh Cooper
Acceptance Criteria:
Good morning,I've looked your service providers for both SysVinit and Systemd (Debian). In your implementation, you make use of *invoke-rc.d* command to know whether or not a service is enabled:# https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/debian.rb#L41# https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/systemd.rb#L104*Problem:* If the *policyrcd-script-zg2* package is installed, you will always get *104*, even for unknown services...*Howto reproduce**1.* Behavior without the *policyrcd-script-zg2* package installed:{code:bash}root@stretch:~# update-rc.d apache2 defaultsroot@stretch:~# update-rc.d apache2 disableinsserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5).insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6).root@stretch:~# invoke-rc.d --quiet --query apache2 startroot@stretch:~# echo $?101{code}That is the expected behavior.*2.* Behavior with the *policyrcd-script-zg2* package installed:{code:bash}root@stretch:~# update-rc.d apache2 defaultsroot@stretch:~# update-rc.d apache2 disableinsserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5).insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6).root@stretch:~# invoke-rc.d --quiet --query apache2 startroot@stretch:~# echo $?104{code}With dummy (inexistent) package:{code:bash}root@stretch:~# invoke-rc.d --quiet --query dummy startroot@stretch:~# echo $?104{code}From my point of view, you should just mimic Debian behavior as done in the systemd in the Debian /lib/systemd/systemd-sysv-install script:{code:bash}...is-enabled)# exit with 0 if $NAME is enabled, non-zero if it is disabledls $ROOT/etc/rc[S5].d/S??$NAME >/dev/null 2>/dev/null;;*)...{code}
Add Comment
Jira (PUP-8355) Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8355
Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results
Change By:
Josh Cooper
Good morning,I've looked your service providers for both SysVinit and Systemd (Debian). In your implementation, you make use of * Puppet Version: invoke-rc.d * command to know whether or not a service is enabled: *Puppet Server Version # https : * //github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/debian.rb#L41 *OS Name # https: / Version /github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/systemd.rb#L104*Problem :* If the *policyrcd-script-zg2* package is installed, you will always get *104*, even for unknown services... Describe your issue in as much detail as possible…Describe steps to *Howto reproduce … * * Desired 1.* Behavior : without the * policyrcd-script-zg2* package installed: {code:bash} root@stretch:~# update-rc.d apache2 defaults *Actual Behavior root@stretch : * ~# update-rc.d apache2 disable insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Please take a moment and attach any relevant log output and/or manifests root@stretch:~# invoke-rc . This will help us immensely when troubleshooting d --quiet --query apache2 startroot@stretch:~# echo $?101{code}That is the issue expected behavior . Examples *2.* Behavior with the *policyrcd-script-zg2* package installed : Run puppet agent with {code:bash}root@stretch:~# update - rc.d apache2 defaultsroot@stretch:~# update - test rc.d apache2 disableinsserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5).insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6).root@stretch:~# invoke - rc.d - trace - quiet - debug -query apache2 start root@stretch:~# echo $? Relevant sections of 104 { code}With dummy (inexistent) package: { /var/log/puppetlabs/puppetserver/puppetserver.log code:bash } } or any applicable logs from the same directory root@stretch:~# invoke-rc . d --quiet --query dummy start root@stretch:~# echo $? For more detailed information turn up 104{code}From my point of view, you should just mimic Debian behavior as done in the server logs by upping the log level systemd in the server's logback.xml Debian /lib/systemd/systemd-sysv-install script: {code:bash} Relevant sections of configurations files (puppet . conf, hiera . conf .is-enabled)# exit with 0 if $NAME is enabled , Server's conf non-zero if it is disabledls $ROOT/etc/rc[S5] .d , defaults / sysconfig) S??$NAME >/dev/null 2>/dev/null ;; For memory issues with server heap dumps are also helpful *) . .. {code}
Jira (PUP-8355) Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8355 Debian - SysVinit/Systemd service providers - Making use of the invoke-rc.d command to know whether or not a service is enabled can lead to unexpected results Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8234) layer 3 data sources can not be overriden for unit testing purposes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8234 layer 3 data sources can not be overriden for unit testing purposes Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8234) layer 3 data sources can not be overriden for unit testing purposes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8234 layer 3 data sources can not be overriden for unit testing purposes Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8370 puppet runs generate a misleading error when hiera-eyaml is configured but not installed Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8370 puppet runs generate a misleading error when hiera-eyaml is configured but not installed Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8284) i18n need to change "on node #{node}" code to be translation friendly
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8284
i18n need to change "on node #{node}" code to be translation friendly
Change By:
Josh Cooper
We need to change how we report the node that a message occurs on to be more translation friendly. Currently the common way is to say "on node # \ {node \ }". We should be more translation friendly about this.{ { noformat} 09:42 $ grep -r 'on node' liblib/puppet/defaults.rb:should be used on nodes running `puppet agent` or `puppet apply`.lib/puppet/error.rb: msg = "#{msg} on node #{node}" if nodelib/puppet/external/dot.rb:'fixedsize', # default: false; label text has no affect on node sizelib/puppet/parser/compiler.rb:message = "#{detail} on node #{node.name}"lib/puppet/util/log.rb: msg = _("%{msg} on node %{node}") % { msg: msg, node: node } unless node.nil? {noformat } }
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8284) i18n need to change "on node #{node}" code to be translation friendly
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8284
i18n need to change "on node #{node}" code to be translation friendly
Change By:
Josh Cooper
We need to change how we report the node that a message occurs on to be more translation friendly. Currently the common way is to say "on node #{node}". We should be more translation friendly about this. {noformat} 09:42 $ grep -r 'on node' liblib/puppet/defaults.rb:should be used on nodes running `puppet agent` or `puppet apply`.lib/puppet/error.rb: msg = "#{msg} on node #{node}" if nodelib/puppet/external/dot.rb:'fixedsize', # default: false; label text has no affect on node sizelib/puppet/parser/compiler.rb:message = "#{detail} on node #{node.name}"lib/puppet/util/log.rb: msg = _("%{msg} on node %{node}") % { msg: msg, node: node } unless node.nil? {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8284) i18n need to change "on node #{node}" code to be translation friendly
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8284
i18n need to change "on node #{node}" code to be translation friendly
Change By:
Josh Cooper
We need to change how we report the node that a message occurs on to be more translation friendly. Currently the common way is to say "on node #{node}". We should be more translation friendly about this.{ noformat} { 09:42 $ grep -r 'on node' liblib/puppet/defaults.rb:should be used on nodes running `puppet agent` or `puppet apply`.lib/puppet/error.rb: msg = "#{msg} on node #{node}" if nodelib/puppet/external/dot.rb:'fixedsize', # default: false; label text has no affect on node sizelib/puppet/parser/compiler.rb:message = "#{detail} on node #{node.name}"lib/puppet/util/log.rb: msg = _("%{msg} on node %{node}") % { msg: msg, node: node } unless node.nil? {noformat } }
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8380) Puppet considers plan with invalid parameter name as valid
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8380 Puppet considers plan with invalid parameter name as valid Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8380) Puppet considers plan with invalid parameter name as valid
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8380 Puppet considers plan with invalid parameter name as valid Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8371) YumRepo purge does not respect --noop
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8371 YumRepo purge does not respect --noop Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8238) Update lang spec with RichDataKey (and the LookupKey and LookupValue aliases)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8238 Update lang spec with RichDataKey (and the LookupKey and LookupValue aliases) Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8238) Update lang spec with RichDataKey (and the LookupKey and LookupValue aliases)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8238 Update lang spec with RichDataKey (and the LookupKey and LookupValue aliases) Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8372) Providers being loaded on masters
Title: Message Title Josh Cooper commented on PUP-8372 Re: Providers being loaded on masters I'm going to mark this as won't fix, as we have a recommended workflow for ensuring ruby types and providers are not loaded in the puppetserver runtime. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8371) YumRepo purge does not respect --noop
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8371 YumRepo purge does not respect --noop Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3814) Clean up tech debt around ResourceStores
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-3814 Clean up tech debt around ResourceStores Issue Type: Improvement Assignee: Unassigned Created: 2018/01/23 4:54 PM Priority: Normal Reporter: Zachary Kent Remove unused code in ResourceStore protocol Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-1948) Selboolean provider has a bug: private method `split' called for nil:NilClass
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-1948
Selboolean provider has a bug: private method `split' called for nil:NilClass
Change By:
Josh Cooper
If for some reason setsebool command takes too long to execute it is killed and following error appears in Puppet log: {noformat} sh: line 1: 5597 Killed /usr/sbin/setsebool -P rsync_export_all_ro on 2>&1Error: private method `split' called for nil:NilClassError: /Stage[main]/Main/Selboolean[rsync_export_all_ro]/value: change from off to on failed: private method `split' called for nil:NilClass {noformat} Puppet should process the exception above and give reasonable error message. Even better would be to have timeout parameter for selboolean resource.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-286 Clean up Bolt::Result ExecutionResult interface Change By: Michael Smith Sub-team: bolt Bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8381) modifycmd does not correctly catch and handle the `password_warn_days` option
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8381 modifycmd does not correctly catch and handle the `password_warn_days` option Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-308) Update writing plans docs for 0.15.0
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-308 Update writing plans docs for 0.15.0 Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8375) Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12)
Title: Message Title Branan Riley updated an issue Puppet / PUP-8375 Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12) Change By: Branan Riley Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Branan Riley updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Branan Riley Fix Version/s: PUP 4.10.10 Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8375) Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12)
Title: Message Title Branan Riley updated an issue Puppet / PUP-8375 Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12) Change By: Branan Riley Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Branan Riley updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Branan Riley Fix Version/s: PUP 4.10.z Fix Version/s: PUP 5.3.4 Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7608) Lookup unique merge doesn't deduplicate with a single layer
Title: Message Title Branan Riley updated an issue Puppet / PUP-7608 Lookup unique merge doesn't deduplicate with a single layer Change By: Branan Riley Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7507) puppet lookup --facts can't modify $facts hash
Title: Message Title Branan Riley updated an issue Puppet / PUP-7507 puppet lookup --facts can't modify $facts hash Change By: Branan Riley Fix Version/s: PUP 4.10.z Fix Version/s: PUP 5.3.4 Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8223) User and group modifications should respect forcelocal
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8223 User and group modifications should respect forcelocal Change By: Melissa Stone Release Notes Summary: When forcelocal is set to true, the groupadd and useradd modules now use local commands for modifying and deleting user and group resources. Prior to this, local commands were only used for adding group and user resources when forcelocal was set to true. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1792) Backport platform fact acceptance test changes from 3.9.x -> 3.6.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1792 Backport platform fact acceptance test changes from 3.9.x -> 3.6.x Change By: Branan Riley Fix Version/s: FACT 3.6.9 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1788) Facter acceptance test changes needed for el-7-aarch64
Title: Message Title Branan Riley updated an issue Facter / FACT-1788 Facter acceptance test changes needed for el-7-aarch64 Change By: Branan Riley Fix Version/s: FACT 3.6.9 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1811) Amazon Linux v2 os.release.full acceptance test fails - expecting "2.0"
Title: Message Title Branan Riley updated an issue Facter / FACT-1811 Amazon Linux v2 os.release.full acceptance test fails - expecting "2.0" Change By: Branan Riley Fix Version/s: FACT 3.6.9 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8223) User and group modifications should respect forcelocal
Title: Message Title Eric Delaney commented on PUP-8223 Re: User and group modifications should respect forcelocal Merged to master at https://github.com/puppetlabs/puppet/commit/45f72e8cac139c31dfae412628b19a7fdaec4dda Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP with bolt task, but works with bolt command Change By: Michael Smith Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-292) Allow run_* functions to set 'run-as' value
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-292 Allow run_* functions to set 'run-as' value Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Eric Delaney updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Eric Delaney THIS IS A CROSS TEAM EPIC - DO NOT PUT IN A SPRINT. EACH TEAM NEEDS SEPARATE EPIC SUPPORTING THIS.Sensitive information such as passwords or key files contained within Puppet catalogs leaks into locations such as PuppetDB or syslog. This elevates the necessary security that must be enforced on these external systems.It would be valuable to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which are sensitive. Components downstream from the catalog compiler could then choose how to handle sensitive data. For example, the master could redact such fields from the catalog before sending it to PuppetDB. The agent could be configured to obscure sensitive resource titles from the log when they are acted upon.One possible way to do this would be the addition of a "sensitive" resource type that is compiled into the catalog. Each instance would specific resource fields to be selected and the preferred means of redaction. These changes need to taken I18N support into consideration Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8381) modifycmd does not correctly catch and handle the `password_warn_days` option
Title: Message Title Melissa Stone created an issue Puppet / PUP-8381 modifycmd does not correctly catch and handle the `password_warn_days` option Issue Type: Bug Assignee: Unassigned Created: 2018/01/23 3:12 PM Priority: Normal Reporter: Melissa Stone *Puppet Version:4.10.x When modifying users and passing in `--warndays` (a feature introduced in https://github.com/puppetlabs/puppet/commit/31089218e84e898e4b2388bf1ed98e08bf892968), the useradd module does not correctly handle this flag. It is supposed to use either `usermod` or `chage` depending on which aspect it is modifying, but the regex set up to catch this misses the warn days scenario (https://github.com/puppetlabs/puppet/blob/4d96086ac88b34f3ed78d61a14e246016db22b17/lib/puppet/provider/nameservice/objectadd.rb#L16). Currently, it only catches and properly handles those flags that deal with password age. *Desired Behavior: When specifying option `:password_warn_days`, use command defined for `:password' or `:localpassword`. *Actual Behavior: When passing in `:password_warn_days`, command is set to `:modify` or `:localmodify`. Add Comment
Jira (PUP-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper commented on PUP-8368 Re: Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Ruby merged a fix upstream: https://github.com/ruby/ruby/commit/a41005eb6a99376ea940888bcf97140643d18f61. I'm trying a ruby build with that patch (against 2.4.3) to see if it resolves the issue. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8375) Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12)
Title: Message Title Josh Cooper commented on PUP-8375 Re: Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12) Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/49fb94be71fe4ff447d1cc521c2d1095787fb973 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-310) Update task-modules control repo for 0.15.0
Title: Message Title Alex Dreyer commented on BOLT-310 Re: Update task-modules control repo for 0.15.0 https://github.com/puppetlabs/task-modules/pull/12 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper commented on PUP-8368 Re: Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Same result on our French Windows image: PS C:\work\puppet> Get-WinSystemLocale LCID Name DisplayName --- 1036 fr-FRFrançais (France) PS C:\work\puppet> ruby .\tcp.rb ./tcp.rb:6:in `%': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError) from ./tcp.rb:6:in `rescue in ' from ./tcp.rb:3:in `'
Jira (FACT-1782) Facter.flush not working as expected in Facter 3.x
Title: Message Title Scott McClellan updated an issue Facter / FACT-1782 Facter.flush not working as expected in Facter 3.x Change By: Scott McClellan Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Scott McClellan updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Scott McClellan Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1743) Environment variable override for structured facts
Title: Message Title Scott McClellan assigned an issue to Larissa Lane Facter / FACT-1743 Environment variable override for structured facts Change By: Scott McClellan Assignee: Larissa Lane Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8380) Puppet considers plan with invalid parameter name as valid
Title: Message Title Michael Smith assigned an issue to Henrik Lindberg Puppet / PUP-8380 Puppet considers plan with invalid parameter name as valid Change By: Michael Smith Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Josh Cooper commented on PUP-8268 Re: Install packages using beaker-puppet's puppet5 methods Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/1c075d357ac3132228bced23e19e261d82468cf1 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8380) Puppet considers plan with invalid parameter name as valid
Title: Message Title
Michael Smith created an issue
Puppet / PUP-8380
Puppet considers plan with invalid parameter name as valid
Issue Type:
Bug
Affects Versions:
PUP 5.4.0
Assignee:
Unassigned
Created:
2018/01/23 2:12 PM
Priority:
Normal
Reporter:
Michael Smith
The Puppet parser appears to consider a plan with a parameter with a leading underscore as valid, such as
plan test::foo(String $_arg) { }
https://puppet.com/docs/puppet/5.3/lang_reserved.html#parameters notes them as invalid for classes and defined types. I would've expected plans to behave the same, and we have design assumptions around reserving leading underscore names for meta params to run_plan. So this plan (for example) would be unrunnable in Bolt.
Jira (PUP-8342) Add transaction_completed to schema
Title: Message Title Kris Bosland updated an issue Puppet / PUP-8342 Add transaction_completed to schema Change By: Kris Bosland Release Notes Summary: This change adds the new transaction_completed flag to the report schema for serialization/deserialization. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8342) Add transaction_completed to schema
Title: Message Title Kris Bosland commented on PUP-8342 Re: Add transaction_completed to schema Eric Delaney I added a comment. Let me know if you have any feedback. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8321) Update how warn_once and deprecation warnings print their location and i18n messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once and deprecation warnings print their location and i18n messages Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8322) 18n add string decorations to "raise EventLogError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8322 18n add string decorations to "raise EventLogError" call Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8340) Update Puppet::Resource::Catalog.alias to use Puppet::Util::Errors.error_location()
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8340 Update Puppet::Resource::Catalog.alias to use Puppet::Util::Errors.error_location() Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8342) Add transaction_completed to schema
Title: Message Title Eric Delaney commented on PUP-8342 Re: Add transaction_completed to schema Kris Bosland Can you add a release not for this if needed? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8347) Find more places where we report the file or line information and convert them to use error_location()
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8347 Find more places where we report the file or line information and convert them to use error_location() Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Kenn Hussey Fix Version/s: PUP 4.10.10 Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8252) re-enable i18n test after translation updated for 5.3.4 release
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8252 re-enable i18n test after translation updated for 5.3.4 release Change By: Eric Delaney QA Risk Assessment: Needs Assessment Automate Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8379) translation string uses wrong variable names
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8379 translation string uses wrong variable names Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Kenn Hussey Fix Version/s: PUP 4.10.z Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact because module expects openssl in the path Change By: Eric Delaney Acceptance Criteria: * update the module to always raise the error* update the tests test to run on solaris 10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact because module expects openssl in the path Change By: Eric Delaney Acceptance Criteria: * update the module to always raise the error* update the tests to run on solaris 10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8377
solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Change By:
Eric Delaney
The test tests/i18n/modules/puppet_apply_unsupported_lang.rb is intended to verify that we can get all warning and error messages when we ask for an unsupported language on the system. In this case even if you don't ask for a different language then the default, we don't see the 'raise' message we're expecting from the custom fact:{code} pfuqyhk1tw6udul.delivery.puppetlabs.net (solaris10-64-1) 08:49:51$ puppet apply -e "class { 'i18ndemo': filename => '/tmp/provider.LpaqLb' }"Warning: This method is deprecated, please use the stdlib validate_legacy function,with Stdlib::Compat::Absolute_Path. There is further documentation for validate_legacy function in the README. at ["/etc/puppetlabs/code/environments/production/modules/i18ndemo/manifests/init.pp", 15]: (at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in `deprecation')Warning: Scope(Class[I18ndemo]): Creating an i18ndemo fileNotice: Compiled catalog for pfuqyhk1tw6udul.delivery.puppetlabs.net in environment production in 0.06 secondsWarning: /Stage[main]/I18ndemo/File[/tmp/provider.LpaqLb]: Ensure set to :present but file type is directory so no content will be syncedNotice: Applied catalog in 0.02 seconds{code} This should contain this error:{code} assert_match The problem is that module is getting the openssl version available ( /Error: which there isn't one in the path on the solaris 10 boxes) . *i18ndemo_fact: this is a Since its its not set we don't raise from a custom fact from \w+-i18ndemo/, apply_result . stderr, 'missing untranslated message for We should change the module to always raise from ruby fact') an error and re-enable the test on solaris10 {code}
Add Comment
This message was sent by
Jira (PUP-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8377
solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Change By:
Eric Delaney
The test tests/i18n/modules/puppet_apply_unsupported_lang.rb is intended to verify that we can get all warning and error messages when we ask for an unsupported language on the system. In this case even if you don't ask for a different language then the default, we don't see the 'raise' message we're expecting from the custom fact:{code} pfuqyhk1tw6udul.delivery.puppetlabs.net (solaris10-64-1) 08:49:51$ puppet apply -e "class { 'i18ndemo': filename => '/tmp/provider.LpaqLb' }"Warning: This method is deprecated, please use the stdlib validate_legacy function,with Stdlib::Compat::Absolute_Path. There is further documentation for validate_legacy function in the README. at ["/etc/puppetlabs/code/environments/production/modules/i18ndemo/manifests/init.pp", 15]: (at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in `deprecation')Warning: Scope(Class[I18ndemo]): Creating an i18ndemo fileNotice: Compiled catalog for pfuqyhk1tw6udul.delivery.puppetlabs.net in environment production in 0.06 secondsWarning: /Stage[main]/I18ndemo/File[/tmp/provider.LpaqLb]: Ensure set to :present but file type is directory so no content will be syncedNotice: Applied catalog in 0.02 seconds{code}The problem is that module is getting the openssl version available (which there isn't one in the path on the solaris 10 boxes). Since its its not set we don't raise. {code}opensslv = Facter::Util::Resolution.exec('openssl version')raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') if opensslv{code} We should change the module to always raise an error and re-enable the test on solaris10
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title
Eric Delaney commented on PUP-8377
Re: solaris 10 doesn't show raise from custom fact because module expects openssl in the path
The underlying problem is actually with the module, its calling 'openssl' which isn't in the path on the solaris10 boxes so we don't get our raise and error:
opensslv = Facter::Util::Resolution.exec('openssl version')
raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') if opensslv
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-198) Publicize Use of puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-198 Publicize Use of puppet-strings Issue Type: Task Assignee: Unassigned Created: 2018/01/23 1:10 PM Priority: Normal Reporter: Eric Putnam Once we have puppet-strings ready to go, we need to let the community know what it is and how and where to use it. This will be in the form of a Puppet blog post and a similar post on the Forge. PDOC-187 PE-18596 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact because module expects openssl in the path Change By: Eric Delaney Sprint: Platform Core KANBAN Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact because module expects openssl in the path Change By: Eric Delaney Fix Version/s: PUP 5.3.4 Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact because module expects openssl in the path
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact because module expects openssl in the path Change By: Eric Delaney Summary: solaris 10 doesn't show raise from custom fact because module expects openssl in the path Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact
Title: Message Title Eric Delaney commented on PUP-8377 Re: solaris 10 doesn't show raise from custom fact Josh Cooper I've already skipped the test on solaris 10. The problem is that we don't get the error message at all on solaris 10 which isn't good (Regardless of the language settings). Error: Facter: error while resolving custom fact "i18ndemo_fact": i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo I've done some more testing and the rest of the test works correctly, but in the case where we're getting an error from Facter on the custom fact, it is getting lost somewhere. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8379) translation string uses wrong variable names
Title: Message Title Eric Delaney commented on PUP-8379 Re: translation string uses wrong variable names Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/2318501c6cf3ebee91a38eb462cde62896ea4ab5 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-197) Generate REFERENCE.md
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-197 Generate REFERENCE.md Issue Type: New Feature Assignee: Unassigned Created: 2018/01/23 11:54 AM Priority: Normal Reporter: Eric Putnam Related to PDOC-131 sort of. Instead of generating entire README, we've instead decided to compromise on a REFERENCE.md. This will be puppet-strings data in a format (markdown) that CS has said is valuable while taking a large burden off of the README. puppet-strings will need to be able to generate this markdown which will just be taking the Yard registries and organizing the data into acceptable looking markdown, in a file called REFERENCE.md. In the cli, we can either create a new --emit-markdown option or create a --format and use it for both json and markdown. Add Comment
Jira (PUP-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Michael Lombardi commented on PUP-8337 Re: Package source on Windows errors out on deduped installation files Merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/6b2d9027a9e6bc9dbe2113d654e96b8436ab75c9 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-183) Puppet Strings 2.0.0
Title: Message Title Eric Putnam updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 Change By: Eric Putnam Epic Name: Puppet Strings Next 2.0.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-183) Puppet Strings 2.0.0
Title: Message Title Eric Putnam updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 Change By: Eric Putnam The next steps to get strings to a state where we and the community agree it's actually complete.*This epic deals with puppet-strings directly, not Forge or other work.* See PF-1437 for Forge stuff. More details in this doc:https://docs.google.com/document/d/1Tj1Y_RxKzP5lGJKXwxQWzNpYu_wVMpYF4JTuhkc2oqw/edit Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-183) Puppet Strings 2.0.0
Title: Message Title Eric Putnam updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 Change By: Eric Putnam The next steps to get strings to a state where we and the community agree it's actually complete. *This epic deals with puppet-strings directly, not Forge or other work.* More details in this doc:https://docs.google.com/document/d/1Tj1Y_RxKzP5lGJKXwxQWzNpYu_wVMpYF4JTuhkc2oqw/edit Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact
Title: Message Title Josh Cooper commented on PUP-8377 Re: solaris 10 doesn't show raise from custom fact I'm not really concerned with i18n on Solaris 10. Can we just skip this test on that platform? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8265) Remove ExecutionResult and Target from Puppet core
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8265 Remove ExecutionResult and Target from Puppet core Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8363) Do not use system_uptime fact as a source of randomness in acceptance test
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8363 Do not use system_uptime fact as a source of randomness in acceptance test Change By: Josh Cooper Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8343) When enforcing String data type for a class param, a regex data type does not raise an error.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8343 When enforcing String data type for a class param, a regex data type does not raise an error. Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-277) SSL default makes winrm harder to use
Title: Message Title Zach Reichert assigned an issue to Unassigned Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8379) translation string uses wrong variable names
Title: Message Title Eric Delaney commented on PUP-8379 Re: translation string uses wrong variable names Larissa Lane This is the ticket that needs an update to the translation .po file for japanese Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8379) translation string uses wrong variable names
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8379
translation string uses wrong variable names
Change By:
Eric Delaney
The translations string for this japanese string is wrong, it uses the wrong variable name: {code} #: ../lib/puppet/error.rb:68 ../lib/puppet/parser/compiler.rb:39msgid "%{message} on node %{node}"msgstr "ノード%{node}の%{msg}" {code} so you end up with untranslated variable names:{code}Info: 設定された環境'puppet_agent_l4rs2vm1'を使用しています。Info: pluginfactsを取得しています。Info: pluginを取得しています。Info: localesを取得しています。Info: factsを読み込んでいます。Error: Facter: error while resolving custom fact "i18ndemo_fact": eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズですError: リモートサーバからカタログを取得できませんでした: SERVERのエラー500 : サーバエラー: ノード%{node}の%{msg}Warning: 失敗したカタログではキャッシュを使用できません。Error: カタログを取得できませんでした; 実行をスキップしています。{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-277) SSL default makes winrm harder to use
Title: Message Title Zach Reichert commented on BOLT-277 Re: SSL default makes winrm harder to use Alex Dreyer I just tested with whats on the master branch (0df4ad4f8eff1decce14ff9e1be6e4b8fa3a7bec). I'm not seeing an mention of `- insecure` when I attempt to run a plan over winrm without ` -insecure` [root@jglk6mp8lkkbjjn ~]# bolt plan run test::my_win_plan nodes=winrm://a096ly48bagmce7.delivery.puppetlabs.net,winrm://rjintdso3lglsox.delivery.puppetlabs.net --modulepath /tmp/C100554.g0DmW1/modules -u Administrator -p Qu@lity! --verbose Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. (at /usr/local/share/gems/gems/bolt-9.9.0df4ad4/vendored/puppet/lib/puppet.rb:130:in `') 2018-01-23T18:48:03.943247 INFO Bolt::Executor: Starting task /tmp/C100554.g0DmW1/modules/test/tasks/a_win.ps1 on ["winrm://a096ly48bagmce7.delivery.puppetlabs.net", "winrm://rjintdso3lglsox.delivery.puppetlabs.net"] 2018-01-23T18:48:13.984342 INFO Bolt::Executor: Ran task '/tmp/C100554.g0DmW1/modules/test/tasks/a_win.ps1' on 2 nodes with 2 failures Evaluation Error: Error while evaluating a Function Call, Plan aborted: run_task 'test::a_win' failed on 2 nodes at /tmp/C100554.g0DmW1/modules/test/plans/my_win_plan.pp:3:17
Jira (PUP-8379) translation string uses wrong variable names
Title: Message Title
Eric Delaney created an issue
Puppet / PUP-8379
translation string uses wrong variable names
Issue Type:
Bug
Affects Versions:
PUP 5.3.3
Assignee:
Eric Delaney
Created:
2018/01/23 10:49 AM
Fix Versions:
PUP 5.3.4, PUP 5.4.0
Priority:
Normal
Reporter:
Eric Delaney
The translations string for this japanese string is wrong, it uses the wrong variable name:
#: ../lib/puppet/error.rb:68 ../lib/puppet/parser/compiler.rb:39 msgid "% {message}
on node % {node}" msgstr "ノード%{node}
の% {msg}" so you end up with untranslated variable names:
Info:
Jira (PUP-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title Maggie Dreyer commented on PUP-8226 Re: Warning in manifest causing invalid byte sequence error on Redhat 7 server Perfect. Past Haus and I are going to do a bit of spelunking into the JRuby source today to try to track down KCode, but we might end up missing this release with that fix. If that's the case, I'll remove the fix version. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title
Eric Delaney commented on PUP-8226
Re: Warning in manifest causing invalid byte sequence error on Redhat 7 server
Maggie DreyerNow that we have translations this problem appears to have gone away.
SERVER_VERSION=5.1.5.SNAPSHOT.2018.01.23T0845 SHA=7a3bb579b8ef02da8a3c91fe6c34da1941e98c23 SUITE_VERSION=5.3.3.250.g7a3bb57
rq2jp5swsamc9w3.delivery.puppetlabs.net (centos7-64-1) 10:30:11$ env LANGUAGE="" LANG="ja_JP" puppet agent -t --server emku4vm6sz039rg.delivery.puppetlabs.net --environment puppet_agent_l4rs2vm1
Info: 設定された環境'puppet_agent_l4rs2vm1'を使用しています。
Info: pluginfactsを取得しています。
Info: pluginを取得しています。
Info: localesを取得しています。
Info: factsを読み込んでいます。
Error: Facter: error while resolving custom fact "i18ndemo_fact": eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズです
Error: リモートサーバからカタログを取得できませんでした: SERVERのエラー500 : サーバエラー: ノード%{node}の%{msg}
Warning: 失敗したカタログではキャッシュを使用できません。
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Michael Smith updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Michael Smith Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Michael Smith commented on PUP-6702 Re: Windows service in Paused state cannot be managed I'm not sure how to look into HEAT, but one of the things I notice with the installer from https://slproweb.com/products/Win32OpenSSL.html (which generally installs to C:\OpenSSL-Win32 or 64) is that it has a default option to Copy OpenSSL DLLs to the Windows system directory. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title
Adam Bottchen commented on PUP-1913
Re: Puppet user resource should respect the forcelocal option
Karthikeyan Kanagaraj The resource you outlined:
user { 'oracle': ensure => present, uid => '10', gid => '1002', groups => 'dba', expiry => absent, allowdupe => true, home => '/app/oracle', forcelocal => true, shell => '/usr/bin/ksh', }
is instructing Puppet to add the oracle user to the supplementary group "dba" and to set an infinite expiration. Unfortunately the lusermod command does not support adding users to supplementary groups or setting account expiry dates, only useradd supports those commands. In order to update the user provider to handle those cases, we would need the OS supplied tools to support them.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-309) Update hands on lab for 0.15.0
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-309 Update hands on lab for 0.15.0 Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-307) Standardize success and failure for plans
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-307 Standardize success and failure for plans Change By: David Kramer Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8377) solaris 10 doesn't show raise from custom fact
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8377 solaris 10 doesn't show raise from custom fact Change By: Eric Delaney Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8252) re-enable i18n test after translation updated for 5.3.4 release
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8252 re-enable i18n test after translation updated for 5.3.4 release Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-194) Gracefully handle Ctrl-C
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-194
Gracefully handle Ctrl-C
Change By:
David Kramer
If bolt is interrupted while executing a plan, it may generate a large stacktrace. For example, if you enter the WinRM password incorrectly, and then Ctrl-C. We should register signal handlers and gracefully exit.{noformat}bx bolt plan run sample::single_task nodes=xcp6ifv2b4xm8e1 --modules spec/fixtures/modules -k -u Administrator -p --transport winrmPlease enter your password:^Cbundler: failed to load command: bolt (/Users/josh/work/bolt/.bundle/bin/bolt)Interrupt: /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:84:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/executor/ruby_executor_service.rb:49:in `wait_for_termination' /Users/josh/work/bolt/lib/bolt/executor.rb:39:in `on' /Users/josh/work/bolt/lib/bolt/executor.rb:57:in `run_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:72:in `run_task_instance' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:47:in `run_named_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:46:in `block in call' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `call' /Users/josh/work/bolt/spec/fixtures/modules/sample/plans/single_task.pp:4:in `block in call_function' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `eval' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `block in call_function'
