Jira (FACT-2134) Facter should distinguish between CentOS 8 and CentOS 8 Stream

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  FACT-2134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter should distinguish between CentOS 8 and CentOS 8 Stream   
 

  
 
 
 
 

 
 Sorry for cross-posting that from the github issue (https://github.com/puppetlabs/facter/pull/2291#issuecomment-790039719), BUT this is (from my point of view) in the way it got merged now heavily breaking tons of puppet modules out there. I would consider to release that change only with a major facter release (and thus major puppet version).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336204.1574351826000.156727.1614804420032%40Atlassian.JIRA.

Jira (FACT-2928) Error: Facter: statvfs() function failed: No such file or directory

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2928  
 
 
  Error: Facter: statvfs() function failed: No such file or directory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/01/28 1:44 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 
 
puppet --version 7.3.0 
 on CentOS 7 with up2date system. When running puppet or gathering facts, I had the following error:  
 
 
 
 
 # puppet facts show  
 
 
 [...]  
 
 
 Debug: Facter: Executing command: which blkid  
 
 
 Error: Facter: statvfs() function failed: No such file or directory  
 
 
 Debug: Facter: Executing command: /bin/cat /proc/uptime  
 
 
 [...]
  
 

Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  PUP-10853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact   
 

  
 
 
 
 

 
 This also shows up when using `puppet facts show`:  
 
 
 
 
 # puppet facts show --debug --trace   
 
 
 [ ...]  
 
 
 Debug: Facter: List of resolvable facts: [#]  
 
 
 Debug: Facter: Resolving facts sequentially  
 
 
 Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/init.rb:24:in `block in '  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/classgen.rb:132:in `class_eval'  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/classgen.rb:132:in `genthing'  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/classgen.rb:33:in `genclass'  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1847:in `provide'  
 
 
 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/init.rb:3:in `'  
 
 
 

Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  FACT-2872  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regressions: secondary interfaces are not anymore reported   
 

  
 
 
 
 

 
 Yes that works to get it over bindings, although a bit clumsy: https://code.immerda.ch/immerda/ibox/puppet-modules/-/blob/76e4586bbd6184af6d6df2c57058a709843ff8e0/ib_unbound/manifests/init.pp#L13-19  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379058.1605915439000.90526.1606993020034%40Atlassian.JIRA.

Jira (FACT-2870) Can't run puppet on machines with VLANs as facts are failing

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  FACT-2870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't run puppet on machines with VLANs as facts are failing   
 

  
 
 
 
 

 
 I can confirm that with puppet-agent-7.0.0.103.gf0655d02-1.el7.x86_64 I was able to run puppet again.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379053.1605909534000.90494.1606986001862%40Atlassian.JIRA.

Jira (PUP-10790) user provider with uid/gid as Integer raises warning

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  PUP-10790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: user provider with uid/gid as Integer raises warning   
 

  
 
 
 
 

 
 Same thing happens on exec, when user is a uid:    
 
 
 
 
  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/exec.rb:599: warning: deprecated Object#=~ is called on Integer; it always returns nil
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379059.1605916728000.84681.1605917100025%40Atlassian.JIRA.

Jira (PUP-10790) user provider with uid/gid as Integer raises warning

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10790  
 
 
  user provider with uid/gid as Integer raises warning   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 7.0.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2020/11/20 3:58 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
    
 
 
 
 
  # cat foo.pp   
 
 
 user { 'user1':  
 
 
   ensure => 'present',  
 
 
   gid=> 10008,  
 
 
   groups => ['bla'],  
 
 
  

Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2871  
 
 
  Regression: interfaces without an ipaddress assigned are not anymore reported   
 

  
 
 
 
 

 
Change By: 
 Peter Meier  
 
 
Priority: 
 Normal Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379055.160591045.84655.1605915060036%40Atlassian.JIRA.

Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  FACT-2871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression: interfaces without an ipaddress assigned are not anymore reported   
 

  
 
 
 
 

 
  
 
 
 
 
 irb$ File.readlines('/proc/net/dev').reject{|l| l=~/\|/ }.map{|l| l.split(':',2).first.strip }.sort.join(',')  
 
 
 => "br0,br1,eno1,enp3s0f1,lo,virbr0,virbr0-nic,vnet0,vnet1,vnet10,vnet11,vnet12,vnet13,vnet14,vnet15,vnet17,vnet2,vnet3,vnet4,vnet5,vnet6,vnet7,vnet8,vnet9"
  
 
 
 
  vs.  
 
 
 
 
  # puppet facts show interfaces  
 
 
 {  
 
 
   "interfaces": "br1,lo,virbr0"  
 
 
 }
  
 
 
 
     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2871  
 
 
  Regression: interfaces without an ipaddress assigned are not anymore reported   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Facter 4  
 
 
Created: 
 2020/11/20 2:14 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 In puppet-agent 7.0.0 interfaces without an ipaddress are not anymore reported in $facts['interfaces'] and also in no other fact.   Facter should report all interfaces somewhere.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian 

Jira (FACT-2870) Can't run puppet on machines with VLANs as facts are failing

[Peter Meier (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2870  
 
 
  Can't run puppet on machines with VLANs as facts are failing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Facter 4  
 
 
Created: 
 2020/11/20 1:58 PM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 Puppet 7.0.0 can't run on machines with VLANs configured, as facter is failing with:    
 
 
 
 
 # puppet agent -t --noop  
 
 
 Info: Using configured environment 'production'  
 
 
 Info: Retrieving pluginfacts  
 
 
 Info: Retrieving plugin  
 
 
 Info: Loading facts  
 
 
 Error: Could not retrieve local facts: undefined method `bury' for ":::::":String  
  

Jira (PDB-4488) PuppetDB module uses deprecated http_instance method

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  PDB-4488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB module uses deprecated http_instance method   
 

  
 
 
 
 

 
 This generates noise if you run puppet through cron - would be nice to have a fix soon! Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321972.1566497006000.72847.1566852540210%40Atlassian.JIRA.

Jira (PUP-9194) REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9194  
 
 
  REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.0.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2018/10/03 1:24 AM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 Since 6.0.1 there is a pretty severe regression which makes unless & onlyif of the exec resource not respecting the specified cwd. Here is the (shortened output of a run in 6.0.0:    
 
 
 
 
 $ puppet apply --debug <  
 
 
 exec{'/usr/bin/pwd':  
 
 
   _onlyif_=> '/usr/bin/pwd',  
 
 
   cwd   => '/tmp',  
 
 
   logoutput 

Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  FACT-1475  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: facter returns wrong ipv6 information when IPV6 stack is disabled
 

  
 
 
 
 

 
 Yes it resolves, still to an ipv6 address. So somehow you still have an ip6 address on your interfaces, which means that you do not have properly disabled ipv6. Are you unloading the module? Anyway it seems that meanwhile the ip util got fixed. At least CentOS 7:  
 
 
 
 
 #  cat /proc/cmdline   
 
 
 BOOT_IMAGE=/vmlinuz-3.10.0-693.21.1.el7.x86_64 root=/dev/mapper/vg--meh-root ro crashkernel=auto rd.lvm.lv=vg-meh/root rd.lvm.lv=vg-meh/swap ipv6.disable=1 console=ttyS0,115200 panic=30 LANG=en_US.UTF-8  
 
 
 # ip -6 addr   
 
 
 # ip -6 route show  
 
 
 # facter -p --show-legacy | grep ipaddress  
 
 
 default_ipaddress => 192.168.1.22  
 
 
 ipaddress => 192.168.1.22  
 
 
 ipaddress_eth0 => 192.168.1.22  
 
 
 ipaddress_lo => 127.0.0.1
  
 
 
 
    Compare to what I reported in FACT-1739 So facter is not anymore reporting an ipaddress6 fact. Still this could have been avoided if facter would match values against an excpected pattern. Which in this case here would be pretty trivial, as the format of an ipaddress is (luckily) the same on any system.  
 

  
 
 
 
   

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8513  
 
 
  Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
Change By: 
 Peter Meier  
 
 
Assignee: 
 Peter Meier  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier assigned an issue to Henrik Lindberg  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8513  
 
 
  Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
Change By: 
 Peter Meier  
 
 
Assignee: 
 Peter Meier Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier commented on  PUP-8513  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
 I can't say whether it ever worked, because it was new code I added that failed. But I have similar code patterns that are working for a long time and still work. But it was likely the first time I added such a piece of code with a resource default _expression_ setting the particular param in site.pp. 

The override of the resource occurs outside the scope of the containing class of the resource (and is also not within a scope that inherits from the declaring class.
 I don't understand why you are saying that the override of the resource occurs outside the scope of the containing class. There is only one class and except for the resource default both param declaration are within the same class.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8513  
 
 
  Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Language  
 
 
Created: 
 2018/03/05 11:43 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 The following manifests fails with the error:  
 
 
 
 
 Error: Parameter 'ignore' is already set on File[/tmp/puppet-test] by # at /tmp/foo.pp:3; cannot redefine at /tmp/foo.pp:13 on node bla  
 
 
 
  Manifest:  
 
 
 
 
 File {  
 
 
   ignore => '*.bak'  
 

Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm

[Peter Meier (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3832  
 
 
  puppetdb module config.ini mgmt should be in sync with rpm   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 5.1.4  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Module  
 
 
Created: 
 2018/02/06 1:42 AM  
 
 
Environment: 
 After an upgrade to (e.g.)   
 
 
 
 
 Feb 06 04:51:53 Updated: puppetdb.noarch 5.1.4-1.el7
  
 
 
 
  The puppetdb module makes changes to files managed by the RPM.  
 
 
 
 
 Feb  6 08:08:46 master puppet-agent[5832]: (/Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/owner) owner changed 'root' to 'puppetdb'  
 
 
 Feb  6 08:08:46 master puppet-agent[5832]: (/Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/group) group changed 'root' to 'puppetdb'  
 
 
 Feb  6 08:08:46 master puppet-agent[5832]: (/Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/mode) mode changed '0644' to '0600'
  
 
 
 

Jira (PUP-6589) Resource Type sshkey doesn't allow the declaration of multiple SSH host keys for one host

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  PUP-6589 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Resource Type sshkey doesn't allow the declaration of multiple SSH host keys for one host  
 
 
 
 
 
 
 
 
 
 
I think the proper thing would be to make the type also a namevar and hence the uniqueness would come from `name` and `type`. I tried to adjust the type with that regard, but I'm failing as I need to convert the type property to a param so it can be a namevar. See https://github.com/duritong/puppet/commit/87cc784392d539c3a522604bed009b221f88ab57 for my WIP, but I lack some provider/type developments detals here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3368) nagios_contact no longer is able to parse utf-8 from nagios config files

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  PUP-3368 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: nagios_contact no longer is able to parse utf-8 from nagios config files  
 
 
 
 
 
 
 
 
 
 
Here you go with a fix a fix for that: https://github.com/puppetlabs/puppet/pull/6169 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3368) nagios_contact no longer is able to parse utf-8 from nagios config files

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  PUP-3368 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: nagios_contact no longer is able to parse utf-8 from nagios config files  
 
 
 
 
 
 
 
 
 
 
This is still a problem and it's likely a problem with the combincation of RHEL 6. 
It's also a problem for any nagios_service etc. 
Use this Vagrantfile to reproduce the issue on a system from the original report and see how you can reproduce it: 
 
 
 
 
 
 
Vagrant.configure("2") do |config| 
 
 
 
 
  config.vm.box = "centos/6" 
 
 
 
 
  config.vm.provision "shell", inline: <

Jira (FACT-775) Facter changes name of VLAN interface (name with dot)

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-775 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter changes name of VLAN interface (name with dot)  
 
 
 
 
 
 
 
 
 
 
I can definitely confirm this bug, also in the latest release: 
Here is a node with multiple vlans on an interface and it is broken. This used to be fine in facter-2.4.6-1.el7.x86_64. 
 
 
 
 
 
 
# ip a show dev enp1s0.10 
 
 
 
 
6: enp1s0.10@enp1s0:  mtu 1500 qdisc noqueue state UP qlen 1000 
 
 
 
 
link/ether 00:0d:de:ad:be:ef brd ff:ff:ff:ff:ff:ff 
 
 
 
 
inet 10.12.34.1/24 brd 10.12.34.255 scope global enp1s0.10 
 
 
 
 
   valid_lft forever preferred_lft forever 
 
 
 
 
facter -p --show-legacy | grep -E '(enp1s0.10|operatingsystem|facterversion)' 
 
 
 
 
facterversion => 3.8.0 
 
 
 
 
interfaces => enp1s0,enp1s0.10,enp1s0.958,enp2s0,enp3s0,lo 
 
 
 
 
ipaddress6_enp1s0.10 => 10.12.34.1 
 
 
 
 
  

Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1475 
 
 
 
  facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Meier 
 
 
 

Labels:
 
 help_wanted  regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-1475 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 
 
We could at least validate the info we get from `ip` like whether the supposed ipv6 address contains a : (colon) otherwise drop it. 
This is what people are left to do now if they have hosts with ipv6 disabled, but are slowly enabling it and hence try to figure out, if the host has an ipv6 address. 
IMHO this is a pretty severe bug that is opened way too long, as it is reporting false facts, that people can't rely on, which makes the purpose of facts completely meaningless. Especially this wasn't the case in Facter versions < 3, so people have code that is with the newer facter version completely unreliable. So at least it is also a regression.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1475) facter returns wrong ipv6 information when IPV6 stack is disabled

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1475 
 
 
 
  facter returns wrong ipv6 information when IPV6 stack is disabled   
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Meier 
 
 
 

Affects Version/s:
 
 FACT 3.8.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1739) ipaddress6 returns ipv4 address

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1739 
 
 
 
  ipaddress6 returns ipv4 address  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.8.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/24 9:11 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Meier 
 
 
 
 
 
 
 
 
 
 
A host with ipv6 disabled: 
 
 
 
 
 
 
$ ip addr show eth0 
 
 
 
 
2: eth0:  mtu 1500 qdisc pfifo_fast state UP qlen 1000 
 
 
 
 
link/ether 52:54:00:48:4e:21 brd ff:ff:ff:ff:ff:ff 
 
 
 
 
 

Jira (PUP-2627) Collecting defined types in masterless configuration

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  PUP-2627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Collecting defined types in masterless configuration  
 
 
 
 
 
 
 
 
 
 
I can confirm that this bug still exists with 3.8.4 and it seems that it only exists with defined types. Removing the resource RAL from routes.yaml fixes the problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1289) misdetecting virtualbox guest as kvm

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1289 
 
 
 
  misdetecting virtualbox guest as kvm  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/12/21 8:51 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Meier 
 
 
 
 
 
 
 
 
 
 
virt-what reports multiple facts: 
 
 
 
 
 
 
# virt-what 
 
 
 
 
virtualbox 
 
 
 
 
kvm
 
 
 
 
 
 
 
Meaning that this is virtualbox guest 

Jira (PUP-3434) Puppet cert sign by fingerprint

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  PUP-3434 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet cert sign by fingerprint  
 
 
 
 
 
 
 
 
 
 
This would also allow a much more sophisticated workflow: Users could just select the FP shown to them, paste it to the master and directly to the sign command. Without having to tediously compare the fingerprint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-697) If NetworkManager is installed but not used facter throws a warning.

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-697 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: If NetworkManager is installed but not used facter throws a warning.  
 
 
 
 
 
 
 
 
 
 
Problem is that NetworkManager is printing to STDERR: 
 
 
 
 
 
 
# nmcli -t -f STATE g 2 /dev/null 
 
 
 
 
# nmcli -t -f STATE g  
 
 
 
 
Error: NetworkManager is not running. 
 
 
 
 
# nmcli -t -f STATE nm 
 
 
 
 
Error: Object 'nm' is unknown, try 'nmcli help'. 
 
 
 
 
# facter os 
 
 
 
 
{name=CentOS, family=RedHat, release={major=7, minor=1, full=7.1.1503}} 
 
 
 
 
# nmcli --version 
 
 
 
 
nmcli tool, version 1.0.0-14.git20150121.b4ea599c.el7
 
 
 
 
 
 
 
PR that addresses this: https://github.com/puppetlabs/facter/pull/919 
 
 
 

Jira (FACT-697) If NetworkManager is installed but not used facter throws a warning.

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-697 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: If NetworkManager is installed but not used facter throws a warning.  
 
 
 
 
 
 
 
 
 
 
I can confirm this appears on CentOS 7.1 using facter 2.4.3 
 
 
 
 
 
 
$ facter -v 
 
 
 
 
2.4.3 
 
 
 
 
$ facter os 
 
 
 
 
{name=CentOS, family=RedHat, release={major=7, minor=1, full=7.1.1503}} 
 
 
 
 
$ facter dhcp_servers 
 
 
 
 
Error: NetworkManager is not running. 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

Jira (FACT-893) CentOS 7.1.1503 breaks /etc/redhat-release

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
PR: https://github.com/puppetlabs/facter/pull/902 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-893) CentOS 7.1.1503 breaks /etc/redhat-release

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-893 
 
 
 
  CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Meier 
 
 
 

Affects Version/s:
 
 FACT2.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-893) CentOS 7.1.1503 breaks /etc/redhat-release

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
I decided to add this task only to cfacter (given that's the future of facter) CFACT-271 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-893) CentOS 7.1.1503 breaks /etc/redhat-release

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier commented on  FACT-893 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: CentOS 7.1.1503 breaks /etc/redhat-release  
 
 
 
 
 
 
 
 
 
 
We should also make sure, that we might revisite the whole thing and prefering /etc/os-release for CentOS, RedHat, ...  7. /etc/os-release seems to be present since 7.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-4042) Exec runs with wrong user if user matches a hex-like string

[Peter Meier (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Meier created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4042 
 
 
 
  Exec runs with wrong user if user matches a hex-like string  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/02/25 2:13 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Meier 
 
 
 
 
 
 
 
 
 
 
Create a user '0x01' and try to run an exec with this user and you end up with the following: 
 
 
 
 
 
 
# puppet apply --parser=future -e 'exec{/usr/bin/whoami: user = 0x01, group = 0x01, logoutput = true }'  
 
 
 
 
Notice: Compiled catalog for foo in environment production in 1.17 seconds 
 
 
 

Jira (PUP-2610) Rack masters lose track of environment loaders

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: Rack masters lose track of environment loaders 










This is quite a severe issue, because the catalog is then being compiled with a wrong environment, which means that stored configs being present from previous runs are being purged from the database, resulting in possible config changes across your whole infrastructure. 












   

 Add Comment

























 Puppet /  PUP-2610



  Rack masters lose track of environment loaders 







 When a puppet master is running under rack the first few seconds of running will cause it to use the wrong modules if the {{[main]}} section has a different {{modulepath}} (or {{environmentpath}}) from the {{[master]}} section.   Reproduction:   Given a rack master with the following puppet.conf:  {code}  [main]  modulepath = /tmp/main-modules  [master]...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 

Jira (PUP-2618) Unable to define multiple module paths when using directory environments

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue


















 Puppet /  PUP-2618



  Unable to define multiple module paths when using directory environments 










Issue Type:

  New Feature




Affects Versions:


 3.6.0




Assignee:


 Unassigned




Created:


 19/May/14 3:10 PM




Priority:

  Normal




Reporter:

 Peter Meier










I have multiple modulepaths per environment. That's a way to structure your modules more by topic.
Example:
env/modules/topic1/module1 env/modules/topic1/module2 env/modules/topic2/module3
With the following config
modulepath = $vardir/environments/$environment/modules/topic1:$vardir/environments/$environment/modules/topic2
To my understanding this is not possible with directory environments and which makes them not that usable for my environments.
I have used the above pattern in several installations for example to serve group of modules from different repositories and so on.












   

 Add Comment
   

Jira (PUP-2584) Spurious warnings when using multiple file sources

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: Spurious warnings when using multiple file sources 










Nope, everything is clear. I simply haven't seen it on my mobile device. Poor excuse... 












   

 Add Comment

























 Puppet /  PUP-2584



  Spurious warnings when using multiple file sources 







 When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names):  {code}  Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=managesource_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2611) sourceselect/file will print warnigs after update to 3.6

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: sourceselect/file will print warnigs after update to 3.6 










That's this issue, not?












   

 Add Comment

























 Puppet /  PUP-2611



  sourceselect/file will print warnigs after update to 3.6 







 After update to 3.6 sourceselect will try all options and print an warning about the 2 that fails.  {code}  file{/etc/logrotate.conf:  require =Package[$PaketLR],  owner =root,  group =root,  mode =644,  ensure =file,  so...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2584) Spurious warnings when using multiple file sources

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier updated an issue


















 Puppet /  PUP-2584



  Spurious warnings when using multiple file sources 










Change By:

 Peter Meier




Fix Version/s:

 3.6.1












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2584) Spurious warnings when using multiple file sources

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: Spurious warnings when using multiple file sources 










This is clearly a regression of 3.6.
Puppet should be silent, if we have multiple sources defined and in the end one maches. Otherwise we get tons of Warnings when using multiple sources of a file, which is a bad UX pattern. We don't want to get warnings if they are not relevant!












   

 Add Comment

























 Puppet /  PUP-2584



  Spurious warnings when using multiple file sources 







 When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names):  {code}  Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=managesource_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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 

Jira (PUP-2584) Spurious warnings when using multiple file sources

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier updated an issue


















 Puppet /  PUP-2584



  Spurious warnings when using multiple file sources 










Change By:

 Peter Meier




Priority:

 Normal Critical












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2303) ArgumentErrors in file_server config parser are swallowed by raising the exception wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue


















 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the exception wrong 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:


 Unassigned




