Jira (PUP-8053) Links should point and reference Japanese versions
Title: Message Title Brett Gray created an issue Puppet / PUP-8053 Links should point and reference Japanese versions Issue Type: Bug Assignee: Garrett Guillotte Created: 2017/10/13 7:06 PM Priority: Normal Reporter: Brett Gray On https://puppet.com/ja/docs/pe/2017.3/release_notes/new_features.html#-02 the menu item refers to docs.puppet.com and puppet.com/docs. These should be doc.puppet.com/ja and puppet.com/ja/docs respectively Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8052) Menu Item リリースノート gets a 404
Title: Message Title Brett Gray created an issue Puppet / PUP-8052 Menu Item リリースノート gets a 404 Issue Type: Bug Assignee: Garrett Guillotte Created: 2017/10/13 7:02 PM Priority: Normal Reporter: Brett Gray In the left hand menu when clicking リリースノート the returned page is a 404. The link is https://puppet.com/ja/docs/pe/2017.3/release_notes Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8051) puppet agent option to wait for lock
Title: Message Title Daniel Parks created an issue Puppet / PUP-8051 puppet agent option to wait for lock Issue Type: New Feature Assignee: Unassigned Created: 2017/10/13 3:23 PM Priority: Normal Reporter: Daniel Parks Please add an option to make puppet agent wait for the lock to become available and then run. As is I often end up retrying multiple times, or setting up a while loop to check for the presence of the lock file. For example, puppet agent --waitforlock --test or puppet agent -Wt. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8050) puppet agent -e environment
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-8050
puppet agent -e environment
Change By:
Daniel Parks
Please add a {{ \ -e}} short option for {{puppet agent}} that corresponds to {{--environment}}. We (and likely many other people) running {{puppet agent -t --environment myenv}} many times per day.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8050) puppet agent -e environment
Title: Message Title Daniel Parks created an issue Puppet / PUP-8050 puppet agent -e environment Issue Type: Improvement Affects Versions: PUP 5.3.1 Assignee: Unassigned Created: 2017/10/13 3:19 PM Priority: Normal Reporter: Daniel Parks Please add a e short option for puppet agent that corresponds to -environment. We (and likely many other people) running puppet agent -t --environment myenv many times per day. Add Comment
Jira (PUP-8038) rubocop-i18n GetText/DecorateString needs to be more selective
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8038 rubocop-i18n GetText/DecorateString needs to be more selective Change By: Eric Delaney Summary: rubocop-i18n GetText/DecorateString is broken needs to be more selective Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8046) Tasks with an ensure parameter cause plan failure
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8046 Tasks with an ensure parameter cause plan failure Change By: Henrik Lindberg Release Notes Summary: Data types that had parameters, attributes or functions named the same as ruby keywords were not handled correctly as the generated code for such data types would result in ruby syntax errors. As an example a task could not have a parameter named 'ensure' because of this problem. This is now fixed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8046) Tasks with an ensure parameter cause plan failure
Title: Message Title Henrik Lindberg commented on PUP-8046 Re: Tasks with an ensure parameter cause plan failure Merged to 5.3.x branch Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza commented on PUP-7781 Re: yumrepo don't support payload_gpgcheck option merged to master at https://github.com/puppetlabs/puppet/commit/7fd083ea3d60f73664dcf51e0f69fb10b1ad32a6 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7781) yumrepo don't support payload_gpgcheck option
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7781 yumrepo don't support payload_gpgcheck option Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7886) Resolve several AAA and TACACS failures in Cisco pipeline
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-7886 Resolve several AAA and TACACS failures in Cisco pipeline Change By: John Duarte Assignee: Erik Dasher John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3713) (maint) Update version determination
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3713 (maint) Update version determination Issue Type: Bug Assignee: Unassigned Created: 2017/10/13 11:19 AM Priority: Normal Reporter: gepetto-bot With the move to the new ezbake packaging, we've fixed a long-standing bug where we had packages with the same name but different content as we didn't include the codename in the release field. This however breaks the method of puppetdb installations, so update the version determination. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7790) Downgrading a package with pkgin fails silents
Title: Message Title Moses Mendoza commented on PUP-7790 Re: Downgrading a package with pkgin fails silents From PUP-7790 . It looks like [the issue](https://github.com/NetBSDfr/pkgin/issues/73) has gotten some upstream attention: > This diff appears to resolve the problem:... > I think this is correct (ignore the downgrade problem if the package has been directly specified), but I'm going to leave it to bake in the SmartOS 2017Q3 builds first before committing here. Commits were pushed 17 days ago. Since these formats do appear to use different databases and to avoid risk of unexpected regression, I'm inclined to leave this as-is and wait for upstream resolution, so I'm going to close this now. Thank you for bringing it to our attention. I'm going to close this issue and link to the upstream bug for people to track resolution Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8044) Enable testing PA built for FIPS on platforms in FIPS mode
Title: Message Title Jayant Sane commented on PUP-8044 Re: Enable testing PA built for FIPS on platforms in FIPS mode PR: https://github.com/puppetlabs/puppet/pull/6271 Note - the changes are piggybacking the other changes in PA-7983 to upgrade openssl version on rhel7 which is a pre-requisite for this to work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows That PR is rather old, it may need to be rebased. I’m on PTO today. I could look at it on Monday. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3263) Architecture Parameter for Package Resource
Title: Message Title Casey Williams assigned an issue to Unassigned Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Casey Williams Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8049) Adjust or skip FIPS incompatible acceptance tests when running in FIPS mode
Title: Message Title Jayant Sane created an issue Puppet / PUP-8049 Adjust or skip FIPS incompatible acceptance tests when running in FIPS mode Issue Type: Task Assignee: Unassigned Created: 2017/10/13 12:25 PM Priority: Normal Reporter: Jayant Sane Following tests were identified to be incompatible with FIPS mode of operation due to their use of md5. They need to be either skipped or adjusted to use one of the fips approved hash algorithms. tests.puppet_apply_a_file_should_create_a_file_and_report_the_md5.rb tests.ticket_1334_clientbucket_corrupted.rb tests.ticket_6541_invalid_filebucket_files.rb tests/face.loadable_from_modules.rb tests/loader.func4x_loadable_from_modules.rb tests/parser_functions.calling_all_functions.rb tests/modules/build.build_agent.rb
Jira (PUP-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Maggie Dreyer commented on PUP-8039 Re: Puppet 4.10.x: Only warn once when gettext cannot be found I was able to demonstrate the spam even just using `puppet module list` after uninstalling the gettext-setup gem. With this fix, only one warning appears stating the GettextSetup could not be found, and translations for modules will not appear. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7888) Pluginsync modules with deep directories fail on Windows
Title: Message Title Glenn Sarti commented on PUP-7888 Re: Pluginsync modules with deep directories fail on Windows matthieu Thankyou for the update!! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7888) Pluginsync modules with deep directories fail on Windows
Title: Message Title matthieu commented on PUP-7888 Re: Pluginsync modules with deep directories fail on Windows Problem solved in windows 2016 which removes the max_path using the "enable NTFS long path support" GPO parameter (https://www.saotn.org/ntfs-long-paths-windows-server-2016-gpo/) . Successfully compiled the xSQLServer 8.2 dsc module in puppetlabs/dsc and downloaded the module through puppet agent in a windows 2016 vm. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Tiffany Longworth updated an issue Puppet / PUP-7883 Make node_terminus=ldap working with jruby/puppetserver Change By: Tiffany Longworth Labels: cs_pr_review Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1391) puppet device cannot create certs when run as root
Title: Message Title Tiffany Longworth updated an issue Puppet / PUP-1391 puppet device cannot create certs when run as root Change By: Tiffany Longworth Labels: cs_pr_review redmine Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3712) Delete/Purge an arbitrary report from the database
Title: Message Title Wyatt Alt commented on PDB-3712 Re: Delete/Purge an arbitrary report from the database Neil Binney FWIW it is safe to delete from the reports table in postgres with psql if necessary delete from reports where certname = 'foo' and end_time = ''; 2) sounds like the receive_time field, which is there right now Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title
Florian Klink created an issue
Puppet / PUP-8048
puppet / facter fails randomly in low memory situations
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/13 7:39 AM
Priority:
Normal
Reporter:
Florian Klink
I accidentially created a VM with only 128MB RAM. Puppet run looks like this:
{{Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not retrieve local facts: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Failed to apply catalog: Could not retrieve local facts: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass}}
This is due to Facter.value(:operatingsystem) being NilClass. When running with --debug, I see a lot of the following messages:Debug: Facter: value for is still nil
It took me a while to find out the puppet run succeeds with more memory just fine. I didn't see any OOM-Killings in dmesg. Of course, it might be not supported/advised to run puppet on such low memory, but I'd still expect puppet to somehow fail in a better way… This might boil down to facter failing in weird ways, puppet not noticing that, or something in between.
puppet-4.8.2-5 on Debian Stretch with packages provided by Debian directly.
Jira (PUP-8046) Tasks with an ensure parameter cause plan failure
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8046 Tasks with an ensure parameter cause plan failure Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1391) puppet device cannot create certs when run as root
Title: Message Title Eric Delaney updated an issue Puppet / PUP-1391 puppet device cannot create certs when run as root Change By: Eric Delaney QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1778) Puppet/Facter loading facts twice
Title: Message Title Jeff Sparrow commented on FACT-1778 Re: Puppet/Facter loading facts twice no problem. Thanks Michael Smith for looking at this. We will eventually be moving to latest Puppet and thus puppet-agent. So hopefully the fix will be out for us by that time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Kevin Reeuwijk updated an issue Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Added Dockerfile (which also copies run-puppet.cmd into the container), this can be used to recreate the container for testing. Change By: Kevin Reeuwijk Attachment: Dockerfile Attachment: run-puppet.cmd Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Kevin Reeuwijk moved an issue Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Change By: Kevin Reeuwijk Method Found: Needs Assessment Component/s: Facter Component/s: Windows Workflow: Documentation Scrum Team Workflow Key: DOC FACT - 1779 Project: Documentation [Internal] Facter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3712) Delete/Purge an arbitrary report from the database
Title: Message Title Neil Binney created an issue PuppetDB / PDB-3712 Delete/Purge an arbitrary report from the database Issue Type: New Feature Assignee: Unassigned Components: PE, PuppetDB Created: 2017/10/13 2:05 AM Priority: Normal Reporter: Neil Binney Reports are timestamped by the agent node. If the time on the node is wrong this can result in reports in the puppetdb with dates in the furture. When the time on the agent node is corrected puppetdb will discard the fresh reports as the date is older than the previous report. To resolve this user should be able to; 1) delete/purge an arbitrary report from the database via PQL. 2) View reports based on a timestamp of when they were received by Puppetdb. Add Comment
