Jira (PUP-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Eric Thompson commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong The instructions for cleaning a -Windows node's certificate- are wrong Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong CI Completed with success https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/159/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti assigned an issue to Erick Banks Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Change By: Glenn Sarti Assignee: qa Erick Banks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti assigned an issue to qa Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Change By: Glenn Sarti Status: Ready for CI Test Assignee: Glenn Sarti qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Zachary Smith commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k Eric Sorenson Peter Huene I would be glad to help. At this point in time without adding hooks to Filesync per chris prices comment, I think we could hack something together in a few ways: 1. Code manager supports an array of hooks that it will post to when its done: https://docs.puppet.com/pe/2016.2/code_mgr_custom.html#postenvironmenthooks ( I believe however this is done after code manager deploys to staging and doesn't block so it might not catch the new type until the next deploy ) This is the only current "supported" hook system but basically doesn't really work for this system as its non-blocking so file sync could be trigger before generate completes ( and often would ). 2. R10k has a generic postrun command that it can do https://github.com/puppetlabs/r10k/blob/master/doc/dynamic-environments/configuration.mkd#postrun This is more or less the correct timing as it would block while code manager executes and would happen before file sync was trigger by code manager. This is basically what FOSS will use. r10k.yaml which holds this is dynamically generated from code managers hocon file, and this value is not exposed. So while this is basically the right time to trigger in the timeline, to make this functionality work we would have to hack the auto generated config file. 3. We could try and hack together .git/hooks in puppet_code.git , I tried this one time and it didn't work but there might be a way to do it. -Z Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Sean Griffin commented on FACT-1405 Re: Facter does not like next hop flags in ip route output The fix doesn't seem to work. On the our pooler's ubuntu 16.04 vm, 'ip route show' does not add 'onlink' at the end of the default interface line. To test this I replaced the ip command so that it returns a line for the default interface with 'onlink' added to make it behave like the user's description. During its execution, 'facter networking' calls ip 4 times. If called with the first argument being 'link' then the original ip command is invoked (/bin/ip). Here is the replacement ip command: PuppetLabs382:01-160714 sgriffin$ cat ip #! /bin/bash echo $* >> /tmp/ip-args if [ "$1" = "link" ] then /bin/ip $* exit $?
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Eric Thompson assigned an issue to qa Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Eric Thompson Status: Resolved Ready for Test Resolution: Fixed Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1405) Facter does not like next hop flags in ip route output
Title: Message Title
Eric Thompson updated an issue
Facter / FACT-1405
Facter does not like next hop flags in ip route output
Change By:
Eric Thompson
Comment:
validated on:{code}root@u4w9tscddf5tsxe:~# facter os{ architecture => "amd64", distro => {codename => "xenial",description => "Ubuntu 16.04 LTS",id => "Ubuntu",release => { full => "16.04", major => "16.04"} },{code}at puppet-agent master sha: 8ae9f84f8da7abe37d4c68f816677306814b164c{code}2016-07-14 15:38:02.282647 DEBUG puppetlabs.facter - resolving networking facts.2016-07-14 15:38:02.283314 DEBUG leatherman.execution:88 - executing command: /sbin/ip route show2016-07-14 15:38:02.284936 DEBUG | - default via 10.32.112.1 dev ens322016-07-14 15:38:02.285518 DEBUG | - 10.32.112.0/20 dev ens32 proto kernel scope link src 10.32.115.2442016-07-14 15:38:02.286171 DEBUG leatherman.execution:555 - process exited with status code 0.2016-07-14 15:38:02.286797 DEBUG leatherman.execution:88 - executing command: /sbin/ip -6 route show2016-07-14 15:38:02.288177 DEBUG | - fe80::/64 dev ens32 proto kernel metric 256 pref medium2016-07-14 15:38:02.288777 DEBUG leatherman.execution:555 - process exited with status code 0.2016-07-14 15:38:02.289637 DEBUG puppetlabs.facter - hostname "u4w9tscddf5tsxe" could not be resolved: hostname may not be externally resolvable.2016-07-14 15:38:02.290370 DEBUG puppetlabs.facter - searching "/var/lib/dhclient" for dhclient lease files.2016-07-14 15:38:02.290926 DEBUG puppetlabs.facter - searching "/var/lib/dhcp" for dhclient lease files.2016-07-14 15:38:02.291534 DEBUG puppetlabs.facter - reading "/var/lib/dhcp/dhclient.ens33.leases" for dhclient lease information.2016-07-14 15:38:02.292122 DEBUG puppetlabs.facter - reading "/var/lib/dhcp/dhclient.ens32.leases" for dhclient lease information.2016-07-14 15:38:02.292748 DEBUG puppetlabs.facter - searching "/var/lib/dhcp3" for dhclient lease files.2016-07-14 15:38:02.293300 DEBUG puppetlabs.facter - searching "/var/lib/NetworkManager" for dhclient lease files.2016-07-14 15:38:02.293888 DEBUG puppetlabs.facter - searching "/var/db" for dhclient lease files.2016-07-14 15:38:02.294529 DEBUG leatherman.execution:88 - executing command: dhcpcd -U lo2016-07-14 15:38:02.295230 DEBUG leatherman.execution:413 - dhcpcd was not found on the PATH.2016-07-14 15:38:02.295815 DEBUG leatherman.execution:88 - executing command: /sbin/ip link show ens322016-07-14 15:38:02.296882 DEBUG | - 2: ens32: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10002016-07-14 15:38:02.296996 DEBUG | - link/ether 00:50:56:8f:51:65 brd ff:ff:ff:ff:ff:ff2016-07-14 15:38:02.297166 DEBUG leatherman.execution:555 - process exited with status code 0.2016-07-14 15:38:02.297385 DEBUG leatherman.execution:88 - executing command: /sbin/ip link show lo2016-07-14 15:38:02.298322 DEBUG | - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 12016-07-14 15:38:02.298446 DEBUG | - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:002016-07-14 15:38:02.298586 DEBUG leatherman.execution:555 - process exited with status code 0.2016-07-14 15:38:02.298782 DEBUG puppetlabs.facter - fact "ipaddress_ens32" has resolved to "10.32.115.244".{code}
Jira (PUP-6438) Parallel spec on Windows improvements, assoc lib/provider refactors
Title: Message Title Daniel Lu updated an issue Puppet / PUP-6438 Parallel spec on Windows improvements, assoc lib/provider refactors Change By: Daniel Lu As per comments on https://github.com/puppetlabs/puppet/pull/5041* Refactor lib/provider files to expose $CHILD_STATUS.exit status to the spec tests in a way that allows stubbing / mocking as with execution_spec or pacman_spec * Take a closer look at settings_spec changes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-6507 Puppet help: Hide bad subcommands, and sort remainder by usefulness Issue Type: Improvement Assignee: Unassigned Created: 2016/07/14 4:08 PM Priority: Normal Reporter: Nicholas Fagerlund The CLI leads meeting recently discussed the current slate of built-in Puppet subcommands (all thirty of them), and came to the conclusion that some of them are useless and/or harmful. Deprecating and removing subcommands is a larger task, and improving the interfaces of useful-but-problematic ones is an even bigger one. But we identified two things we can do today to vastly improve the user experience. Namely: puppet help's list of subcommands should omit the useless or confusing ones completely. This won't break the workflow of anyone who's actually using them, but will keep new users from hitting their heads on exposed nails or stepping into the insulation. The list of remaining subcommands should be sorted into categories according to their usefulness, so users who haven't memorized everything can more easily stay on the rails. The useless commands The CLI leads team has broadly agreed that the following subcommands aren't good news. This list mostly focuses on the "indirector faces," but also includes some other stuff. puppet file
Jira (PUP-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson Release Notes Summary: fix a regression from commit eccd3b which modified puppet to not swallow errors silently, but it causes caused a regression when a puppet sub-application raises an error Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson Release Notes Summary: commit eccd3b modified puppet to not swallow errors silently, but it causes a regression when a puppet sub-application raises an error Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson commented on PUP-6425 Re: Regression: puppet help errors out if any application raises while generating help validated on ubuntu1604 at puppet-agent master SHA: 8ae9f84f8da7abe37d4c68f816677306814b164c root@u4w9tscddf5tsxe:~# vi /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb root@u4w9tscddf5tsxe:~# puppet help Usage: puppet [options] [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally caLocal Puppet Certificate Authority management.
Jira (PUP-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6425) Regression: puppet help errors out if any application raises while generating help
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6425 Regression: puppet help errors out if any application raises while generating help Change By: Eric Thompson QA Risk Assessment Reason: regression due to very recent commit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Glenn Sarti assigned an issue to Erick Banks Puppet / PUP-6398 Executing parallel specs on Windows is not reliable Change By: Glenn Sarti Assignee: qa Erick Banks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Glenn Sarti assigned an issue to qa Puppet / PUP-6398 Executing parallel specs on Windows is not reliable Change By: Glenn Sarti Status: Ready for CI Test Assignee: Ethan Brown qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Glenn Sarti commented on PUP-6398 Re: Executing parallel specs on Windows is not reliable CI Started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_init-van-component_master/352/ CI Completed with success at; https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_pkg-van-promote_master/260/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1512) Puppet help silently exits when an application fails to load
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1512 Puppet help silently exits when an application fails to load Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1512) Puppet help silently exits when an application fails to load
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1512 Puppet help silently exits when an application fails to load Change By: Eric Thompson Release Notes Summary: fix a problem where `puppet help` face-based application could silently fail when trying to display help for each installed application Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1512) Puppet help silently exits when an application fails to load
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-1512 Puppet help silently exits when an application fails to load Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1512) Puppet help silently exits when an application fails to load
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1512 Puppet help silently exits when an application fails to load Change By: Eric Thompson Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1512) Puppet help silently exits when an application fails to load
Title: Message Title Eric Thompson commented on PUP-1512 Re: Puppet help silently exits when an application fails to load validated on ubuntu1604 at puppet-agent master SHA: 8ae9f84f8da7abe37d4c68f816677306814b164c root@u4w9tscddf5tsxe:~# puppet module install msopentech-windowsazure Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /etc/puppetlabs/code/environments/production/modules └── msopentech-windowsazure (v1.2.0) root@u4w9tscddf5tsxe:~# puppet help Usage: puppet [options] [options]
Jira (PUP-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6094
{{puppet -h|--help}} should be equivalent to {{puppet help}}
Change By:
Eric Thompson
QA Status:
Reviewed
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6094
{{puppet -h|--help}} should be equivalent to {{puppet help}}
Change By:
Eric Thompson
Release Notes Summary:
fixed slight differences between the output of `puppet --help` and `puppet help`
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6094
{{puppet -h|--help}} should be equivalent to {{puppet help}}
Change By:
Eric Thompson
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Eric Thompson commented on PUP-6094
Re: {{puppet -h|--help}} should be equivalent to {{puppet help}}
validated on ubuntu1604 at puppet-agent master SHA: 8ae9f84f8da7abe37d4c68f816677306814b164c
root@u4w9tscddf5tsxe:~# puppet --help > dashdash
root@u4w9tscddf5tsxe:~# puppet help > face
root@u4w9tscddf5tsxe:~# diff dashdash face
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Sean McDonald updated an issue Facter / FACT-1454 When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults Change By: Sean McDonald Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Eric Thompson assigned an issue to Eric Thompson
Puppet / PUP-6094
{{puppet -h|--help}} should be equivalent to {{puppet help}}
Change By:
Eric Thompson
Assignee:
qa Eric Thompson
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Eric Thompson updated an issue Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Eric Thompson Release Notes Summary: Facter now constructs IP route information correctly when there are additonal flags in the ip route Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong CI Started https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_init-van-component_stable/212/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1405) Facter does not like next hop flags in ip route output
Title: Message Title
Eric Thompson commented on FACT-1405
Re: Facter does not like next hop flags in ip route output
validated on:
root@u4w9tscddf5tsxe:~# facter os
{
architecture => "amd64",
distro => {
codename => "xenial",
description => "Ubuntu 16.04 LTS",
id => "Ubuntu",
release => {
full => "16.04",
major => "16.04"
}
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Eric Thompson updated an issue Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Eric Thompson Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith assigned an issue to qa Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Nathaniel Smith Status: Ready for CI Test Assignee: Nathaniel Smith qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong Merged from stable to master at; https://github.com/puppetlabs/puppet/commit/b4c8da62acd10a6caa0103e3198a05bf5aa49084 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong Merged into master at; https://github.com/puppetlabs/puppet/commit/b5780b02053eda7f22859ce51b793feb70aac11b Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti commented on PUP-6115 Re: The instructions for cleaning a Windows node's certificate are wrong Repro Steps 1 Agent (Windows Server 2012 R2) 2 Masters (2 Learning VMs) Assumes the agent does not have any certs on the two masters git clone the PR bundle install etc. Change the hosts file on the agent to point puppet to Master #1 Delete C:\ProgramData\PuppetLabs\puppet\etc\ssl puppet agent -t Accept the cert on Master 1 puppet agent -t (Should do a succesful puppet run) Copy C:\ProgramData\PuppetLabs\puppet\etc\ssl to C:\ProgramData\PuppetLabs\puppet\etc\ssl.master1 Change the hosts file on the agent to point puppet to Master #2 Delete C:\ProgramData\PuppetLabs\puppet\etc\ssl puppet agent -t Accept the cert on Master 2 puppet agent -t (Should do a succesful puppet run) Copy C:\ProgramData\PuppetLabs\puppet\etc\ssl.master1\private_keys to C:\ProgramData\PuppetLabs\puppet\etc\ssl\private_keys puppet agent -t
Jira (PDB-2865) Implement a quicker "inner loop" retry of commands
Title: Message Title Ryan Senior assigned an issue to Andrew Roetker PuppetDB / PDB-2865 Implement a quicker "inner loop" retry of commands Change By: Ryan Senior Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2853) (upgrade PDB RBAC dependency) clj-rbac-client shows null for rbac-status if rbac-url isn't configured
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2853 (upgrade PDB RBAC dependency) clj-rbac-client shows null for rbac-status if rbac-url isn't configured Change By: Andrew Roetker Summary: (upgrade PDB RBAC dependency) clj-rbac-client shows null for rbac-status if rbac-url isn't configured Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2856) OSX and Windows testing related to the PuppetDB CLI in PE
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2856 OSX and Windows testing related to the PuppetDB CLI in PE Change By: Andrew Roetker Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2224) Create FOSS PDB CLI full stack tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2224 Create FOSS PDB CLI full stack tests Change By: Andrew Roetker Summary: Create FOSS PDB CLI full stack tests Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6427) Intermittent Appveyor PR CI failure due to password complexity
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6427 Intermittent Appveyor PR CI failure due to password complexity Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6427) Intermittent Appveyor PR CI failure due to password complexity
Title: Message Title Glenn Sarti commented on PUP-6427 Re: Intermittent Appveyor PR CI failure due to password complexity FR not required as the code paths changed are extensively exercised by PR CI and Jenkins CI processes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6427) Intermittent Appveyor PR CI failure due to password complexity
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6427 Intermittent Appveyor PR CI failure due to password complexity Change By: Glenn Sarti Acceptance Criteria: Spec tests use complex passwordsSpec tests with complex passwords succeed in PR and Jenkins CI processes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6427) Intermittent Appveyor PR CI failure due to password complexity
Title: Message Title Glenn Sarti commented on PUP-6427 Re: Intermittent Appveyor PR CI failure due to password complexity CI Started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_init-van-component_stable/210/ CI Completed with success; https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/157/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6506) Running puppet with no arguments should allow a default operation to specified in puppet.conf
Title: Message Title Zachary Smith updated an issue Puppet / PUP-6506 Running puppet with no arguments should allow a default operation to specified in puppet.conf Change By: Zachary Smith One of the more interesting thing I have noticed and like liked about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent \-t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like `\-\-test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like `--environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command. We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entrie is there, and we could have a notice at the begining of the runs saying something like "using default_args: puppet agent \-t \-\-noop \-\-environment foo" to take some of the magic out of it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message
Jira (PUP-6506) Running puppet with no arguments should allow a default operation to specified in puppet.conf
Title: Message Title Zachary Smith updated an issue Puppet / PUP-6506 Running puppet with no arguments should allow a default operation to specified in puppet.conf Change By: Zachary Smith One of the more interesting thing I have noticed and liked about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent \-t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like `\-\-test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like `--environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command. We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entrie entry is not there, and we could have a notice at the begining beginning of the runs saying something like "using default_args: puppet agent \-t \-\-noop \-\-environment foo" to take some of the magic out of it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You
Jira (PUP-6506) Running puppet with no arguments should allow a default operation to specified in puppet.conf
Title: Message Title Zachary Smith updated an issue Puppet / PUP-6506 Running puppet with no arguments should allow a default operation to specified in puppet.conf Change By: Zachary Smith One of the more interesting thing I have noticed and like about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent \ -t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like `--test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like `--environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command. We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entrie is there, and we could have a notice at the begining of the runs saying something like "using default_args: puppet agent -t --noop --environment foo" to take some of the magic out of it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you
Jira (PUP-6506) Running puppet with no arguments should allow a default operation to specified in puppet.conf
Title: Message Title Zachary Smith updated an issue Puppet / PUP-6506 Running puppet with no arguments should allow a default operation to specified in puppet.conf Change By: Zachary Smith One of the more interesting thing I have noticed and like about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent \-t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like ` \ - \ -test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like `--environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command. We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entrie is there, and we could have a notice at the begining of the runs saying something like "using default_args: puppet agent \ -t \ - \ -noop \ - \ -environment foo" to take some of the magic out of it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this
Jira (PUP-6506) Running puppet with no arguments should allow a default operation to specified in puppet.conf
Title: Message Title Zachary Smith created an issue Puppet / PUP-6506 Running puppet with no arguments should allow a default operation to specified in puppet.conf Issue Type: New Feature Assignee: Unassigned Created: 2016/07/14 10:17 AM Priority: Normal Reporter: Zachary Smith One of the more interesting thing I have noticed and like about other industry tools like chef-client, is that it is a single command. I think puppet is often more complicated then it needs to be for common operations. I think it would be nice to be able to specify somthing like `default_args` in puppet.conf to allow novice users to simply run `puppet` and have default args set to `'agent t'`. Right now running puppet with no arguments holds no value, and because we have confusing arguments, new users have to learn concepts like ` test` is 3 arguments put together, they also often confuse apply and agent when first learning puppet. If am the administator of puppet , it would be nice to have a pre-canned set of arguments that I could specify from the command line, especially for things like ` -environment foo` where I could manage that and just teach developers `puppet`. I think this would lower the price of admission for such a common command. We could default it to show the current behavior "See 'puppet help' for help on available puppet subcommands" if the puppet.conf entrie is there, and we could have a notice at the begining of the runs saying something like "using default_args: puppet agent -t --noop --environment foo" to take some of the magic out of it.
Jira (PDB-2706) investigate convergence test failure 5/17/16
Title: Message Title Rob Browning commented on PDB-2706 Re: investigate convergence test failure 5/17/16 Tested both master and stable (as of yesterday) ~10x with the seed in the gist and didn't see any failures, so we're going to close this for now. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2706) investigate convergence test failure 5/17/16
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-2706 investigate convergence test failure 5/17/16 Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Sean Griffin assigned an issue to Unassigned Facter / FACT-1449 Facter does not honor digits as Strings Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tom Limoncelli commented on PUP-3483 Re: Systemd provider doesn't scan for changed units I think the best solution is the ::systemd module from camptocamp: Any time you modify a unit file (.service) have it notify Exec['systemctl-daemon-reload']. https://github.com/camptocamp/puppet-systemd The problem, however, is that modules like puppetlabs-firewall can't be expected to depend on a third-party module like camptocamp/puppet-systemd. The correct solution is for Puppet to make The One True Exec['systemctl-daemon-reload'] and have everyone standardize on it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Facter / FACT-1449 Facter does not honor digits as Strings Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6503) Types from invalid modules do not fail
Title: Message Title Henrik Lindberg commented on PUP-6503 Re: Types from invalid modules do not fail My 2c: No hyphens in names !!! Compilation should raise "no such resource type" if the type is in a directory with a hyphen (just as if it was erroneously named with other random chars) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Geoff Williams commented on PUP-3483 Re: Systemd provider doesn't scan for changed units I'm hitting this too - In my case I've created the exec resource but am now having to reference it all over the place as the packaging cannot fix the things I need since I'm writing puppet code to update the systemd unit files/environment settings after-the-fact. In addition to this I'm having to write code to special-case windows in order to not attempt to interact with systemd at all. To me, it would be a much cleaner solution if the puppet service resource could handle any required reloads once and for all so that I don't have to Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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.
