Jira (PUP-8879) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8879 Move all outstanding PUP tickets to Modules Change By: Melissa Stone Assignee: Melissa Stone 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-8874) Extract the code & verify the module
Title: Message Title Melissa Stone commented on PUP-8874 Re: Extract the code & verify the module As there is already a repo where this code has been extracted, I simply installed the latest passing sha from puppet-agent#master, deleted the scheduled_task files that have already been extracted, then installed the puppetlabs/scheduled_task module from the forge. I then executed a scheduled task manifest to ensure it would apply as expected. I took a screen shot of the results, which I have pasted in this ticket. 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-8874) Extract the code & verify the module
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8874 Extract the code & verify the module Change By: Melissa Stone Attachment: Screen Shot 2018-07-20 at 2.31.07 PM.png 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-8877) Package module into puppet-agent
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8877 Package module into puppet-agent Change By: Melissa Stone Assignee: Melissa Stone 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-8999) Puppet failover breaks when additional requests are made during server list resolution
Title: Message Title Amy Sahli commented on PUP-8999 Re: Puppet failover breaks when additional requests are made during server list resolution See https://github.com/puppetlabs/puppet/pull/6879 for PR 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Charlie Sharpsteen commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Now that PUP-7779 is in, I think we could do this in a fairly straight-forward manner by adding a report_facts setting that would cause the Puppet Agent to load and submit a new factset to `/puppet/v3/facts` at the end of the run before the report is sent to `/puppet/v3/report`. This setting should default to false as the additional fact submission would represent a 33% increase in the datasets sent to PuppetDB on each run from facts, catalog, report to facts, catalog, facts, report. For most folks, PuppetDB will handle that just fine — but at large scale it is a big enough increase that has to be enabled deliberately. We could follow the naive implementation above with something more sophisticated that computes the diff between facts loaded at the beginning of the run and those loaded at the end and attaches it to the report. That would be much more efficient as both the amount of data and number of processing operations would be reduced. However, this would require changes to the report format and PuppetDB and thus is a much bigger lift to accomplish. 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
Jira (PUP-8875) Create the CI pipeline
Title: Message Title Melissa Stone commented on PUP-8875 Re: Create the CI pipeline A pipeline already exists at https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/windows/view/scheduled_task/view/master/ Should we create a new view in the 'core' tab? 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-8875) Create the CI pipeline
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8875 Create the CI pipeline Change By: Melissa Stone Assignee: Melissa Stone 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-615) I want to install a puppet-agent with bolt
Title: Message Title Michael Smith commented on BOLT-615 Re: I want to install a puppet-agent with bolt Additional work to get to a releasable set of tasks for puppetlabs-puppet_agent was broken off as Epic BOLT-700. 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-8878) Remove type/provider code from puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8878 Remove type/provider code from puppet Change By: Melissa Stone Assignee: Melissa Stone 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-8874) Extract the code & verify the module
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8874 Extract the code & verify the module Change By: Melissa Stone Assignee: Melissa Stone 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-682) Have nice error message if user tries 'apply' with no PA
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-682 Have nice error message if user tries 'apply' with no PA Change By: Alex Dreyer Assignee: Alex Dreyer 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-8957) [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Geoff Nichols 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-8957) [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3
Title: Message Title Geoff Nichols assigned an issue to Enis Inan Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Geoff Nichols Assignee: Branan Riley Enis Inan 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Jorie Tappa Sprint: Platform Core Grooming 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Jorie Tappa Team: Platform OS Coremunity 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-706) Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-706 Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF This probably is case of the orchestrator client library not correctly validating the token and stripping whitespace. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-706) Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-706 Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF Change By: Alex Dreyer Fix Version/s: 0.21.3 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-690) facts task should include legacy facts
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-690 facts task should include legacy facts Change By: Alex Dreyer Assignee: Alex Dreyer 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-698) Output of ruby script over WinRM not consistent
Title: Message Title Alex Dreyer assigned an issue to Michael Smith Puppet Task Runner / BOLT-698 Output of ruby script over WinRM not consistent Change By: Alex Dreyer Assignee: Michael Smith 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-649) Support _run_as as an apply option
Title: Message Title Alex Dreyer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-649 Support _run_as as an apply option Change By: Alex Dreyer 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 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-648) Support _catch_errors as an apply option
Title: Message Title Alex Dreyer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-648 Support _catch_errors as an apply option Change By: Alex Dreyer Assignee: Michael Smith 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 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-648) Support _catch_errors as an apply option
Title: Message Title Alex Dreyer assigned an issue to Michael Smith Puppet Task Runner / BOLT-648 Support _catch_errors as an apply option Change By: Alex Dreyer Assignee: Michael Smith 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-613) I want to use the plan spec helpers to test my module
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-613 I want to use the plan spec helpers to test my module Change By: Alex Dreyer Assignee: Alex Dreyer 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-523) I want to install modules with bolt
Title: Message Title Alex Dreyer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: Alex Dreyer Assignee: Alex Dreyer Nick Lewis 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-682) Have nice error message if user tries 'apply' with no PA
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-682 Have nice error message if user tries 'apply' with no PA Change By: Alex Dreyer Assignee: Alex Dreyer 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan assigned an issue to Enis Inan Facter / FACT-1475 facter returns wrong ipv6 information when IPV6 stack is disabled Change By: Enis Inan Assignee: Enis Inan 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan commented on FACT-1475 Re: facter returns wrong ipv6 information when IPV6 stack is disabled Vadym Chepkov Ah, I'm able to reproduce it now. Thank you! Going to try to put up a fix for this soon. 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Vadym Chepkov commented on FACT-1475 Re: facter returns wrong ipv6 information when IPV6 stack is disabled Yes, changes take effect during boot time. 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan commented on FACT-1475 Re: facter returns wrong ipv6 information when IPV6 stack is disabled Peter Meier I'm not sure what you mean by "unloading the module." I have it here https://github.com/ekinanp/facter/tree/FACT-1475/MODULES (that I'll revert once I can replicate the issue and get a fix in) with the ipv6 manifest in the customer module. The script disable-ipv6.sh is a wrapper to puppet apply that declares that class. (The other modules are dependencies for the kernel_parameter resource). 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Peter Meier commented on FACT-1475 Re: facter returns wrong ipv6 information when IPV6 stack is disabled Yes it resolves, still to an ipv6 address. So somehow you still have an ip6 address on your interfaces, which means that you do not have properly disabled ipv6. Are you unloading the module? Anyway it seems that meanwhile the ip util got fixed. At least CentOS 7: # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-693.21.1.el7.x86_64 root=/dev/mapper/vg--meh-root ro crashkernel=auto rd.lvm.lv=vg-meh/root rd.lvm.lv=vg-meh/swap ipv6.disable=1 console=ttyS0,115200 panic=30 LANG=en_US.UTF-8 # ip -6 addr # ip -6 route show # facter -p --show-legacy | grep ipaddress default_ipaddress => 192.168.1.22 ipaddress => 192.168.1.22 ipaddress_eth0 => 192.168.1.22 ipaddress_lo => 127.0.0.1 Compare to what I reported in FACT-1739 So facter is not anymore reporting an ipaddress6 fact. Still this could have been avoided if facter would match values against an excpected pattern. Which in this case here would be pretty trivial, as the format of an ipaddress is (luckily) the same on any system.
Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan commented on FACT-1475 Re: facter returns wrong ipv6 information when IPV6 stack is disabled Vadym Chepkov Thanks! I've tried applying that manifest on CentOS 5, 6, and 7 nodes but I still can't reproduce the issue. - CentOS 7.2.1511 [root@s5ivbahpr655b6y facter]# ./MODULES/disable-ipv6.sh Notice: Compiled catalog for s5ivbahpr655b6y.delivery.puppetlabs.net in environment production in 0.06 seconds Notice: /Stage[main]/Customer::Ipv6/Kernel_parameter[ipv6.disable]/ensure: created Notice: Applied catalog in 0.85 seconds 2018-07-20 14:02:32.161888 DEBUG leatherman.execution:93 - executing command: /usr/sbin/ip route show 2018-07-20 14:02:32.163215 DEBUG | - default via 10.32.112.1 dev ens160 proto static metric 100 2018-07-20 14:02:32.163318 DEBUG | - 10.32.22.9 via 10.32.112.1 dev ens160 proto dhcp metric 100 2018-07-20 14:02:32.163377 DEBUG | - 10.32.112.0/20 dev ens160 proto kernel scope link src 10.32.121.83 metric 100 2018-07-20
Jira (BOLT-335) Boltlib functions should have configurable timeouts
Title: Message Title Charlie Sharpsteen commented on BOLT-335 Re: Boltlib functions should have configurable timeouts This feature will be important once we start executing task plans — which I assume are coming to orchestrator as well as bolt. 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-8529) Remove data_binding_terminus setting
Title: Message Title Thomas Hallgren commented on PUP-8529 Re: Remove data_binding_terminus setting As Henrik points out, only none `hiera_xxx` calls will use the configured data binding terminus for the lookup. The `hiera_xxx` calls will bypass the terminus and use the global provider directly. That answers Josh Cooper's question with a: "no, this ticket is not blocked". To answer Henrik Lindberg's question, AFAICT, we only have two data_binding_terminus configured. "hiera" and "none", and both are trapped before the terminus is called upon. So the only chance of anything happening here is if someone has installed some external data_binding_terminus. If the objective is to remove this terminus due to long standing deprecation, then I don't see any problems with that. 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-9010) Puppetserver fails to compile catalog when disable_i18n = true
Title: Message Title
Mateusz Gozdek commented on PUP-9010
Re: Puppetserver fails to compile catalog when disable_i18n = true
It seems, that client-side compilation is also broken because of this, is it now covered by tests? test.pp:
$a = [ 'foo', 'bar', 'baz']
notify { $a.map |$v| { "fqdn='${v}'" }.join(' or '): }
result:
# puppet apply -t test.pp
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Jira (PUP-8529) Remove data_binding_terminus setting
Title: Message Title Henrik Lindberg commented on PUP-8529 Re: Remove data_binding_terminus setting Well, all hiera_xxx calls will have lookupinvocation.hiera_xxx_call be true so would always get the :hiera terminus. That means that hiera_xxx calls does not have to be removed to drop the data_binding_terminus setting. Not quite sure what needs to be done by the other branch of the logic - who would call this method and expect the data_binding_terminus to be in effect. Ping Thomas Hallgren. 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-7609) Make @class and @@class always be a hard error
Title: Message Title Henrik Lindberg commented on PUP-7609 Re: Make @class and @@class always be a hard error Yes. Closing this, the other has more info. 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Marcel commented on PUP-6936 Re: unable to read last_run_summary.yaml from user Hey, any news on this? The problem are the permissions on /opt/puppetlabs/puppet/cache, they are 750. Thanks Marcel 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.