Created:


 18/Apr/14 11:09 AM




Priority:

  Normal




Reporter:

 Peter Meier










Within the parser for the file_serving config, multiple ArgumentErrors are raised with the wrong amount of arguments, raising a different ArgumentError.
Like: Yo dawg, I heard you like ArgumentErrors so I put an ArgumentError in your ArgumentError.
PR coming.












   

 Add Comment


















 

Jira (PUP-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier updated an issue


















 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the error wrong 










Change By:

 Peter Meier




Summary:

 ArgumentErrorsinfile_serverconfigparserareswallowedbyraisingthe exception error wrong












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2303) ArgumentErrors in file_server config parser are swallowed by raising the error wrong

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: ArgumentErrors in file_server config parser are swallowed by raising the error wrong 










https://github.com/puppetlabs/puppet/pull/2553












   

 Add Comment

























 Puppet /  PUP-2303



  ArgumentErrors in file_server config parser are swallowed by raising the error wrong 







 Within the parser for the file_serving config, multiple ArgumentErrors are raised with the wrong amount of arguments, raising a different ArgumentError.   Like: Yo dawg, I heard you like ArgumentErrors so I put an ArgumentError in your ArgumentError.   PR coming.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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-2142) selboolean provider does not fully manage persistent feature

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue


















 Puppet /  PUP-2142



  selboolean provider does not fully manage persistent feature 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 02/Apr/14 6:18 AM




