Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Thomas Kishel commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 https://github.com/puppetlabs/puppet/pull/7320 targets 5.5.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9396) Puppet agent is not correctly writing events: failed:
Title: Message Title Paladox created an issue Puppet / PUP-9396 Puppet agent is not correctly writing events: failed: Issue Type: Bug Affects Versions: PUP 6.0.0 Assignee: Unassigned Created: 2019/01/03 8:00 PM Environment: Debian 9 Priority: Critical Reporter: Paladox Hi, i recently upgraded from puppet 4.8 to 6.1 on debian 9. Since then i noticed if i make error like: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: The parameter $name redefines a built in parameter in the 'define' _expression_ (file: /etc/puppetlabs/puppet/environments/production/modules/monitoring/manifests/wiki.pp, line: 3, column: 5) on node misc1.miraheze.org the servers las run summery file ( /opt/puppetlabs/server/data/puppetserver/state/last_run_summary.yaml ) only shows events: failure: 0 success: 0 total: 0 even though the catalog failed. Under puppet 4.8 this worked but under 6.1 it seems to have different behaviour. I made a error a few days ago without realising my mistake until i tried running puppet.
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Rob Braden commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 We still need to address this, but fwiw bundler has dropped the rubygems 3.0.0 hard requirement: https://github.com/bundler/bundler/pull/6867 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Thomas Kishel commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Yes: https://github.com/puppetlabs/puppet/blob/099ab2efb8b1bd7649586a3a79312166dfb62e90/lib/puppet/provider/package/gem.rb#L135 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9393) MacOS Agent URL's are broken for the pe_repo class
Title: Message Title Branan Riley commented on PUP-9393 Re: MacOS Agent URL's are broken for the pe_repo class Hi, PE 2019.0.1 ships with puppet-agent 6.0.4. Generally, upgrading the agent version on the master is unsupported and WILL cause bad things to happen - in this case, because you've updated your masters to 6.1.0, the pe_repo code is looking for an agent which is not available (6.1.0 on PE 2019.0.1). The fix is to downgrade to the agent that was shipped as part of that PE release. If you're a PE customer and you need further help, please reach out to support at https://support.puppet.com. If you're just evaluating PE, you can find community help on the Puppet Slack or on the puppet-users mailing list. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Branan Riley commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 It looks like --no-document has been around long enough that we should be able to just switch to it in all supported streams (5.5, 6.0, and master). I'll get this scheduled so it will go out in the upcoming set of releases. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Branan Riley updated an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Change By: Branan Riley Sprint: Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Branan Riley updated an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Change By: Branan Riley Labels: gem package sadness type_and_provider Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Branan Riley updated an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8962) Type and provider info should be logged when prefetch fails
Title: Message Title Kris Bosland updated an issue Puppet / PUP-8962 Type and provider info should be logged when prefetch fails Change By: Kris Bosland Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8962) Type and provider info should be logged when prefetch fails
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-8962 Type and provider info should be logged when prefetch fails Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2354) agent is confused about cert state
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-2354 agent is confused about cert state Change By: Thomas Kishel CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4182) Use beaker 4 in pdb acceptance tests
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4182 Use beaker 4 in pdb acceptance tests Change By: Zachary Kent Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4182) Use beaker 4 in pdb acceptance tests
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4182 Use beaker 4 in pdb acceptance tests Change By: Zachary Kent Fix Version/s: PDB n/a Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4182) Use beaker 4 in pdb acceptance tests
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4182 Use beaker 4 in pdb acceptance tests Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1054) Add a bolt standard library
Title: Message Title Alex Dreyer commented on BOLT-1054 Re: Add a bolt standard library sysem::env in the release note should be system::env Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1054) Add a bolt standard library
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1054 Add a bolt standard library Change By: Melissa Amos Labels: doc_reviewed docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1054) Add a bolt standard library
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1054 Add a bolt standard library Change By: Melissa Amos Labels: doc_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1054) Add a bolt standard library
Title: Message Title Melissa Amos commented on BOLT-1054 Re: Add a bolt standard library Docs for review: http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#standard-library-functions-1-8-0 http://docs-internal.puppet.com/docs/bolt/dev/plan_functions.html (Linking to the whole page here, so you can verify that I caught all additions) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Andreas Ntaflos commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 We ran into the same issue today, with Puppet 5.5.6 on Ubuntu 16.04 and 18.04: Error: Could not update: Execution of '/usr/bin/gem install -v 2.7.7 --no-rdoc --no-ri rubygems-update' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) invalid option: --no-rdoc Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (BOLT-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Melissa Amos Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Melissa Amos commented on BOLT-997 Re: puppet_agent::install doesn't match on RedhatEnterpriseServer platform Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#puppet-agent-install-task-didn-t-match-on-red-hat-1-8-0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Josh Cooper commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 The alternative way to exclude documentation is to specify the --no-document option. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9395
provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Change By:
Josh Cooper
Since version 3.x, gem will not have anymore the 2 params ` {{\ - \ -no-ri ` }} and ` {{\ - \ -no-rdoc ` }} , that currently are the default params.([https://github.com/puppetlabs/puppet/blob/24ead48f617cd3912491fe419ac7b67cda53a320/lib/puppet/provider/package/gem.rb#L131)] when is used the provider gem in the type package. This should be addressed by adding an option to disable them or override them through the parameter `install_options` already existing in the type package. The version 3.x of rubygems is a constraint since the new bundler major version 2.0.0 dropped support for rubygem older than 3.0.0 : [https://github.com/bundler/bundler/releases/tag/v2.0.0] .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PDB-4191) Allow building puppetdb-cli against recent OpenSSL version
Title: Message Title Zachary Kent assigned an issue to Unassigned PuppetDB / PDB-4191 Allow building puppetdb-cli against recent OpenSSL version Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Cas Donoghue Release Notes Summary: Previously the The ` bash puppet_agent::install ` and `powershell` implementations of task now utilizes updates in the `facts` task would defer to `facter` to calculate resolve Red Hat operating system facts resulting in different values based on the presence of `facter`. The task now only defers order to `facter` when download the target has the ` correct puppet-agent ` feature package . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Cas Donoghue Release Notes Summary: Previously the `bash` and `powershell` implementations of the `facts` task would defer to `facter` to calculate system facts resulting in different values based on the presence of `facter`. The task now only defers to `facter` when the target has the `puppet-agent` feature. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2354) agent is confused about cert state
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-2354 agent is confused about cert state If `allow_duplicate_certs` is broken, we should document it as a known issue to spare users the frustration of trying to utilize it? Change By: Thomas Kishel Release Notes: Known Issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1060) Reconcile git commits, JIRA tickets, and versions (Bolt 1.8.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1060 Reconcile git commits, JIRA tickets, and versions (Bolt 1.8.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/03 10:15 AM Due Date: 2019/01/03 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-03) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1061) Kick off release pipeline (Bolt 1.8.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1061 Kick off release pipeline (Bolt 1.8.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/03 10:15 AM Due Date: 2019/01/03 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-03) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1063) Docs for bolt release (Bolt 1.8.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1063 Docs for bolt release (Bolt 1.8.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/03 10:15 AM Due Date: 2019/01/03 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-03) Release notes and docs changes for bolt 1.8.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1064) Send release announcements (Bolt 1.8.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1064 Send release announcements (Bolt 1.8.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/03 10:15 AM Due Date: 2019/01/03 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-03) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.8.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.8.0 is now available".
Jira (BOLT-1062) Update homebrew-puppet (Bolt 1.8.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1062 Update homebrew-puppet (Bolt 1.8.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/03 10:15 AM Due Date: 2019/01/03 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-03) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1059) Bolt 1.8.0 2019-01-03 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1059 Bolt 1.8.0 2019-01-03 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/01/03 10:15 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.8.0 2019-01-03 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1902) Facter should validate that external/custom/executable facts output proper UTF-8
Title: Message Title Charlie Sharpsteen updated an issue Facter / FACT-1902 Facter should validate that external/custom/executable facts output proper UTF-8 Change By: Charlie Sharpsteen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1902) Facter should validate that external/custom/executable facts output proper UTF-8
Title: Message Title Charlie Sharpsteen updated an issue Facter / FACT-1902 Facter should validate that external/custom/executable facts output proper UTF-8 Change By: Charlie Sharpsteen Modern versions of Puppet require that the data they serialize to JSON is proper UTF-8. When facts have an incorrect encoding, this currently does not raise an error until it is serialized, at which point it is far too late, and the error message is not helpful.Instead, Facter itself should raise an error about this, indicating the specific fact which returned bad data. This will provide better context fordebugging. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Michael Smith Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: Michael Smith Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4239) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4239 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2019/01/03 8:57 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
Jira (PUP-2354) agent is confused about cert state
Title: Message Title Jayant Sane assigned an issue to Unassigned Puppet / PUP-2354 agent is confused about cert state Change By: Jayant Sane Assignee: Jayant Sane Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Luca Zecca created an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Components: Types and Providers Created: 2019/01/03 8:06 AM Priority: Major Reporter: Luca Zecca Since version 3.x, gem will not have anymore the 2 params `-no-ri` and `-no-rdoc`, that currently are the default params.(https://github.com/puppetlabs/puppet/blob/24ead48f617cd3912491fe419ac7b67cda53a320/lib/puppet/provider/package/gem.rb#L131) when is used the provider gem in the type package. This should be addressed by adding an option to disable them or override them through the parameter `install_options` already existing in the type package. The version 3.x of rubygems is a constraint since the new bundler major version 2.0.0 dropped support for rubygem older than 3.0.0 : https://github.com/bundler/bundler/releases/tag/v2.0.0 . Add Comment
Jira (PUP-9365) Newlines in resource titles result in invalid .dot files
Title: Message Title Henrik Lindberg commented on PUP-9365 Re: Newlines in resource titles result in invalid .dot files For anyone that want to work on this - I think the logic is here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/graph/simple_graph.rb#L439 For some values it calls a stringify method, and it only deals with embedded double quotes. Not certain if something similar is needed for values that are used in DOT output without stringifying them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks updated an issue Puppet / PUP-9394 File mode X should work with the = operator Change By: Daniel Parks Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks created an issue Puppet / PUP-9394 File mode X should work with the = operator Issue Type: Improvement Assignee: Unassigned Created: 2019/01/03 12:13 AM Priority: Normal Reporter: Daniel Parks Setting mode => 'u=rwX,go=rX' or similar symbolic modes on File resources fails with the following error: File[/foo]/mode: change from '0755' to 'u=rwX,go=rX' failed: X only works with the '+' operator at "u=rwX" in symbolic mode "u=rwX,go=rX" It would be helpful if X worked with the = operator. In that case, it would only set the execute bit if the resource represented a directory. I realize that this isn't the way chmod works. I know that I can use '0644' and it will automatically apply '0755', but that's weird and surprising. Using X in symbolic mode is much clearer and more intuitive. Add Comment
