Jira (PUP-6185) Windows stat / lstat are inefficient - may calculate mode too frequently
Title: Message Title Ethan Brown created an issue Puppet / PUP-6185 Windows stat / lstat are inefficient - may calculate mode too frequently Issue Type: Bug Affects Versions: PUP 4.4.1 Assignee: Unassigned Created: 2016/04/18 9:57 PM Fix Versions: PUP 4.5.0 Labels: windows Priority: Normal Reporter: Ethan Brown Based on how stat and lstat are patched in Windows, there are a couple of problems: Monkey patches should probably execute code lazily, rather than optimistically (if possible) - i.e. don't calculate the lstat type until is actually asked for, then keep using the same value ((Windows::Security.get_mode}} is called every time the stats .mode is accessed - i.e.
Jira (PUP-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Ethan Brown commented on PUP-6025 Re: Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Merged to stable in https://github.com/puppetlabs/puppet/commit/e0a4e9ede3c2f43464e7cc1e035fad38b581b897 Merged up to master in https://github.com/puppetlabs/puppet/commit/e0b7d916041ece8bff51412d2464793a1f34c185 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-6184) Remove win32-dir code usage from Puppet / Facter
Title: Message Title
Ethan Brown created an issue
Puppet / PUP-6184
Remove win32-dir code usage from Puppet / Facter
Issue Type:
Improvement
Assignee:
Unassigned
Components:
Windows
Created:
2016/04/18 6:35 PM
Priority:
Normal
Reporter:
Ethan Brown
win32-dir uses the Shell APIs to find common directories on Windows. Find an alternative solution that doesn't require CSIDL
On a cursory look, the consumed code can be replaced with something like:
Dir.const_set('COMMON_APPDATA', 'C:\\ProgramData')
Dir.const_set('WINDOWS', 'C:\\Windows')
Dir.const_set('PROFILE', 'C:\\Users\\Administrator')
Jira (PUP-6183) Examine Nano Server Test Failures - File Relevant Tix
Title: Message Title Ethan Brown created an issue Puppet / PUP-6183 Examine Nano Server Test Failures - File Relevant Tix Issue Type: Improvement Assignee: Unassigned Created: 2016/04/18 6:28 PM Priority: Normal Reporter: Ethan Brown With some minor hacking to Ruby based facter, the source for Puppet may be placed on Nano, and the Ruby runtime can execute the specs. Such a run is at https://gist.github.com/Iristyle/057c5560dbe64532fd1770a36e51f805 and shows a host of failures related to: Some problems creating temp files for rspec The use of ADSI monikers Bad tests that use paths like C:\\Windowsexplorer.exe, which doesn't exist on Nano Codepage is 65001 by default on Nano, so some UTF8 tests don't fail like they would normally Use of COM / invalid classes, such as WindowsInstaller.Installer Task scheduler failures given no COM win32-dir gem uses CSIDL ids to find paths, which no longer exists on Nano
Jira (FACT-1397) Replace Facter WMI call layer with MI call layer instead
Title: Message Title Ethan Brown updated an issue Facter / FACT-1397 Replace Facter WMI call layer with MI call layer instead Change By: Ethan Brown Summary: Replace Facter WMI calls call layer with MI calls call layer instead 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-1397) Replace Facter WMI call layer with MI call layer instead
Title: Message Title
Ethan Brown updated an issue
Facter / FACT-1397
Replace Facter WMI call layer with MI call layer instead
Change By:
Ethan Brown
WMI doesn't exist on all platforms - the alternative is to use the MI APIs instead (or worst case, call to PowerShell and use {{Get-CimInstance -Query ""}})This effort currently tracks both Facter 2.x for the ability to run specs against Puppet on Nano, and for 3.x, which is shipped version compatibility.[MI_Session_QueryInstances|https://msdn.microsoft.com/en-us/library/windows/desktop/hh437541(v=vs.85).aspx] This effort should not actually include rewriting existing facts that use WMI, which is covered in FACT-1396. This ticket is to track reworking our extensibility layer to not use WMI.
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-1397) Replace Facter WMI calls with MI calls instead
Title: Message Title
Ethan Brown updated an issue
Facter / FACT-1397
Replace Facter WMI calls with MI calls instead
Change By:
Ethan Brown
WMI doesn't exist on all platforms - the alternative is to use the MI APIs instead (or worst case, call to PowerShell and use {{Get-CimInstance -Query ""}})This effort currently tracks both Facter 2.x for the ability to run specs against Puppet on Nano, and for 3.x, which is shipped version compatibility. [MI_Session_QueryInstances|https://msdn.microsoft.com/en-us/library/windows/desktop/hh437541(v=vs.85).aspx]
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-1397) Replace Facter WMI calls with MI calls instead
Title: Message Title Ethan Brown created an issue Facter / FACT-1397 Replace Facter WMI calls with MI calls instead Issue Type: Improvement Affects Versions: FACT 3.1.5, FACT 2.4.6 Assignee: Unassigned Created: 2016/04/18 5:59 PM Priority: Normal Reporter: Ethan Brown WMI doesn't exist on all platforms - the alternative is to use the MI APIs instead (or worst case, call to PowerShell and use Get-CimInstance -Query "") This effort currently tracks both Facter 2.x for the ability to run specs against Puppet on Nano, and for 3.x, which is shipped version compatibility. Add Comment
Jira (FACT-1396) Replace Facter 2.x queries with WMI where applicable
Title: Message Title Ethan Brown created an issue Facter / FACT-1396 Replace Facter 2.x queries with WMI where applicable Issue Type: Improvement Affects Versions: FACT 2.4.6 Assignee: Unassigned Components: Windows Created: 2016/04/18 5:50 PM Priority: Normal Reporter: Ethan Brown All calls can use native APIs instead of WMI: select Name from Win32_Processor - https://github.com/puppetlabs/facter/blob/2.x/lib/facter/processors/os.rb#L113 select DNSDomain from Win32_NetworkAdapterConfiguration where IPEnabled = True - https://github.com/puppetlabs/facter/blob/2.x/lib/facter/domain.rb#L86 select Architecture, Level, AddressWidth from Win32_Processor - https://github.com/puppetlabs/facter/blob/2.x/lib/facter/domain.rb#L86 select TotalPhysicalMemory
Jira (NPUP-41) Implement the `type` function.
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-41 Implement the `type` function. Issue Type: New Feature Affects Versions: NPUP 0.1.0 Assignee: Unassigned Created: 2016/04/18 5:47 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Implement the type function according to how it functions in the Ruby implementation. Additionally, this should implement the corresponding type inference logic. Add Comment
Jira (FACT-1395) Replace Facter 2.x WMI Operating System kernel query with Windows API
Title: Message Title Ethan Brown commented on FACT-1395 Re: Replace Facter 2.x WMI Operating System kernel query with Windows API It looks like the solution here is RtlGetVersion as mentioned at http://www.codeproject.com/Articles/678606/Part-Overcoming-Windows-s-deprecation-of-GetVe - a PR is up at https://github.com/puppetlabs/facter/pull/1312 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 (NPUP-40) REPL: replace readline dependency with editline (libedit)
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-40 REPL: replace readline dependency with editline (libedit) Change By: Peter Huene Scope Change Category: Found Scope Change Reason: Discovered during a meeting with RE and pulled into Sprint to fix Sprint: Language Triage 2016-04-20 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-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Henrik Lindberg commented on PUP-6178 Re: Look for hiera.yaml in codedir first, then confdir Kylo Ginsberg assuming 4.5.0 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-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6178 Look for hiera.yaml in codedir first, then confdir Change By: Henrik Lindberg Fix Version/s: PUP 4.5.0 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-6153) Spike - PUP-4866 (LFN Paths on Windows) and PUP-6152 Research solution approach
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6153 Spike - PUP-4866 (LFN Paths on Windows) and PUP-6152 Research solution approach Change By: Henrik Lindberg Summary: Spike - PUP-4866 (LFN Paths on Windows) and PUP-6152 Research solution approach 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 (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Kylo Ginsberg commented on HI-490 Re: Move hiera.yaml from codedir to confdir John Duarte or Eric Thompson ping. Just a heads-up that this is the epic for moving hiera.yaml from codedir to confdir. 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-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1385 Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Change By: Hailee Kenney Assignee: Hailee Kenney 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-1364) facter does not serialize integers above 32bits in structured facts in windows
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1364 facter does not serialize integers above 32bits in structured facts in windows Change By: Hailee Kenney Assignee: Hailee Kenney 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-6182) Application declarations don't properly validate component mappings
Title: Message Title
Nick Lewis created an issue
Puppet / PUP-6182
Application declarations don't properly validate component mappings
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/04/18 2:50 PM
Priority:
Normal
Reporter:
Nick Lewis
This ticket captures a set of bugs in component mapping for application declarations.
1) Non-existent components are ignored when compiling environment catalog or agent catalog
site {
my_app { "foo":
nodes => {
Node['node.example.com'] => [ Imaginary[component] ],
Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title William Hopper updated an issue Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: William Hopper Release Notes Summary: Previously, SysVinit services running on RedHat systems which use systemd as the default init system were not being properly queried for `enable` status by the systemd provider. The provider has been updated to use a backwards-compatible `systemctl` command to ensure all services can be properly queried. 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-2744) RHEL7 traditional services should have provider 'redhat' not 'init'
Title: Message Title William Hopper updated an issue Puppet / PUP-2744 RHEL7 traditional services should have provider 'redhat' not 'init' Change By: William Hopper Release Notes Summary: Previously, SysVinit services running on RedHat systems which use systemd as the default init system were mishandled by Puppet. Instead of using the RedHat service provider and `chkconfig` to query services, Puppet fell back to the parent init provider and omitted the `enable` status. This has been fixed by ensuring the RedHat provider is always used for these services instead. 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Glenn Sarti assigned an issue to James Pogran Puppet / PUP-6025 Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Change By: Glenn Sarti Assignee: James Pogran 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-1395) Replace Facter 2.x WMI Operating System kernel query with Windows API
Title: Message Title Ethan Brown created an issue Facter / FACT-1395 Replace Facter 2.x WMI Operating System kernel query with Windows API Issue Type: Improvement Affects Versions: FACT 2.4.6 Assignee: Unassigned Components: Windows Created: 2016/04/18 2:37 PM Fix Versions: FACT 2.4.7 Priority: Normal Reporter: Ethan Brown Currently there are 2 WMI queries used to retrieve the operating system release version for Windows: SELECT version, producttype FROM Win32_OperatingSystem at https://github.com/puppetlabs/facter/blob/2.x/lib/facter/operatingsystem/windows.rb#L9 SELECT version FROM Win32_OperatingSystem at https://github.com/puppetlabs/facter/blob/2.x/lib/facter/kernelrelease.rb#L44
Jira (PUP-4760) Service type should not retrieve ensure status when not needed
Title: Message Title William Hopper assigned an issue to Unassigned Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: William Hopper Assignee: William Hopper 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6091
Lookup should parse dot in key consistently throughout
Change By:
Eric Thompson
Acceptance Criteria:
That the lookup CLI application and lookup function works the same way wrt . : "dotted access" as in hiera.* use of dotted access "drills down" into data e.g. lookup('key,subkey.0')* verbatim lookup is possible by quoting part of key e.g. lookup('key."a.b.c".0')* interpolation is possible using hiera syntax and semantic - thus making it possible to use a hiera data file without change e.g.:* It is possible to lookup a verbatim key using the lookup CLI by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup CLI by not quoting, e.g. ahash.some_key* It is possible to lookup a verbatim key using the lookup API by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup API by not quoting, e.g. ahash.some_key
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-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6176 Behavior of undef in relationships has changed in master since 4.4.x 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-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title
Eric Thompson commented on PUP-6176
Re: Behavior of undef in relationships has changed in master since 4.4.x
validated on rhel7 at master puppet-agent SHA: 043c6c30b29539bd89e1ab9dc2cc9843ffa13503
[root@eeaxl0yyb692hs3 ~]# puppet apply -e 'notify {example: message => yay, notify => undef}'
Notice: Compiled catalog for eeaxl0yyb692hs3.delivery.puppetlabs.net in environment production in 0.04 seconds
Notice: yay
Notice: /Stage[main]/Main/Notify[example]/message: defined 'message' as 'yay'
Notice: Applied catalog in 0.02 seconds
[root@eeaxl0yyb692hs3 ~]# puppet apply -e 'notify {example: message => undef}'
Notice: Compiled catalog for eeaxl0yyb692hs3.delivery.puppetlabs.net in environment production in 0.05 seconds
Notice: example
Notice: /Stage[main]/Main/Notify[example]/message: defined 'message' as 'example'
Jira (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6176 Behavior of undef in relationships has changed in master since 4.4.x Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title John Duarte updated an issue Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: John Duarte QA Risk Assessment: 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title
John Duarte updated an issue
Puppet / PUP-5353
Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Change By:
John Duarte
Release Notes Summary:
Previously, the puppet service resource attempted to enable or disable static services on systemd. This resulted in erroneous change notifications.This fix corrects the problem. Changing the {{enable}} parameter for a static service no longer triggers a change and a {{debug}} message is logged.
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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title John Duarte updated an issue Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: John Duarte 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title John Duarte updated an issue Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: John Duarte 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title
John Duarte commented on PUP-5353
Re: Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Validated using puppet-agent at sha 043c6c3 containing puppet at sha 611d0245 this fails validation.
Steps to reproduce
Enable test
Apply the following manifest
package { 'dbus': ensure => installed, }
$dbus_service = $::operatingsystemmajrelease ? {
'5' => 'messagebus',
'6' => 'messagebus',
'7' => 'dbus',
}
service { 'messagebus':
ensure => running,
name => $dbus_service,
Jira (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6176 Behavior of undef in relationships has changed in master since 4.4.x 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6091
Lookup should parse dot in key consistently throughout
Change By:
Eric Thompson
Acceptance Criteria:
That the lookup CLI application and lookup function works the same way wrt. "dotted access" as in hiera.* use of dotted access "drills down" into data e.g. lookup('key,subkey.0')* verbatim lookup is possible by quoting part of key e.g. lookup('key."a.b.c".0')* interpolation is possible using hiera syntax and semantic - thus making it possible to use a hiera data file without change e.g.:* It is possible to lookup a verbatim key using the lookup CLI by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup CLI by not quoting, e.g. ahash.some_key* It is possible to lookup a verbatim key using the lookup API by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup API by not quoting, e.g. ahash.some_key
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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6091
Lookup should parse dot in key consistently throughout
Change By:
Eric Thompson
Lookup and Hiera treats dotted keys differently. While hiera will recognize them everywhere (except when they are quoted), the Puppet lookup will only recognized them within interpolations that in turn, are only recognized by the Hiera Data Provider. For the sake of consistency, lookup should instead do what Hiera does.This means that:* the command line {{lookup}} should be made consistent with hiera and facter tools as they take unquoted input as sub-lookup, and handles quoted input as verbatim.* interpolation expressions should be recognized by all data providers, not just the Hiera data provider* dotted keys that are not quoted, should be parsed at all times, not just in interpolations ACCEPTANCE CRITERIA* It is possible to lookup a verbatim key using the lookup CLI by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup CLI by not quoting, e.g. ahash.some_key* It is possible to lookup a verbatim key using the lookup API by quoting it . e.g. "'foo.bar'"* It is possible to perform a sub-lookup using the lookup API by not quoting, e.g. ahash.some_key
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
Jira (PDB-2622) PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2622 PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service Change By: Wyatt Alt Sprint: Hopper 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-2622) PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2622
PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service
Change By:
Nick Walker
h1. The ProblemWhile doing some performance testing I noticed that my disk IO was maxed out on a vacuum command. For a while I thought it was autovacuum but then I investigated and found that it was an explicit {{vacuum ( analyze, verbose)}} that puppetdb was running. My database is roughly 180GB at this time and I think the analyze was probably picking up a lot of pages off disk and putting them in the cache but then they weren't needed again so they were being thrown out by more often used pages. If it was doing this on the reports table that would probably take a long time to read 120GB of data off disk. I think it's particularly problematic that this runs at startup of the service because if you run into some issue and you tune something and restart the service now you've introduced a query that itself may cause you performance problems. Also, if you restart the whole box that is running puppetdb and postgresql then your postgresql server will be reading pages from disk for agents running puppet and also for this vacuum process that will be competing for resources. Long story short, I couldn't restart pe-puppetdb during my tests without killing the vacuum analyze or it'd kill my performance. h1. Suggested SolutionDon't run vacuum analyze on startup. If we need to ensure stats are updated we should trust autovacuum to do that. If we're worried about tables with less than 50 rows that wouldn't be hit by default autovacuum settings then we should find a way to discover those tables and only vacuum them. We could also consider tuning autovacuum settings on these small tables to make sure that a new row would trigger an autovacuum on the small tables. I think that'd be a combo of autovacuum_vacuum_threshold = 1 autovacuum_analyze_threshold = 1 autovacuum_vacuum_scale_factor = .01 autovacuum_analyze_scale_factor = .01
Add Comment
Jira (PUP-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: John Duarte Assignee: qa John Duarte 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title Michael Smith commented on FACT-1392 Re: Facter fails when locale files are missing for specified locale on CentOS 7 I have no idea either. 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-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf Change By: Nathanael Cole Summary: in the PE Console, the default basemodulepath doesn't inherit custom codedir in from puppet.conf 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-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir from puppet.conf Change By: Nathanael Cole h3. IssueIn 2015.3.3 (tested), if you specify a custom codedir in puppet.conf, without also specifying a specific basemodulepath, the basemodulepath within the Console itself does not update according to the default behaviour as described here: https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepathClasses added to the assumed basemodulepath within that custom codedir will be available for use directly within other code, but the PE Console can not see or apply them.h3. Expected ResultsBased on the wording of the basemodulepath configuration (https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath), if you specify a custom "/path/to/code/" codedir, then the basemodulepath would default to "/path/to/code/modules/"Assumption of default based on documentation: "Default: $codedir/modules:/opt/puppetlabs/puppet/modules"h3. ReplicationTo replicate# spin up new 2015.3.3 directory# mkdir -p /path/to/code/modules# specify /path/to/code/ as codedir in puppet.conf# run puppet config print basemodulepath, notice expected /path/to/code/modules# create test module in /path/to/code/modules# refresh console classes listFAIL: test module is not available within the Console.h3. Work-AroundIf you specify /path/to/code as your codedir, you can also specify /path/to/code/modules as your basemodulepath, and the modules in the path will now be available in the console.To replicate:# spin up new 2015.3.3 directory# mkdir -p /path/to/code/modules# specify /path/to/code/ as codedir in puppet.conf# specify /path/to/code/modules as basemodulepath in puppet.conf# run puppet config print basemodulepath, notice expected /path/to/code/modules# create test module in /path/to/code/modules# refresh console classes listSUCCESS: Test class is now available to be added within the Console. Add Comment
Jira (PUP-6181) in the PE Console, the default basemodulepath doesn't inherit custom codedir in puppet.conf
Title: Message Title Nathanael Cole created an issue Puppet / PUP-6181 in the PE Console, the default basemodulepath doesn't inherit custom codedir in puppet.conf Issue Type: Improvement Affects Versions: PUP 4.3.2 Assignee: Unassigned Created: 2016/04/18 12:39 PM Priority: Major Reporter: Nathanael Cole Issue In 2015.3.3 (tested), if you specify a custom codedir in puppet.conf, without also specifying a specific basemodulepath, the basemodulepath does not update according to the default behaviour as described here: https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath Classes added to the assumed basemodulepath within that custom codedir will be available for use directly within other code, but the PE Console can not see or apply them. Expected Results Based on the wording of the basemodulepath configuration (https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath), if you specify a custom "/path/to/code/" codedir, then the basemodulepath would default to "/path/to/code/modules/" Assumption of default based on documentation: "Default: $codedir/modules:/opt/puppetlabs/puppet/modules" Replication To replicate spin up new 2015.3.3 directory
Jira (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title John Duarte commented on FACT-1392 Re: Facter fails when locale files are missing for specified locale on CentOS 7 Need instructions on how to reproduce in openstack in order to understand why the existing acceptance test failed to capture this. 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-4760) Service type should not retrieve ensure status when not needed
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: William Hopper Assignee: William Hopper 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1392 Facter fails when locale files are missing for specified locale on CentOS 7 Change By: John Duarte Assignee: qa John Duarte 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title John Duarte updated an issue Facter / FACT-1392 Facter fails when locale files are missing for specified locale on CentOS 7 Change By: John Duarte 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 (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title John Duarte updated an issue Facter / FACT-1392 Facter fails when locale files are missing for specified locale on CentOS 7 Change By: John Duarte QA Risk Assessment: High 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6025 Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Change By: Glenn Sarti Assignee: James Pogran 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-6180) Add acceptance test for Puppet CA face
Title: Message Title Michael Smith created an issue Puppet / PUP-6180 Add acceptance test for Puppet CA face Issue Type: Bug Assignee: Unassigned Created: 2016/04/18 11:09 AM Priority: Normal Reporter: Michael Smith It was broken in Puppet 4 and no one new. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2527 support latest_report? as a query field on event-counts/aggregate-event-counts Change By: Wyatt Alt Assignee: Wyatt Alt 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-6179) Puppet CA face broken
Title: Message Title Michael Smith created an issue Puppet / PUP-6179 Puppet CA face broken Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2016/04/18 11:06 AM Fix Versions: PUP 4.4.2 Priority: Normal Reporter: Michael Smith The Puppet CA face appears to have been broken the entire lifetime of Puppet 4. Add Comment
Jira (PUP-6179) Puppet CA face broken
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6179 Puppet CA face broken Change By: Michael Smith Assignee: Michael Smith 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-6153) Spike - PUP-4866 and PUP-6152 Research solution approach
Title: Message Title Craig Gomes assigned an issue to Unassigned Puppet / PUP-6153 Spike - PUP-4866 and PUP-6152 Research solution approach Change By: Craig Gomes Assignee: 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 (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2527 support latest_report? as a query field on event-counts/aggregate-event-counts Change By: Wyatt Alt Story Points: 3 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-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Wyatt Alt Sprint: Hopper 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-2334) Convert remaining compojure usage to comidi
Title: Message Title Wyatt Alt commented on PDB-2334 Re: Convert remaining compojure usage to comidi This is quasi-blocked on a bug in comidi, which is causing it to take longer than expected. I've got a higher priority ticket to take care of right now, but I'll come back to this one and take another crack at a workaround after that's done. 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Priscilla Piedra good to hear it! I've still got no idea how you might have ended up in this situation to begin with though, so let us know if the issue comes back. 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-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Wyatt Alt commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' Robert Heinzmann this is usually caused by a misconfigured or missing routes.yaml. Can you please give the output of this? cat $(puppet config print confdir)/routes.yaml 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title John Duarte updated an issue Puppet / PUP-5929 Allow type alias to define a mapping between puppet names and runtime types Change By: John Duarte QA Risk Assessment: 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title John Duarte updated an issue Puppet / PUP-5929 Allow type alias to define a mapping between puppet names and runtime types Change By: John Duarte 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-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5929 Allow type alias to define a mapping between puppet names and runtime types Change By: John Duarte Assignee: qa John Duarte 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Craig Gomes assigned an issue to James Pogran Puppet / PUP-6025 Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Change By: Craig Gomes Assignee: James Pogran 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 (HI-510) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Kylo Ginsberg created an issue Hiera / HI-510 Look for hiera.yaml in codedir first, then confdir Issue Type: Improvement Assignee: Unassigned Created: 2016/04/18 8:50 AM Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PUP-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6178 Look for hiera.yaml in codedir first, then confdir Change By: Kylo Ginsberg Sprint: Language 2016-05-04 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-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-6178 Look for hiera.yaml in codedir first, then confdir Issue Type: Improvement Assignee: Unassigned Created: 2016/04/18 8:49 AM Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt I have applied this config on DB and I haven't seen the error... seems like it worked! Thanks for your 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-6091 Lookup should parse dot in key consistently throughout Change By: Kylo Ginsberg Status: Ready for CI Test 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 (PUP-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-5353 Statically-enabled systemd service is treated like SysV init scripts - enabled each run. Change By: Kylo Ginsberg Status: Ready for CI Test 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 (PDB-2617) Fix incorrect selection of stale-nodes
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2617 Fix incorrect selection of stale-nodes 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-1389) Facter.rb regression when called from MCO
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Facter / FACT-1389 Facter.rb regression when called from MCO 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 (NPUP-36) Implement the `step` function.
Title: Message Title Sean Griffin assigned an issue to Unassigned Native Puppet / NPUP-36 Implement the `step` function. 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 (NPUP-36) Implement the `step` function.
Title: Message Title Sean Griffin updated an issue Native Puppet / NPUP-36 Implement the `step` function. Change By: Sean Griffin 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-6176) Behavior of undef in relationships has changed in master since 4.4.x
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6176 Behavior of undef in relationships has changed in master since 4.4.x Change By: Sean Griffin Status: Ready for CI Test 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 (PUP-5929) Allow type alias to define a mapping between puppet names and runtime types
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5929 Allow type alias to define a mapping between puppet names and runtime types Change By: Sean Griffin Status: Ready for CI Test 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 (PDB-2629) (maint) Remove Debian 6 from pipelines
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2629 (maint) Remove Debian 6 from pipelines Issue Type: Bug Assignee: Unassigned Created: 2016/04/18 7:17 AM Priority: Normal Reporter: gepetto-bot Debian 6 has reached EOL and should be removed from all build/test pipelines Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6136) newparam(:downgrade) for package type
Title: Message Title Matt Schuchard commented on PUP-6136 Re: newparam(:downgrade) for package type Yes, that would be an example of a typical use-case and the desired goal. As for that discussion, it looks like Henrik rejected an alternate implementation that I myself also rejected for the same reasons he did. The current package behavior on ensure is to pull the version out via regex and then append it onto the provider install command. Reworking that would be even rougher than the route I am traversing, especially because I don't know what providers have that kind of intrinsic functionality (if any). Something I found interesting from viewing the spec tests during my implementation is that Puppet can pull in an array of versions for what is currently installed due to different archs. This really throws a wrench into the situation for should <=> version. 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-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: { { code:bash} ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown {code } } This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{code :bash }# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown{code}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: {code} Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown' {code} Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{code:bash} # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown{code}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown }}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{# ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown}}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.:{{ # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown}}This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title David Gardner updated an issue Facter / FACT-1394 Warning printed when 'ip route show' output contains "linkdown" Change By: David Gardner When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: # ip ro sho default via 192.168.1.1 dev eth2 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdownThis causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :) 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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title
David Gardner updated an issue
Facter / FACT-1394
Warning printed when 'ip route show' output contains "linkdown"
Change By:
David Gardner
When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: {{ # ip ro shodefault via 192.168.1.1 dev eth2192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown }} This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.0.0/24 dev eth0 proto kernel scope link src192.168.0.1 linkdown' Warning: Facter: Could not process routing table entry: Expected a destination followedby key/value pairs, got '192.168.2.0/24 dev eth1 proto kernel scope link src192.168.2.1 linkdown'Facter should probably cope with such eventualities, possibly by just ignoring lines with "linkdown" in them. Happy to provide a simple patch to do this if that would be the desired behaviour :)
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
Jira (FACT-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title David Gardner created an issue Facter / FACT-1394 Warning printed when 'ip route show' output contains "linkdown" Issue Type: Bug Affects Versions: FACT 3.1.5 Assignee: Unassigned Created: 2016/04/18 2:35 AM Environment: Debian Sid with PC1 install of Puppet 4.x and puppet-agent latest versions from jessie apt repo (includes facter 3.1.5) Priority: Normal Reporter: David Gardner When there are network links which are configured but down "ip route show" appends "linkdown" to the output of those routes. e.g.: ip ro sho default via 192.168.1.1 dev eth2 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.133 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.1 linkdown This causes facter to print a warning on every puppet agent run, or whenever facter is run separately: Warning: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs, got '192.168.0.0/24 dev
Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title
Robert Heinzmann created an issue
PuppetDB / PDB-2628
PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Issue Type:
Bug
Affects Versions:
PDB 2.3.8
Assignee:
Unassigned
Components:
Platform
Created:
2016/04/18 1:27 AM
Environment:
[root@puppet]# rpm -qf /usr/share/ruby/vendor_ruby/puppet/indirector/facts/puppetdb.rb puppetdb-terminus-2.3.8-1.el7.noarch
[root@puppet]# rpm -qa | grep puppet puppet-3.8.6-1.el7.noarch puppetserver-1.1.3-1.el7.noarch puppetdb-2.3.8-1.el7.noarch puppetdb-terminus-2.3.8-1.el7.noarch
os => {"name"=>"CentOS", "family"=>"RedHat", "release"=> {"major"=>"7", "minor"=>"2", "full"=>"7.2.1511"}
}
Priority:
Normal
Reporter:
Robert Heinzmann
If trusted_node_data = true in [master], and agent provides /etc/puppet/csr_attributes.yaml puppet run's fail