Environment:


selinux




Priority:

  Normal




Reporter:

 Peter Meier










The provider for selboolean is very limited regarding the persistent parameter:
Puppet will only set a boolean to be persistent if it will also change the current value.
This is because the provider (getseboolean) does not support retrieving the current state of the persistent field.
This has the drawback, that if a boolean is already enabled, but later should also be enabled in a persistent manner, puppet won't do the necessary change and simply skips that task.








  

Jira (PUP-2020) Expose config_version via REST Api

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue


















 Puppet /  PUP-2020



  Expose config_version via REST Api 










Issue Type:

  New Feature




Assignee:

 Andy Parker




Components:


 Networking Services




Created:


 23/Mar/14 10:36 AM




Priority:

  Normal




Reporter:

 Peter Meier










It would be interesting to expose the config_version via REST-Api, so that people having an own config_version script, would be able to query from the puppet client if the config_version changes since the last run and e.g. only run puppet apply then.












   

 Add Comment






















 This message was sent by Atlassian JIRA 

Jira (PUP-1568) Error reporting within augeas provider fails

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier created an issue


















 Puppet /  PUP-1568



  Error reporting within augeas provider fails 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 02/Feb/14 5:13 AM




Labels:


 puppet augeas




Priority:

  Normal




Reporter:

 Peter Meier










