Jira (PUP-7905) Add a --tasks feature flagged validator
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7905 Add a --tasks feature flagged validator Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7940) Support task diagnostics in a plan
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-7940 Support task diagnostics in a plan Change By: Henrik Lindberg Method Found: Needs Assessment Issue Type: Bug New Feature Key: BOLT PUP - 74 7940 Project: Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7941) Autogenerated custom types never get all properties set
Title: Message Title Reinhard Vicinus created an issue Puppet / PUP-7941 Autogenerated custom types never get all properties set Issue Type: Bug Affects Versions: PUP 4.10.7 Assignee: Unassigned Created: 2017/09/12 12:57 AM Priority: Minor Reporter: Reinhard Vicinus Don't know if I missed something, but as far as I can tell via prefetch autogenerated resources of custom types never get all properties set. Here is a simple example: test/lib/puppet/type/touchfile.rb Puppet::Type.newtype(:touchfile) do
Jira (PUP-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Nacho Barrientos commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever Thanks for (re-)fixing this. Unfortunately my e-mail to puppet-dev has not generated much interest :/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Sam McLeod commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment This bug is very annoying. Our Puppet 3 (Open Source) workflow was: 1. Create branch (r10k environment) 2. Set nodes to run off branch by setting `environment = ` in the nodes puppet.conf 3. Develop on and test branch 4. Merge branch in to production Now the only way we can reliably test branches is to enable puppet on the node, do interactive puppet runs passing `--environment=` and disable puppet again so it doesn't default back to running off production. I tried creating the branch directory in `/etc/puppetlabs/code/environments/` as suggested above, but that just results in no-change puppet runs. I'm really surprised this has gone unfixed for so long. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5634) Application declaration "nodes" parameter should accept string representation of nodes, components
Title: Message Title Yasmin Rajabi updated an issue Puppet / PUP-5634 Application declaration "nodes" parameter should accept string representation of nodes, components Change By: Yasmin Rajabi Labels: app_mgmt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5307) Include reference to capabilities in error message when two capability mappings try to set the same parameter
Title: Message Title Yasmin Rajabi updated an issue Puppet / PUP-5307 Include reference to capabilities in error message when two capability mappings try to set the same parameter Change By: Yasmin Rajabi Labels: app_mgmt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Just heard back from Puppet support: I'm so sorry for the delay, and I thank you for patience with this ticket. I was able to speak to our product managers about the feature request https://tickets.puppetlabs.com/browse/PUP-1054. The feature is on our roadmap, but we don't have a timeline for when it will be completed. We do regularly go through and evaluate feature requests to reprioritize them and I have brought this up with the engineering team to take look. The best place to look for status updates will be in that JIRA ticket. Please let me know if you have any questions or concerns. if not, is it alright to close this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7894) Scheduled Task v2 - Create windows/taskscheduler2
Title: Message Title Glenn Sarti commented on PUP-7894 Re: Scheduled Task v2 - Create windows/taskscheduler2 Ethan Brown Initial PR for review https://github.com/puppetlabs/puppet/pull/6198 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Geoff Nichols commented on PUP-7918 Re: puppet fails to change user group membership if directory group names have spaces Thomas Kishel, thanks for filing this! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Sam McLeod commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment I've just found a repeatable workaround for this bug. Simply creating the environment directory does not work (`/etc/puppetlabs/code/environment/`) however if you copy the `production` environment's directory and it's substructure - it does seem to work: ``` cp -a /etc/puppetlabs/code/environment/production /etc/puppetlabs/code/environment/ puppet agent -t ... So, while it's not a fix, this hopefully will serve as a temporary workaround until this bug is squashed! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7878) Change in Puppet type management breaks defined class checks
Title: Message Title Henrik Lindberg assigned an issue to Geoff Nichols Puppet / PUP-7878 Change in Puppet type management breaks defined class checks Change By: Henrik Lindberg Assignee: Justin Couch Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7822) Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7822 Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: With stdlib having similar functionality this not a high priority. CS Severity: 2 - Annoyance CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You
Jira (PUP-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7883 Make node_terminus=ldap working with jruby/puppetserver Change By: Owen Rodabaugh Labels: cs_pr_review Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7883 Make node_terminus=ldap working with jruby/puppetserver Change By: Owen Rodabaugh CS Priority: Normal CS Impact: While there are not many users of the ldap terminus, a PR has been made to fix it and should be reviewed to help those who do use it. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You
Jira (PUP-7926) vendored pathspec library has an over-reaching regexp
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7926 vendored pathspec library has an over-reaching regexp Change By: Kenn Hussey Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7908) explore possibility to get rid of Class[''] when using 'script'
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7908 explore possibility to get rid of Class[''] when using 'script' Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7908) explore possibility to get rid of Class[''] when using 'script'
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7908 explore possibility to get rid of Class[''] when using 'script' Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7908) explore possibility to get rid of Class[''] when using 'script'
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7908 explore possibility to get rid of Class[''] when using 'script' Change By: Thomas Hallgren Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3656) (maint) Update clj-parent to 1.4.1
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3656 (maint) Update clj-parent to 1.4.1 Issue Type: Bug Assignee: Unassigned Created: 2017/09/12 11:19 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-7308) classes do not honor refresh events when running with tags
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: While tags are not widely used there are a number of customers who rely on them for their specific workflow. We should either fix them to work as expected or make a decision on the future of them. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Team: Platform OS Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7920) Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass`
Title: Message Title John Duarte updated an issue Puppet / PUP-7920 Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass` Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7920) Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass`
Title: Message Title John Duarte updated an issue Puppet / PUP-7920 Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass` Change By: John Duarte Fix Version/s: PUP 5.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7942 Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Change By: Erik Dasher We build puppet agent's for these Cisco platforms:cisco-wrlinux-5-x86_64 (Test Target = cisconx-64) cisco-wrlinux-7-x86_64 (Test Target = ciscoxr-64) We presently only ciscoxr- 64a 64 in the Non Standard pipeline. We should also test cisco*nx*-64 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Rick Sherman commented on PUP-7942 Re: Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline I'd say this is significantly more important than the XR platform. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7942 Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Change By: Erik Dasher Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7908) explore possibility to get rid of Class[''] when using 'script'
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7908 explore possibility to get rid of Class[''] when using 'script' Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3655) PuppetDB query tutorial doesn't explain how to get puppetdb_query function
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3655 PuppetDB query tutorial doesn't explain how to get puppetdb_query function Change By: Isaac Eldridge Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 3262 3655 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7943) I18N puppet.po file should not contain %s and %f entries
Title: Message Title Eric Delaney created an issue Puppet / PUP-7943 I18N puppet.po file should not contain %s and %f entries Issue Type: Bug Affects Versions: PUP 5.3.0 Assignee: Unassigned Created: 2017/09/12 9:53 AM Priority: Normal Reporter: Eric Delaney I was reviewing the puppet.po file when I noticed that we a bunch of %s and a few %f entries in the strings. This is mostly caused when the puppet code builds up the text string to be output. This makes it hard on translators as they only have a small piece of the whole sentence to work with. This will make for a poor reading experience in some languages. Here is a list of what I found while looking: #: ../lib/puppet/face/module/list.rb:120 msgid "Module '%s' (v%s) fails to meet some dependencies:"
Jira (PUP-7944) Bump puppet version to 4.10.8
Title: Message Title Sean McDonald created an issue Puppet / PUP-7944 Bump puppet version to 4.10.8 Issue Type: Task Assignee: Sean McDonald Created: 2017/09/12 11:16 AM Fix Versions: PUP 4.10.8 Priority: Normal Reporter: Sean McDonald 1) Check that the version number in source for puppet is correct version for puppet should be 4.10.8 check lib/puppet/version.rb for the PUPPETVERSION variable. check .gemspec for version variable Add Comment
Jira (PUP-7878) Change in Puppet type management breaks defined class checks
Title: Message Title Alexey Zhigaev commented on PUP-7878 Re: Change in Puppet type management breaks defined class checks It works! Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7940) Support task diagnostics in a plan
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7940 Support task diagnostics in a plan Change By: Kenn Hussey Sprint: Tasks Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Maggie Dreyer Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3662) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3662 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion =
Jira (PDB-3659) Reconcile git commits and JIRA tickets (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3659 Reconcile git commits and JIRA tickets (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Use the ticketmatch script to 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. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an
Jira (PDB-3657) puppet-client-tools 1.2.2 2017-09-18 Release
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3657 puppet-client-tools 1.2.2 2017-09-18 Release Issue Type: Task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker puppet-client-tools 1.2.2 2017-09-18 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PDB-3663) Prepare long form release notes and short form release story (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3663 Prepare long form release notes and short form release story (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3660) Update version number in source (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3660 Update version number in source (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PDB-3661) Merge master into stable (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3661 Merge master into stable (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git
Jira (PDB-3665) Smoke test packages (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3665 Smoke test packages (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (PDB-3666) Go/no-go meeting (before noon PST) (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3666 Go/no-go meeting (before noon PST) (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) This should happen Monday-Thursday, before noon PST. We should not be shipping anything after noon PST or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: AJ Roetker AJ Roetker AJ Roetker AJ Roetker Molly Waggett
Jira (PDB-3670) Update dujour to notify users to use 1.2.2 (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3670 Update dujour to notify users to use 1.2.2 (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Update dujour to notify users to use 1.2.2. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3668) Docs pushed (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3668 Docs pushed (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3667) Packages pushed (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3667 Packages pushed (PDB 1.2.2) Issue Type: Sub-task Assignee: Molly Waggett Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (PDB-3658) Is the code ready for release? (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3658 Is the code ready for release? (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:27 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%221.2.2%22
Jira (PDB-3664) Tag the release and create packages (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3664 Tag the release and create packages (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Tag and create packages Tag using kerminator: ! tag 1.2.2 at with "1.2.2" Build using jenkins, or by running `rake package:implode package:bootstrap pl:jenkins:uber_build` when you've verified what version you're building (this uses the latest version of the packaging repo to build the packages). Dependencies: Every ticket before this except for release notes. Add Comment
Jira (PDB-3669) Send out announcements (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3669 Send out announcements (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Molly Waggett: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available"
Jira (PDB-3671) Close all resolved tickets in Jira (PDB 1.2.2)
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-3671 Close all resolved tickets in Jira (PDB 1.2.2) Issue Type: Sub-task Assignee: AJ Roetker Created: 2017/09/12 1:28 PM Priority: Normal Reporter: AJ Roetker (Initial planned release date: 2017-09-18) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%221.2.2%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-7920) Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass`
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7920 Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass` Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7945) Scope.to_s fails if there is no source and no path to env in Environment obj
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7945 Scope.to_s fails if there is no source and no path to env in Environment obj Issue Type: Bug Assignee: Henrik Lindberg Created: 2017/09/12 1:34 PM Priority: Normal Reporter: Henrik Lindberg If the environment does not refer to an actual environment directory the Scope.to_s method will fail when running puppet script since the Environment instance has a nil path. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7944) Bump puppet version to 4.10.8
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7944 Bump puppet version to 4.10.8 Change By: Kenn Hussey Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7942 Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Change By: Erik Dasher Story Points: 1 Sprint: Platform OS 2017-09-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7878) Change in Puppet type management breaks defined class checks
Title: Message Title Alexey Zhigaev commented on PUP-7878 Re: Change in Puppet type management breaks defined class checks I have the same issue. OS CentOS Linux release 7.3.1611 (Core) Packages puppet5-release-5.0.0-1.el7.noarch puppet-agent-5.1.0-1.el7.x86_64 puppetserver-5.0.0-1.el7.noarch java-1.8.0-openjdk-headless-1.8.0.141-1.b16.el7_3.x86_64 sudo puppetserver --version puppetserver version: 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Tiffany Longworth commented on PUP-4755 Re: Puppet config set --section main foo bar does not set or respect an empty [main] section Maggie Dreyer Karen Van der Veer it looks like that PR has been hanging out for a while - is there anyone who can review and merge https://github.com/puppetlabs/puppet/pull/6080 ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1746) virtual and is_virtual are reported incorrectly on freebsd proxmox vms
Title: Message Title Elof Ofel commented on FACT-1746 Re: virtual and is_virtual are reported incorrectly on freebsd proxmox vms Need I do something more on this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7878) Change in Puppet type management breaks defined class checks
Title: Message Title Thomas Hallgren commented on PUP-7878 Re: Change in Puppet type management breaks defined class checks Alexey Zhigaev, the only way I can see this happening, is if PuppetServer loaded one version of Puppet and the function call, when it loads for the first time, uses another version of Puppet. This will typically happen when the puppet installation is upgraded without restarting the server. I can't think of any other scenario that would provoke errors like this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7875) Add a run_task function
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7875 Add a run_task function Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3657) puppet-client-tools 1.2.2 2017-09-18 Release
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-3657 puppet-client-tools 1.2.2 2017-09-18 Release Change By: AJ Roetker Story Points: 1 Team: Enterprise in the Cloud Sprint: ETC 2017-10-03 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7920) Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass`
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7920 Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass` Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7920) Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass`
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7920 Puppet PRs failing travis against ruby 1.9.3 with `undefined method spec for nil:NilClass` Change By: Kenn Hussey Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7932) Make --strict=error when using --tasks feature
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7932 Make --strict=error when using --tasks feature Change By: Kenn Hussey Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7892) Add discovery to the Puppet Loader system
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7892 Add discovery to the Puppet Loader system Change By: Kenn Hussey Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7813 Yum package provider: ensure => latest fails when packages update available Change By: Maggie Dreyer Release Notes Summary: The yum package provider will now no longer crash when yum's output contains additional messaging that comes with some plugins. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7893) AIX 5.3 tests/resource/mount/mounted.rb failure
Title: Message Title John Duarte updated an issue Puppet / PUP-7893 AIX 5.3 tests/resource/mount/mounted.rb failure Change By: John Duarte Fix Version/s: PUP 5.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1747) facter seg faults after puppet cert sign in Cisco pipeline
Title: Message Title Erik Dasher commented on FACT-1747 Re: facter seg faults after puppet cert sign in Cisco pipeline This issue is resolved. We were able to run the presuite to completion with puppet agent build 47c1741f80ffc769332dd3fa4240d0d291d1cd65. Puppet Agent Build: 5.1.0.189.g47c1741 Puppet Agent Linky: http://builds.delivery.puppetlabs.net/puppet-agent/47c1741f80ffc769332dd3fa4240d0d291d1cd65 Jenkins Test Run (passing the presuite, TACACS and AAA failures outside scope of this ticket: https://jenkins-modules.puppetlabs.com/job/forge-netdev_cisco-ciscopuppet_intn-sys_smoke-master/165/PLATFORM=redhat-7-mda,WORKER_LABEL=beaker/consoleText Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Erik Dasher created an issue Puppet / PUP-7942 Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline Issue Type: Task Assignee: Unassigned Created: 2017/09/12 9:05 AM Priority: Normal Reporter: Erik Dasher We build puppet agent's for these Cisco platforms: cisco-wrlinux-5-x86_64 cisco-wrlinux-7-x86_64 We presently only ciscoxr-64a in the Non Standard pipeline. We should also test cisco*nx*-64 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: Faced by anyone with large scale decommissioning of nodes. CS Severity: 4 - Major CS Business Value: 4 - $ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Owen Rodabaugh updated an issue Facter / FACT-1653 External Facts from PowerShell do not parse structured output (JSON/YAML) Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: Most customers have at least some windows nodes. While the workaround for this is annoying rather than severe is contributes to the perception that windows is not a first class part of our ecosystem. CS Severity: 2 - Annoyance CS Business Value: 4 - $ CS Frequency: 4 - 50-90% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7942) Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline
Title: Message Title Erik Dasher commented on PUP-7942 Re: Add Cisco_Nexus-7-x86_64 as a test target in Puppet Agent Non Standard Pipeline https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/puppet-agent.yaml shows that cisconx-64 is present in the configuration. It's not being executed... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3501) PQL queries using fact names with dashes does not work
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3501 PQL queries using fact names with dashes does not work Change By: Russell Mull Fix Version/s: PDB 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
