Jira (PUP-9934) AIX user resource fails
Title: Message Title Vladimir Vassyukov created an issue Puppet / PUP-9934 AIX user resource fails Issue Type: Bug Affects Versions: PUP 6.5.0 Assignee: Unassigned Created: 2019/07/31 9:37 PM Environment: root@nes-t1a-app6> [~]# oslevel -s 7100-05-03-1846 root@nes-t1a-app6> [~]# uname -a AIX nes-t1a-app6 1 7 00F7040C4C00 Debug: Executing: '/bin/chpasswd -e -c oracle' Error: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAix Error: /Stage[main]/Aix::Oracleuser/User[oracle]/password: change from [old password hash redacted] to [new password hash redacted] failed: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAix Priority: Major Reporter: Vladimir Vassyukov An error occurs using parameter "password" module "users". I find the bug report PUP-8538, it describes the same issue, and it marked as fixed in version PUP 4.10.11, PUP 5.3.6, PUP 5.5.1, but i get the error in version 6.5.0 Add Comment
Jira (BOLT-1501) Change AWS plugin config field
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1501 Change AWS plugin config field Change By: Tom Beech Assignee: Tom Beech 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319097.1564618066000.39319.1564618140099%40Atlassian.JIRA.
Jira (BOLT-1501) Change AWS plugin config field
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1501 Change AWS plugin config field Change By: Tom Beech Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319097.1564618066000.39318.1564618140094%40Atlassian.JIRA.
Jira (BOLT-1501) Change AWS plugin config field
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1501 Change AWS plugin config field Issue Type: Improvement Assignee: Unassigned Created: 2019/07/31 5:07 PM Priority: Normal Reporter: Tom Beech When using a config file to specify AWS plugin configuration, the information is located under the 'aws' field. This configuration should instead be located in the 'plugins' field, similar to the Prompt plugin. Current config: aws: credentials: /path/to/creds Correct config: plugins: aws: credentials: /path/to/creds
Jira (BOLT-1475) Kerberos - Create development / debug environment inside test containers
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1475 Kerberos - Create development / debug environment inside test containers Change By: Lucy Wyman Assignee: Lucy Wyman 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317167.1563491448000.38990.1564609380094%40Atlassian.JIRA.
Jira (BOLT-1498) Update homebrew-puppet (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1498 Update homebrew-puppet (Bolt 1.27.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) Until we automate this, you'll also need to update the version and SHA hashes of homebrew-puppet. 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-1494) Reconcile git commits, JIRA tickets, and versions (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1494 Reconcile git commits, JIRA tickets, and versions (Bolt 1.27.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) Ensure all tickets referenced in the commit log have been targeted at the release. 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. Ensure all tickets have release notes. Ensure all tickets have been resolved. In JIRA releases, change 'BOLT Next' to 'BOLT x.y.z' with the release date. Create a new 'BOLT Next'.
Jira (BOLT-1499) Docs for bolt release (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1499 Docs for bolt release (Bolt 1.27.1) Issue Type: Sub-task Assignee: Chris Cowell Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) Release notes and docs changes for bolt 1.27.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1495) Kick off release pipeline (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1495 Kick off release pipeline (Bolt 1.27.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) With our automated builds pipeline Ensure the sha at the tip of the master branch of bolt has been promoted to bolt-vanagon Based on that sha ensure both the component pipeline and bolt-vanagon packaging pipeline have completed successfully bolt packages are staged on puppet-bolt based on sha from bolt vanagon Go to the release pipeline 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!
Jira (BOLT-1496) Publish release artifacts (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1496 Publish release artifacts (Bolt 1.27.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) Run the Bolt shipping pipeline. Set REF to 1.27.1. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1500) Send release announcements (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1500 Send release announcements (Bolt 1.27.1) Issue Type: Sub-task Assignee: Chris Cowell Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) When docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt now available". In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com In the body, include a summary of the release and links to the release notes and installation instructions. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. (Optional) Set up a canned response in Gmail so that you don't have to recreate this email every time: Subject: Bolt X.Y.Z now available Body: Greetings! We're happy to announce the release of Bolt X.Y.Z. Highlights in this release include: Gerund phrase Gerund phrase For more information, check out
Jira (BOLT-1497) Update the release spreadsheet (Bolt 1.27.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1497 Update the release spreadsheet (Bolt 1.27.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Due Date: 2019/07/31 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-07-31) Update the release google spreadsheet for Bolt 1.27.1. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1493) Bolt 1.27.1 2019-07-31 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1493 Bolt 1.27.1 2019-07-31 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/07/31 2:04 PM Priority: Normal Reporter: Cas Donoghue Bolt 1.27.1 2019-07-31 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9730) Connections with multiple addresses for a host should try ALL addresses for that host
Title: Message Title Jorie Tappa commented on PUP-9730 Re: Connections with multiple addresses for a host should try ALL addresses for that host So since there's been some investigation on this and then follow up tickets were made (PUP-9732) this one might be able to just be closed, once we've tested the behavior for failover from IPv6 to IPv4. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311671.1559920061000.38787.1564604820232%40Atlassian.JIRA.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Scott McClellan assigned an issue to Scott McClellan Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Scott McClellan Assignee: Scott McClellan 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.38681.1564598940177%40Atlassian.JIRA.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Branan Riley updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Branan Riley Sprint: Skeletor Kanban 20190619, Skeletor Kanban 20190703, Skeletor Kanban 20190717, Skeletor Kanban 20190731 , Skeletor Kanban 20190814 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.38546.1564596421915%40Atlassian.JIRA.
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Branan Riley updated an issue Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Branan Riley Sprint: Skeletor Kanban 20190717, Skeletor Kanban 20190731 , Skeletor Kanban 20190814 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.38548.1564596421925%40Atlassian.JIRA.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Change By: Cas Donoghue Assignee: Cas Donoghue 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309610.1558465731000.38310.1564593300280%40Atlassian.JIRA.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Change By: Cas Donoghue Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309610.1558465731000.38308.1564593240434%40Atlassian.JIRA.
Jira (PUP-9932) Make 3x functions thread-safe
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9932 Make 3x functions thread-safe Change By: Maggie Dreyer Summary: make Make 3x functions thread-safe 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306743.1556579117000.38079.1564588140213%40Atlassian.JIRA.
Jira (PUP-9932) make 3x functions thread-safe
Title: Message Title Maggie Dreyer commented on PUP-9932 Re: make 3x functions thread-safe Thanks Henrik, this is a great starting point! I'll let you know if I have more specific questions. We were also wondering in general about the future of 3x functions, beyond this effort, perhaps for Puppet 7. So thanks for including the details on the possible migration path too. And for context, this ticket is part of a larger effort to make the Puppet runtime threadsafe, because we are planning to make it possible to run Puppet Server without the JRuby pool in the future, using just one instance of Puppet and running requests through it concurrently. If you have any thoughts about the rest of the tickets in the epic, or things we may not have thought of, please feel free to comment there as well. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306743.1556579117000.38040.1564587360165%40Atlassian.JIRA.
Jira (BOLT-1492) get_targets surfaces exception when used in apply block with inventory v2
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1492 get_targets surfaces exception when used in apply block with inventory v2 Change By: Lucy Wyman 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318475.1564443989000.38013.1564586460207%40Atlassian.JIRA.
Jira (PUP-9932) make 3x functions thread-safe
Title: Message Title Henrik Lindberg commented on PUP-9932 Re: make 3x functions thread-safe Maggie Dreyer What is meant by being "thread safe" in this context? Asking because the puppet runtime is not thread safe so what is the purpose of making 3x functions "thread safe"? (I think what is really asked is how to make 3x functions not taint loaded classes which is what makes them leak across environments unless code is completely reloaded). How 3x functions work: The 3x functions use an anonymous Module and methods are created in this module using the names function_ and real_function_. This module is then picked up in the implementation of Scope - it calls a method named "extend_with_function_module". Scope is extended with the anonymous module for the "root" environment (unclear if this is meaningful as I think that only held the logging functions and those are 4x), and the anon module for the "current env". The effect of this is that each instance of Scope will have the function_ and real_function_ available as callable methods. The 3.x function logic is in lib/puppet/parser/functions.rb and in lib/puppet/parser/scope.rb - the ruby_legacy_function_instantiator is what makes 3x loadable the 4x way. There has been several changes to 3x functions - there used to be memory leaks related to the mapping from env to anonymous module - this is now (since Puppet 4.4 - PUP-5813) done with an adapter that associates the information with the env's lifecycle. I suspect that change also fix some other potential cases of leaking. In Puppet 6 when we started loading 3x via ruby_the legacy_function_instantiator we also added a scan that the loaded 3x function is free from dangerous constructs. The constructs it is protecting against would if allowed taint the Scope class as opposed to the anonymous module. So what remains to be done here for safety? it is a problem that code can load 3x functions via code paths other than via 4x loaders - this means that they can have dangerous constructs. I would like remove those code paths. I don't think that the Scope extend of the anonymous module causes leakage as it is tied to a specific instance of scope What I think should also be done: We should get rid of the use of anonymous modules as it means that the set of available methods for Scope changes as functions are loaded. I suspect that to have negative impact on performance (destroys possible optimization) - but this is only a suspicion. Investigate if the extend of the root environment's anon module is really needed - if we do not remove this kind of extend all together. We should get rid of the support to call function_ and real_function_ as those only works for calling 3x functions. This is a problem because 3x logic using those can end up calling a 3x version of a function when there is a 4x function shadowing it (if the called 3x function was loaded via a different code path than via the legacy instantiator). (The right way to call functions is to use Scope.call_function. When a 3x function is being evaluated self is bound to an instance of Scope - this opens up for mistakes in the implementation of a
Jira (FACT-1978) Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)
Title: Message Title Andreas created an issue Facter / FACT-1978 Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2) Issue Type: Bug Assignee: Unassigned Created: 2019/07/31 2:56 AM Priority: Major Reporter: Andreas For Amazon Linux, Facter expects the version string in /etc/system-release as $major.$minor But on recent AMI versions of Amazon Linux 2 /etc/system-release contains only the major version: Amazon Linux release 2 (Karoo) This problem causes operatingsystemmajrelease and operatingsystemrelease to not get populated. As a result OS specific conditionals in Puppet won't work as expected. Add Comment
Jira (FACT-1884) Add NIM master detection
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-1884 Add NIM master detection Change By: Sebastian Miclea Release Notes Summary: Added an new AIX specific fact that returns the type of the NIM configuration on. This will output 'master', 'standalone' or nothing if '/etc/niminfo' is missing. Release Notes: Enhancement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276290.1537303892000.37687.1564565520123%40Atlassian.JIRA.
Jira (FACT-1935) Facter ipaddress6 on Windows returns link-local address with interface identifier
Title: Message Title Dorin Pleava commented on FACT-1935 Re: Facter ipaddress6 on Windows returns link-local address with interface identifier This issue is solved in this [link PR|https://github.com/puppetlabs/facter/pull/1816]. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316045.1562828787000.37609.1564560900125%40Atlassian.JIRA.
Jira (FACT-1977) Create FacterNG skeleton
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-1977 Create FacterNG skeleton Change By: Bogdan Irimie Assignee: Bogdan Irimie 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318945.1564552155000.37602.1564560600197%40Atlassian.JIRA.
Jira (FACT-1977) Create FacterNG skeleton
Title: Message Title Bogdan Irimie assigned an issue to Sebastian Miclea Facter / FACT-1977 Create FacterNG skeleton Change By: Bogdan Irimie Assignee: Bogdan Irimie Sebastian Miclea 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318945.1564552155000.37604.1564560600225%40Atlassian.JIRA.