If the augeas provider fails to store a change to a file it's error reporting is broken due to the refactoring that happened in https://github.com/puppetlabs/puppet/commit/000b8fef6a33e5c9f56c0801523de15a0e5bc30b


# cat foo.pp 
augeas{'enable_shorewall':
  context = '/files/etc/sysconfig/shorewall',
  changes = 'set startup 1',
  lens= 'Shellvars.lns',
  incl= '/etc/sysconfig/shorewall',
}
# lsattr /etc/sysconfig/shorewall
ie- /etc/sysconfig/shorewall
# puppet apply --debug --trace foo.pp 
Notice: Compiled catalog for foo in environment production in 0.10 seconds
Debug: Creating default schedules
Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not exist
Debug: 

Jira (PUP-1568) Error reporting within augeas provider fails

[Peter Meier (JIRA)]

Title: Message Title










 

 Peter Meier commented on an issue


















  Re: Error reporting within augeas provider fails 










https://github.com/puppetlabs/puppet/pull/2324












   

 Add Comment

























 Puppet /  PUP-1568



  Error reporting within augeas provider fails 







 If the augeas provider fails to store a change to a file it's error reporting is broken due to the refactoring that happened in https://github.com/puppetlabs/puppet/commit/000b8fef6a33e5c9f56c0801523de15a0e5bc30b   {noformat}  # cat foo.pp  augeas{'enable_shorewall':  context = '/files/etc/sysconfig/shorewall',  changes = 'set startup 1',  lens ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
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/groups/opt_out.