Jira (FACT-1890) Facter report zfs snapshot as partition

[t (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 t updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1890  
 
 
  Facter report zfs snapshot as partition   
 

  
 
 
 
 

 
Change By: 
 t  
 

  
 
 
 
 

 
 On a FreeBSD server (FreeBSD 11.2-Release-p4), sometime the facter return inside the mount hash all zfs snapshots as partition.Event zfs list didn't not return those snapshot partition.I've no idea if facter should or shouldn't return zfs snapshot as partition, but it definitively shouldn't return as "normal" partition.The weird part is he only So for reproducing the problem :You need to access  ( at this moment cd .zfs/snapshot/SOMETHING are {color:#FF}not{color} enough )  do that for  one  set of  file in a  snapshot , after that all snapshot from that dataset are show by facter.    
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (FACT-1890) Facter report zfs snapshot as partition

[t (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 t updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1890  
 
 
  Facter report zfs snapshot as partition   
 

  
 
 
 
 

 
Change By: 
 t  
 

  
 
 
 
 

 
 On a FreeBSD server (FreeBSD 11.2-Release-p4), sometime the facter return inside the mount hash all zfs snapshots as partition. It Event zfs list didn ' s in fact look like a partition but it's t  not  a real  return those snapshot  partition.I've no idea if facter should or shouldn't return zfs snapshot as partition, but it definitively shouldn't return as "normal" partition. The weird part is he only (at this moment) do that for one set of snapshot   
 

  
 
 
 
 

 
 
 

 
 
 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, 

Jira (FACT-1890) Facter report zfs snapshot as partition

[t (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 t created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1890  
 
 
  Facter report zfs snapshot as partition   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 FACT 3.12.z  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/17 6:37 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 t  
 

  
 
 
 
 

 
 On a FreeBSD server (FreeBSD 11.2-Release-p4), sometime the facter return inside the mount hash all zfs snapshots as partition. It's in fact look like a partition but it's not a real partition. I've no idea if facter should or shouldn't return zfs snapshot as partition, but it definitively shouldn't return as "normal" partition. The weird part is he only (at this moment) do that for one set of snapshot   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

Jira (FACT-1491) Failed to get IP Address

[t (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 t commented on  FACT-1491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to get IP Address   
 

  
 
 
 
 

 
 I see Branan Riley ask for help. I'm the person who open this issue. I don't known if it's worth the time to solve this problem. This problem appeart only when using facter inside a vserver.  But as I know vserver are at it end of life, vserver don't support systemd. We still using vserver because we got lot of service, but we currently migrate to something like lxc/systemd-nspawn, that's going to take time.   <
 /td> 
 

  
 
 
 
 

 
 
 

 
 
 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-4774) File_line equivalent for databases

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. commented on  PUP-4774 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File_line equivalent for databases  
 
 
 
 
 
 
 
 
 
 

I think the mysql module is what you're looking for in this case
 
I was thinking of a unified interface, that would work with any database – or, at least, the most common ones. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6938) ssh_authorized_key should be able to take a ready-made OpenSSH public key

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6938 
 
 
 
  ssh_authorized_key should be able to take a ready-made OpenSSH public key  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/23 12:20 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
When creating adding an authorized public key with the Ssh_authorized_key-resource, the manifest is supposed to provide all of the pieces of the key. 
It would be very nice, if the resource could simply parse an existing foo.pub in the format used by OpenSSH (maybe, in some other formats as well). The path to the file can be interpreted the same way, source-attribute of the File-resource is or, perhaps even better, the way template() interprets its arguments. 
Options specified in the manifest can complement and, in case of conflict, overwrite those found in the file. 
By treating the keys as data rather than as code, it would be easier for users to deal with large number of them. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

Jira (FACT-1491) Failed to get IP Address

[t (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 t commented on  FACT-1491 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to get IP Address  
 
 
 
 
 
 
 
 
 
 
 Le 31/10/2016 à 11:51:00-0700, Branan Riley (JIRA) a écrit 
Sorry for the delay : 
 ip addr 
 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 3: eth1:  mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:26:b9:77:42:c7 brd ff:ff:ff:ff:ff:ff inet XXX.YYY.193.TTT/24 brd XXX.YYY.193.255 scope global secondary eth1 valid_lft forever preferred_lft forever 
 ip route 
 default via XXX.YYY.194.1 dev if2 XXX.YYY.193.0/24 dev eth1 proto kernel scope link src XXX.YYY.193.TTT XXX.YYY.194.0/24 dev if2 proto kernel scope link src XXX.YYY.194.EEE XXX.YYY.200.0/24 dev if4 proto kernel scope link src XXX.YYY.200.FFF 
 If I use the old facter 
 facter ipaddress 
 I get what I want. 
 If I use the new facter I get a empty line 
But well. I don't known if it's very important thing, yes I think they are a bug inside the new facter. But vserver is in the path to end_of_life because vserver don't support systemd. 
And vserver make some very weird route table. 
So if you can solve that it's very good, if you cannot (or more probably don't get the time) it's ok too (for me). 
Regards 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PUP-6838) file_line should support "before"-clause as well as "after"

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6838 
 
 
 
  file_line should support "before"-clause as well as "after"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/22 10:16 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
It is currently possible to specify, that the specified line should be inserted after a particular regexp. However, sometimes the location can only be specified as before a line. 
For example, one may wish to insert an XML-snippet into a config file before a particular closing tag – regardless of what's preceding it. Please, add the feature. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6837) file_line confused, when the "line" is multi-line text

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6837 
 
 
 
  file_line confused, when the "line" is multi-line text  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/22 10:12 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
I needed to insert a multi-line XML-snippet into web.xml-file configuring a vendor-supplied Tomcat-instance. The file_line seemed like an almost perfect way to do it: 
 
 
 
 
 
 
  file_line{'Insist on secure connections': 
 
 
 
 
path=> "${base}/conf/web.xml", 
 
 
 
 
line=> template('atlassian/secure-tomcat.xml'), 
 
 
 

Jira (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T assigned an issue to Jenny Mahmoudi 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Assignee:
 
 Paul T Jenny Mahmoudi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T assigned an issue to Paul T 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Assignee:
 
 Jenny Mahmoudi Paul T 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Priority:
 
 Blocker Normal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Summary:
 
 Hiera cannot find  datafile  datadir 
 
 
 
 
 
 
 
 
 
 I have  a  working puppet 2016.2.1 using code manager (r10k) and environments (dev, staging, prod). This is working great. I than started to utilize hiera. When setting the hiera.yaml (as shown below). I'm getting the error "Cannot find datafile /etc/puppetlabs/code/environments*//*hieradata/common.yaml, skipping"#---:backends:  - yaml:hierarchy:  - "nodes/%{::trusted.certname}"  - "%{environment}"  - "puppet_role/%{puppet_role}"- common:yaml::datadir: "/etc/puppetlabs/code/environments/%{::environment}/hieradata"#I notice the double backslash which is a problem. If I replace the environment variable with an actual  environment  name (e.g.  :datadir: "/etc/puppetlabs/code/environments/*  development */hieradata" ) and run hiera  --  debug i get back results. Has anyone run into this?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

Jira (HI-541) Hiera cannot find datadir

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datadir  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul T 
 
 
 

Labels:
 
 3.2 hiera 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-541) Hiera cannot find datafile

[Paul T (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul T created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-541 
 
 
 
  Hiera cannot find datafile  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 3.2.0 
 
 
 

Assignee:
 
 Jenny Mahmoudi 
 
 
 

Components:
 

 UX 
 
 
 

Created:
 

 2016/10/20 12:19 PM 
 
 
 

Environment:
 
 
CentOS Linux release 7.2.1511 (Core) Puppet 4.5.3 (2016.2.1)strong text Hiera 3.2.0 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Paul T 
 
 
 
 
 
 
 
 
 
 
I have working puppet 2016.2.1 using code manager (r10k) and environments (dev, staging, prod). This is working great. I than started to utilize hiera. When setting the hiera.yaml (as shown below). I'm getting the error "Cannot find datafile /etc/puppetlabs/code/environments*//*hieradata/common.yaml, skipping" 
# — :backends: 
 

yaml
 
 
:hierarchy: 
 

Jira (PUP-6680) Descendant providers do not inherit features from ancestors

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6680 
 
 
 
  Descendant providers do not inherit features from ancestors  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/09/05 6:44 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
My package-provider is very simple – it derives from the stock gem-provider and overwrites gemcmd to use the gem-executable installed with RedHat's rh-ruby22 package for RHEL/CentOS-6 (where the default Ruby is 1.8.7): 
 
 
 
 
 
 
require 'puppet/provider/package' 
 
 
 
 
  
 
 
   

Jira (PUP-620) (PR 2429) Add install_options to gem provider

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. commented on  PUP-620 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: (PR 2429) Add install_options to gem provider  
 
 
 
 
 
 
 
 
 
 
I can't get this to work either: 
 
 
 
 
 
 
  package {'sensu': 
 
 
 
 
ensure  => installed, 
 
 
 
 
provider=> 'gem22', 
 
 
 
 
install_options => ['--clear-sources', {'--source' => $gemsrc}], 
 
 
 
 
  }
 
 
 
 
 
 
 
While Puppet is running, I can see the gem's complete command-line – neither of the two install-options are on it: 
 
 
 
 
 
 
/opt/rh/rh-ruby22/root/usr/bin/ruby /opt/rh/rh-ruby22/root/usr/bin/gem install --no-rdoc --no-ri sensu
 
 
 
 
 
 
 
The gem22 is our own little provider here, which descends from the official Puppet's gem by replacing the gemcmd: 
 
 
 
 
 
 
require 'puppet/provider/package' 
 
 
   

Jira (FACT-1491) Failed to get IP Address

[t (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 t created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1491 
 
 
 
  Failed to get IP Address  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.4.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 PE 
 
 
 

Created:
 

 2016/08/22 5:56 AM 
 
 
 

Environment:
 
 
Os : Linux Debian in vserver 
Puppet version : official puppet-agent from Puppetlabs 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 t 
 
 
 
 
 
 
 
 
 
 
When I use facter on a server who DON'T have eth0 but only eth1 (or more), the facter ipaddress return a empty string. 
root:~# /opt/puppetlabs/puppet/bin/facter ipaddress 
root:~# 
The second problem (I think related) is the network.primary information are incorrect. For example 
{ domain => "xxx.fr", fqdn => "yyy.xxx.fr", hostname => "yyy", interfaces => { eth1 => { bindings => [  { address => "aaa.bbb.ccc.78", netmask => "255.255.255.0", network => "aaa.bbb.ccc.0" } 

Jira (PUP-5427) incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. commented on  PUP-5427 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.  
 
 
 
 
 
 
 
 
 
 
There are two problems here: 
 

The gem-provider should not rely on the $PATH for the default gem – it must explicitly invoke the gem-executable appropriate for the underlying OS. On Linux that's /usr/bin/gem, on FreeBSD that's typically /usr/local/bin/gem and so on.
 

The gem-provider must allow specifying an alternative gemcmd. People have been asking for this for years. Something like: 
 
 
 
 
 
 
  package {'foo': 
 
 
 
 
ensure   => 'latest', 
 
 
 
 
provider => 'gem', 
 
 
 
 
gemcmd   => '/usr/local/bin/gem22' 
 
 
 
 
  }
 
 
 
 
 
 
 
ought to work. But does not...
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
   

Jira (PUP-6236) Allow parameters in the values of resource-attributes

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6236 
 
 
 
  Allow parameters in the values of resource-attributes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 Here is my use-case... I need to install a number of files into a directory, that is not itself managed by Puppet. The files themselves are all under the {{files/}} subdirectory of my module and named just as they should be named once installed.The ownership and permissions will be the same for all of them, so it is tempting to use the {{File}}-resource _once_ -- passing it an _array_ of file-names.Unfortunately, because the {{source}}-attribute is different, I can not use the compact form of resource-definition. It would've been nicer, if the (parts of) resource-name were usable in the attribute-values. For example, the name itself can be accessible as {{%n}} and the basename of that -- as {{%b}}. Then I'd be able to do:{code:puppet}  file {['/foo/one', '/foo/two', '/foo/three']:source => "puppet:///${module_name}/%b",group  => ...  }{code}Now, of course, one can argue, that the File-resource itself should be smart enough to automatically append the {{basename($name)}} to any {{source}}-attribute ending with a slash -- to solve my problem thus:{code:puppet}source => "puppet:///${module_name}/"{code}but a more general approach may be more useful. For example, if the file-content were to come from {{templates/}} instead of {{files/}}, one would be able to use a construct like:{code:puppet}content => template("${module_name}/%b.erb"){code}Another use-case would be expressing dependency of a Service on the corresponding service-script File (on Unix):{code:puppet}  service {["one", "two", "three"]:require => File["/etc/init.d/%n" ]   }...  file {["/etc/init.d/one", "/etc/init.d/two", "/etc/init.d/three"]:notify => Service["%b"]  }{code}Obviously, macros other than {{%b}} and {{%n}} can be thought up... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
  

Jira (PUP-6236) Allow parameters in the values of resource-attributes

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6236 
 
 
 
  Allow parameters in the values of resource-attributes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 Here is my use-case... I need to install a number of files into a directory, that is not itself managed by Puppet. The files themselves are all under the {{files/}} subdirectory of my module and named just as they should be named once installed.The ownership and permissions will be the same for all of them, so it is tempting to use the {{File}}-resource _once_ -- passing it an _array_ of file-names.Unfortunately, because the {{source}}-attribute is different, I can not use the compact form of resource-definition. It would've been nicer, if the (parts of) resource-name were usable in the attribute-values. For example, the name itself can be accessible as {{%n}} and the basename of that -- as {{%b}}. Then I'd be able to do:{code:puppet}  file {['/foo/one', '/foo/two', '/foo/three']:source => "puppet:///${module_name}/%b",group  => ...  }{code}Now, of course, one can argue, that the File-resource itself should be smart enough to automatically append the {{basename($name)}} to any {{source}}-attribute ending with a slash -- to solve my problem thus:{code:puppet}source => "puppet:///${module_name}/"{code}but a more general approach may be more useful. For example, if the file-content were to come from {{templates/}} instead of {{files/}}, one would be able to use a construct like:{code:puppet}content => template("${module_name}/%b.erb"){code}Another use-case would be expressing dependency of a Service on the corresponding service-script File (on Unix):{code:puppet}  service {["one", "two", "three"]:require => File["/etc/init.d/%n"  }...  file {["/etc/init.d/one", "/etc/init.d/two", "/etc/init.d/three"]:notify => Service[ " %b " ]  }{code}Obviously, macros other than {{%b}} and {{%n}} can be thought up... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 

Jira (PUP-6236) Allow parameters in the values of resource-attributes

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6236 
 
 
 
  Allow parameters in the values of resource-attributes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Affects Versions:
 

 PUP 3.8.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2016/04/26 12:41 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
Here is my use-case... I need to install a number of files into a directory, that is not itself managed by Puppet. The files themselves are all under the files/ subdirectory of my module and named just as they should be named once installed. 
The ownership and permissions will be the same for all of them, so it is tempting to use the File-resource once – passing it an array of file-names. 
Unfortunately, because the source-attribute is different, I can not use the compact form of resource-definition. It would've been nicer, if the (parts of) resource-name were usable in the attribute-values. For example, the name itself can be accessible as %n and the basename of that – as %b. Then I'd be able to do: 
 
 
 
 
 
  

Jira (PUP-4774) File_line equivalent for databases

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4774 
 
 
 
  File_line equivalent for databases  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/06/22 10:30 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 
Given the number of applications storing most of their configuration in a database (JIRA, Drupal are just two example), it would be quite useful to be able to maintain rows of configuration tables in the same way the already existing file_line can maintain lines in configuration files. For example, the way to ensure, Drupal's variable-table has the correct address of the site's admin would be: 
 
 
 
 
 
 
table_row { Administrator's address: 
 
 
 
 
server = mysql://localhost, 
 
 
 
 
table = variable, 
  

Jira (PUP-4774) File_line equivalent for databases

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4774 
 
 
 
  File_line equivalent for databases  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 Giventhenumberofapplicationsstoringmostoftheirconfigurationinadatabase(JIRA,Drupalarejusttwo example examples ),itwouldbequiteusefultobeabletomaintainrowsofconfiguration_tables_inthesamewaythealreadyexisting{{file_line}}canmaintainlinesinconfiguration_files_.Forexample,thewaytoensure,Drupal's{{variable}}-tablehasthecorrectaddressofthesite'sadminwouldbe:{noformat}table_row{Administrator'saddress:server=mysql://localhost,table=variable,key=name='site_mail',ensure=value='ad...@example.com'}{noformat}I'dbehappytodiscussfinerdetailsand,maybe,evenofferanimplementation--ifthereisaPuppetdeveloperagreeing,thatthiswouldbeagoodthingtoaddtothesoftware. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4774) File_line equivalent for databases

[Mikhail T. (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail T. updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4774 
 
 
 
  File_line equivalent for databases  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikhail T. 
 
 
 
 
 
 
 
 
 
 Giventhenumberofapplicationsstoringmostoftheirconfigurationinadatabase(JIRA,Drupalarejusttwoexamples),itwouldbequiteusefultobeabletomaintainrowsofconfiguration_tables_inthesamewaythealreadyexisting{{file_line}}canmaintainlinesinconfiguration_files_.Forexample,thewaytoensure,Drupal's{{variable}}-tablehasthecorrectaddressofthesite'sadminwouldbe:{noformat}table_row{Administrator'saddress:server=mysql://localhost /drupal ,table=variable,key=name='site_mail',ensure=value='ad...@example.com'}{noformat}I'dbehappytodiscussfinerdetailsand,maybe,evenofferanimplementation--ifthereisaPuppetdeveloperagreeing,thatthiswouldbeagoodthingtoaddtothesoftware. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.