Jira (FACT-1132) dmi resolver for OpenBSD
Title: Message Title Kylo Ginsberg commented on FACT-1132 Re: dmi resolver for OpenBSD We have no OpenBSD CI and this didn't break anything in non-OpenBSD CI, so resolving. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1120) does not build on FreeBSD
Title: Message Title Kylo Ginsberg commented on FACT-1120 Re: does not build on FreeBSD We have no FreeBSD CI and this didn't break anything in non-FreeBSD CI, so resolving. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1146) Regression: Facter 3 provides link local IPv6 address
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1146 Regression: Facter 3 provides link local IPv6 address Change By: Kylo Ginsberg Sprint: Client 2015-08-19 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Change By: Kylo Ginsberg Sprint: Client 2015-08-19 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Kylo Ginsberg commented on FACT-1147 Re: Interfaces with multiple IPs are not facted correctly I'd suggest we treat this as two issues: 1) returning the 'primary' address in the current structured (and legacy) facts 2) returning multiple IPs I just targeted this for 3.0.3 but just for the first of those two issues. The second issue is trickier since the current fact structure doesn't have an obviously clean way to represent this, so we should think about how we want to handle that. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Change By: Kylo Ginsberg Fix Version/s: FACT 3.0.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1146) Regression: Facter 3 provides link local IPv6 address
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1146 Regression: Facter 3 provides link local IPv6 address Change By: Kylo Ginsberg Fix Version/s: FACT 3.0.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1822) PR (1559): (DOC-2166) fix broken link - jtappa
Title: Message Title gepetto-bot commented on PDB-1822 Re: PR (1559): (DOC-2166) fix broken link - jtappa pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1693/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1822) PR (1559): (DOC-2166) fix broken link - jtappa
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1822 PR (1559): (DOC-2166) fix broken link - jtappa Issue Type: Task Assignee: Unassigned Created: 2015/07/23 6:07 PM Labels: github Priority: Normal Reporter: gepetto-bot (DOC-2166) fix broken link Author: Jorie Tappa <> Company: Github ID: jtappa Pull Request 1559 Discussion Pull Request 1559 File Diff Pull Request Description (webhooks-id: f2b5c4712edbd4de9f698dfae7b288ab)
Jira (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Hunter Haugen created an issue Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Issue Type: Bug Assignee: Unassigned Created: 2015/07/23 4:22 PM Environment: facter 3.0.1, sles 10 Priority: Normal Reporter: Hunter Haugen Interfaces can have multiple IP addresses of the same protocol (v4 or v6): t5yi12595vbs1v6:/etc # ip addr show lo 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Jira (PUP-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Michael Smith Status: Ready for CI Test Assignee: Kylo Ginsberg qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1966) It should be harder to revoke your CA cert
Title: Message Title Nick Walker assigned an issue to Eric Sorenson Puppet / PUP-1966 It should be harder to revoke your CA cert Change By: Nick Walker Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1966) It should be harder to revoke your CA cert
Title: Message Title Nick Walker commented on PUP-1966 Re: It should be harder to revoke your CA cert Agreed. Now that puppet cert revoke -a give a reasonable error and is not allowed this should fall into the exact same category. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1128) Intermittent failure attaching process to job object
Title: Message Title Michael Smith commented on FACT-1128 Re: Intermittent failure attaching process to job object Neither are we, I have no idea how to reproduce it. If from analysis we think using CREATE_BREAKAWAY_FROM_JOB would help, I'm fine adding it and continuing on our way. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1128) Intermittent failure attaching process to job object
Title: Message Title Branan Riley commented on FACT-1128 Re: Intermittent failure attaching process to job object The node on which this happened is long reaped, so I'm not sure the best way to try to repro/debug. What I'm reading would seem to indicate that CREATE_BREAKAWAY_FROM_JOB might help, but I'm unsure how and when facter is getting run in such a way that it's job object isn't compatible with the one it creates for the programs it calls. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1128) Intermittent failure attaching process to job object
Title: Message Title Branan Riley assigned an issue to Branan Riley Facter / FACT-1128 Intermittent failure attaching process to job object Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4848 Global parser = future with environment.conf parser = current gives an error Change By: Steve Barlow Scope Change Reason: Found by Nick during doc updates testing Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4848 Global parser = future with environment.conf parser = current gives an error Change By: Steve Barlow Scope Change Reason: Found by Nick during doc updates Scope Change Category: Found Original Estimate: 0 minutes Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1138 Improve os family and release reporting for Cisco NX-OS Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith assigned an issue to Scott Garman Facter / FACT-1138 Improve os family and release reporting for Cisco NX-OS Change By: Michael Smith Assignee: Michael Smith Scott Garman Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith updated an issue Facter / FACT-1138 Improve os family and release reporting for Cisco NX-OS Change By: Michael Smith Fix Version/s: FACT 3.x Fix Version/s: FACT 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith assigned an issue to Scott Garman Facter / FACT-1138 Improve os family and release reporting for Cisco NX-OS Change By: Michael Smith Assignee: Scott Garman Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4822) Regression PMT cannot connect to forge on OSX
Title: Message Title John Duarte commented on PUP-4822 Re: Regression PMT cannot connect to forge on OSX FYI: Puppet installed via gem uses the system ssl and is not affected by this issue. The following interaction of using the PMT on OS X 10.10 x86_64 with puppet-4.2.1 installed from gem confirms this. uudcnimp0uz8ydy:~ root# curl -O http://builds.puppetlabs.lan/puppet/4.2.1/artifacts/puppet-4.2.1.gem % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 2469k 100 2469k0 0 5874k 0 --:--:-- --:--:-- --:--:-- 5864k uudcnimp0uz8ydy:~ root# gem install puppet-4.2.1.gem Fetching: facter-2.4.4-universal-darwin.gem (100%) Successfully installed facter-2.4.4-universal-darwin Fetching: json_pure-1.8.2.gem (100%) Successfully installed json_pure-1.8.2
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Kylo Ginsberg commented on FACT-1138 Re: Improve os family and release reporting for Cisco NX-OS Michael Smith The version salad isn't all mapped out yet, but my understanding is that 2015.2.1 will add support for the various agents that didn't make the cut for 2015.2.0, including this (and Solaris/AIX/). This in turn means that it should include facter 3.1 (master) since that's where we've been working on that stuff. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4822) Regression PMT cannot connect to forge on OSX
Title: Message Title Matthaus Owens commented on PUP-4822 Re: Regression PMT cannot connect to forge on OSX Options 6. Apply homebrew's patch which sucks in certs from the system keystore during the postinstall. https://github.com/Homebrew/homebrew/blob/master/Library/Formula/openssl.rb#L106-L128 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith commented on FACT-1138 Re: Improve os family and release reporting for Cisco NX-OS Kylo Ginsberg is it? That probably means the version needs to be 3.0.3, and ported to stable. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Scott Garman commented on FACT-1138 Re: Improve os family and release reporting for Cisco NX-OS Michael Smith I'm booked solid today, and am on PTO Fri + Mon, but I can plan to verify this on Tuesday. This change is planned for 2015.2.1, so there's no big rush. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title Verne Lindner commented on PUP-2838 Re: Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names Scott Walker I'm not following your comment about UI graphs and CL --graph use: would you explain what the concern is? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1138) Improve os family and release reporting for Cisco NX-OS
Title: Message Title Michael Smith commented on FACT-1138 Re: Improve os family and release reporting for Cisco NX-OS Scott Garman is this something you can review once it finishes CI? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title Rob Reynolds commented on PUP-1165 Re: Spurious 'trigger changed' messages generated by scheduled task provider I agree - should we file a documentation ticket Michelle Fredette? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4828) Scope out a HOCON port to C++
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-4828 Scope out a HOCON port to C++ Change By: Maggie Dreyer Preben's notes about his experience porting to Ruby can be found here:https://docs.google.com/a/puppetlabs.com/document/d/1-rVv-Yj5bO5I4g6c65wbxHimxh6C_Od9Y1yl6MMrWwE/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4828) Scope out a HOCON port to C++
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-4828 Scope out a HOCON port to C++ Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Ian Au commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) In pip.rb, I see: if Facter.value(:osfamily) == "RedHat" and Facter.value(:operatingsystemmajrelease).to_i < 7 "pip-python" else "pip" end To simplify things, if it's Redhat 6, why don't we just also use "pip" instead of "pip-python". Older versions of python-pip also creates /usr/bin/pip Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Stuart James commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
So when OSFamily is detected as Redhat on Centos6/RHEL6 we need puppet to now look at probably the standard location of /usr/bin/pip (as it appears as though python-pip EPEL has removed the symlink it use to provide) or also include this location as one of its search options.
As a temporary workaround i added this to the manifest
file { '/usr/bin/pip-python':
ensure => 'link',
target => '/usr/bin/pip',
require => Package["python-pip"]
}
and ensure that its a requirement prior to using pip as a provider in package installation
package {"supervisor":
ensure => installed,
provider => pip,
Jira (PDB-1821) better postgres coverage for extensions testing
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1821 better postgres coverage for extensions testing Issue Type: Improvement Assignee: Unassigned Created: 2015/07/23 8:12 AM Priority: Normal Reporter: Wyatt Alt A lot of our testing in pe-puppetdb-extensions relies on the with-pdb-instance function, which never uses postgres. Since sync is a postgres-only feature, we should fix that function to work with postgres (or come up with some other approach.) Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4920) Can Service disable before stopping?
Title: Message Title
C Lang created an issue
Puppet / PUP-4920
Can Service disable before stopping?
Issue Type:
Bug
Affects Versions:
PUP 3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2015/07/23 7:55 AM
Environment:
CentOS 7.x, Epel Puppet 3.6.2
Priority:
Normal
Reporter:
C Lang
I'm attempting to have Puppet disable and stop itself after creating a cron job to run the agent. This mostly works, but has an annoying glitch.
service { 'puppet':
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title C Lang commented on PUP-1165 Re: Spurious 'trigger changed' messages generated by scheduled task provider Beyond documentation, shouldn't day_of_week either work or be removed? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1146) Regression: Facter 3 provides link local IPv6 address
Title: Message Title Brian Rak commented on FACT-1146 Re: Regression: Facter 3 provides link local IPv6 address Facter 2: https://github.com/puppetlabs/facter/blob/2.x/lib/facter/ipaddress6.rb#L31 It's ignoring addresses beginning with fe80 (ignore that ::1 part, it doesn't make any sense) Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1146) Regression: Facter 3 provides link local IPv6 address
Title: Message Title Brian Rak created an issue Facter / FACT-1146 Regression: Facter 3 provides link local IPv6 address Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/23 7:22 AM Environment: CentOS 6 x86_64 Facter 3.0.1 (commit 9b1ef723a1494a01e0eccfe93a75fd43316690c2) Priority: Normal Reporter: Brian Rak Given an interface with multiple IPv6 addresses, facter is returning the link-local one only. The link local address is not very useful. The network6/netmask6 values are correct. For example (irrelevant information removed) # ip -6 addr show br0 6: br0: mtu 1500
Jira (PUP-4916) fix hiera documentation in relation to deep_merge_options in hiera.yaml
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4916 fix hiera documentation in relation to deep_merge_options in hiera.yaml Change By: Henrik Lindberg Component/s: Client Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1819) PR (1557): (maint) Fix broken dashboard urls - mullr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1819 PR (1557): (maint) Fix broken dashboard urls - mullr Change By: Kenneth Barber Affects Version/s: PDB 3.0.1 Fix Version/s: PDB 3.0.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1530) Upgrade to latest clojure.java.jdbc
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1530 Upgrade to latest clojure.java.jdbc Change By: Kenneth Barber Fix Version/s: PDB 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Ian Au commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Stuart, I made the same mistake as you did when troubleshooting this. I originally sym linked /usr/bin/python-pip to /usr/bin/pip and it still wasn't working. Then I realized the naming typo. It should actually be a sym link from /usr/bin/pip-python to /usr/bin/pip. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1810) Filesync Service: Add new git sha1 field
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1810 Filesync Service: Add new git sha1 field Change By: Kenneth Barber This ticket should cover (in theory) the entirety of the PDB-only requirements for providing the Filesync service solution. This depends on Puppet work to be done by one of the Puppet teams before this can commence.My 'in my head' estimate is no more than 5 story points, but leaving story points blank so we can all discuss a proper estimate later on.h2. OverviewThere is a largish project that requires a small change to the PDB storage, for more information see here:https://docs.google.com/a/puppetlabs.com/document/d/1HJSdlluYmNKfOOrFIvPAi79YQuVYSnq7XJGbfEqgi-U/editFrom a PuppetDB perspective the proposed change is basically to add a new field to the following object types during submission and query:* Catalogs* ReportsThis field represents the sha1 hash of the internal VCS repository (probably git). The proposal is to simply include this in the wire format during command submission, and have it returnable (and queryable as a string) via the matching query endpoints.h2. Tasks* Create schema migrations to add the sha1 fields to each of the required tablesprobably just ‘reports’ and ‘catalogs’** not sure if its even worth normalizing this, I doubt it. Worth pondering later on.** Update the commands so that they can receive this new sha1 type and store it* Update the terminus to send this new data field** Obviously this field needs to be lifted from Puppet first from the report and catalog parts.** We need to be backward compatible here, in that we need to support old versions of Puppet that may not have this field (for reports at least, we may see a bump in the report version here for example).** As long as the Puppet interface isn’t surprising this should be very BAU.* Add query and view capabilities to all the main endpoints for this new field** Again, this should be a very BAU query engine change.** This should make export/import just ‘work’, although I think we need to bump the versioning when we do this in the export metadata.* Anonymization support** I highly doubt this is needed, but worth noting. Add Comment
Jira (PUP-4919) static compiler always sets ensure parameter to 'file' if a source is declared
Title: Message Title
Taylan Develioglu updated an issue
Puppet / PUP-4919
static compiler always sets ensure parameter to 'file' if a source is declared
Change By:
Taylan Develioglu
The static_compiler catalog terminus always sets ensure to 'file' on file resources as long as the resource has a source parameter declared.It does this even if the ensure parameter is explicitly declared.Applying a catalog, with the following file resource, compiled with static compiler, will create the file anyway. {code} file { '/tmp/statically_compiled.txt': ensure => absent, mode => 0755, owner => 'root', group => 'root', source => 'puppet:///modules/foo/statically_compiled.txt',} {code} ...Notice: /Stage[main]/Main/File[/tmp/statically_compiled.txt]/ensure: defined content as '{md5}8fea78c7e5ed0f5b3bd13565589a6f7c'... The catalog confirms ensure is being set to "file" :irb(main):001:0> require 'json'=> trueirb(main):002:0> JSON.load(File.read('foo.json'))['data']['resources'].find { |res| res['title'] == '/tmp/statically_compiled.txt' }=> {"type"=>"File", "title"=>"/tmp/statically_compiled.txt", "tags"=>["file", "class"], "file"=>"/etc/puppet/environments/tdevelioglu/puppet/manifests/site.pp", "line"=>7, "exported"=>false, "parameters"=>{"ensure"=>"file", "mode"=>"0755", "owner"=>"root", "group"=>"root", "ignore"=>[".svn", "CVS", ".git"], "content"=>"{md5}8fea78c7e5ed0f5b3bd13565589a6f7c", "checksum"=>"md5"}}This is inconsistent with the behavior of the normal compiler, where a file's ensure parameter is enforced regardless of the value of the source parameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4919) static compiler always sets ensure parameter to 'file' if a source is declared
Title: Message Title
Taylan Develioglu created an issue
Puppet / PUP-4919
static compiler always sets ensure parameter to 'file' if a source is declared
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Created:
2015/07/23 5:19 AM
Priority:
Normal
Reporter:
Taylan Develioglu
The static_compiler catalog terminus always sets ensure to 'file' on file resources as long as the resource has a source parameter declared. It does this even if the ensure parameter is explicitly declared.
Applying a catalog, with the following file resource, compiled with static compiler, will create the file anyway.
file { '/tmp/statically_compiled.txt': ensure => absent, mode => 0755, owner => 'root', group => 'root', source => 'puppet:///modules/foo/statically_compiled.txt', }
... Notice: /Stage[main]/Main/File[/tmp/statically_compiled.txt]/ensure: defined content as ' {md5}8fea78c7e5ed0f5b3bd13565589a6f7c' ... The catalog confirms ensure is being set to "file" : irb(main):001:0> require 'json' => true irb(main):002:0> JSON.load(File.read('foo.json'))['data']['resources'].find { |res| res['title'] == '/tmp/statically_compiled.txt' } => {"type"=>"File", "title"=>"/tmp/statically_compiled.txt", "tags"=>["file", "class"], "file"=>"/etc/puppet/environments/tdevelioglu/puppet/manifests/site.pp", "line"=>7, "exported"=>false, "parameters"=>{"ensure"=>"file", "mode"=>"0755", "owner"=>"root", "group"=>"root", "ignore"=>[".svn", "CVS", ".git"], "content"=>"{md5}
8fea78c7e5ed0f5b3bd13565589a6f7c", "checks
Jira (PUP-4604) Port fix for pip provider on more recent RedHat operating systems.
Title: Message Title Stuart James commented on PUP-4604 Re: Port fix for pip provider on more recent RedHat operating systems. please see https://tickets.puppetlabs.com/browse/PUP-3829?focusedCommentId=198351&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198351 The update to python-pip has caused the issue where by on Centos 6 (assuming RHEL6) it is looking for pip-python binary. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Stuart James commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
ran an strace on it
stat("/usr/local/sbin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/usr/local/bin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/sbin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/bin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/usr/sbin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/usr/bin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/root/bin/pip-python", 0x7ffdfe128af0) = -1 ENOENT (No such file or directory)
stat("/usr/local/sbin/pip-python", 0x7ffdfe113e80) = -1 ENOENT (No such file or directory)
stat("/usr/local/bin/pip-python", 0x7ffdfe113e80) = -1 ENOENT (No such file or directory)
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Stuart James commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) maybe this relates to PUP-4604 . As of the most recent update to either python-pip or puppet caused this issue for me. I created a symlink but i still receive the "Could not locate the pip command" ls -l /usr/bin/python-pip lrwxrwxrwx. 1 root root 12 Jul 23 06:27 /usr/bin/python-pip -> /usr/bin/pip rpm -qf /usr/bin/pip python-pip-7.1.0-1.el6.noarch Looking at my yum.log i think the issue exists with the python-pip rpm from EPEL as it worked when i initially built the server on the 9th (with puppet-3.8.1-1.el6.noarch ) Jul 09 12:27:14 Installed: python-pip-1.3.1-4.el6.noarch Jul 22 06:19:03 Updated: python-pip-7.1.0-1.el6.noarch
Jira (PDB-1820) Include 'status' field in 'nodes' endpoint
Title: Message Title David McCauley created an issue PuppetDB / PDB-1820 Include 'status' field in 'nodes' endpoint Issue Type: New Feature Affects Versions: PDB 3.0.0 Assignee: Unassigned Components: PE Created: 2015/07/23 3:17 AM Priority: Normal Reporter: David McCauley Currently in PE we display a view of all available nodes in a table. A column of this table is the 'run status' of a given node. To acquire the data for this table we first make a call to the 'nodes' endpoint for all of the data except the 'run status' where we make a separate request to the 'reports'. We then combine this data and pass it to the UI. It would help us greatly if a new 'node' endpoint were to contain this 'status' field from the latest report. We would like to be able to run filter queries upon this field and page on this new endpoint if possible.
Jira (PUP-4918) Logrotate and init scripts permission and signal issues
Title: Message Title Lukas Zapletal created an issue Puppet / PUP-4918 Logrotate and init scripts permission and signal issues Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2015/07/23 1:45 AM Priority: Normal Reporter: Lukas Zapletal This patch updates logrotate script and aligns it what is defined in defaults.rb, specifically: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L1036-L1046 and https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L1258-L1274 Because of logrotate and puppet during restart were both "fighting" for correct file permissions, this was causing issues with SELinux. Also fixed paths which has been incorrect for Fedora/RHEL systems (/var/log/puppetlabs vs /var/log/puppet). It contains both now which seems to work just fine. I am not adding logrotate scriplet for master tho as I don't know if it supports signals. When running master under webrick one should not expect fully working log rotation tho. Open for discussion. As part of this patch, I am also updating Red Hat startup scripts: RHEL6 traditional UNIX-like "reload" command was actually sending HUP signal and therefore restarting daemon instead correct USR1 RHEL7 systemd unit was extended with "reload" command using USR1 signal https://github.com/puppetlabs/puppet/pull/4097
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Paul W created an issue Puppet / PUP-4917 puppet resource package does not display McAfee Agent Issue Type: Bug Affects Versions: puppet-agent 1.2.2, puppet-agent 1.2.1 Assignee: Unassigned Attachments: ProgramsAndFeaturesW2008.png, ProgramsAndFeaturesW2012.png Components: Windows Created: 2015/07/23 1:30 AM Environment: Operating System information provided by Facter: kernel => windows kernelmajversion => 6.3 kernelrelease => 6.3.9600
Jira (FACT-1145) Virtualization resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1145 Re: Virtualization resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title Scott Walker commented on PUP-2838 Re: Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names Beth Cornils I ran into this too generating a graph using the agent running on master. Is there any concern that introduction of graphs into the UI might draw users to try --graph with the agent? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1145) Virtualization resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1145 Virtualization resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 1:16 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Facter is currently lacking a virtualization resolver for OpenBSD. Add Comment
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1144 Re: Memory resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1144 Memory resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 1:09 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Facter is currently lacking a memory resolver for OpenBSD. Add Comment
Jira (FACT-1143) Processor resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1143 Re: Processor resolver for OpenBSD PR Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1143) Processor resolver for OpenBSD
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1143 Processor resolver for OpenBSD Issue Type: Improvement Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/23 12:31 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse Currently there is no processor resolver for OpenBSD. Add Comment
