Jira (PDB-170) exported resources with single element arrays aren't arrays on the collected side

2017-05-19 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PDB-170 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: exported resources with single element arrays aren't arrays on the collected side  
 
 
 
 
 
 
 
 
 
 
We worked around it with puppetdb query. Fine to close it, can we update the docs to reflect this limitation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4051) Master unable to reliably reload puppet.conf

2015-02-26 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4051 
 
 
 
   Master unable to reliably reload puppet.conf  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Andy Parker 
 
 
 

Components:
 

 Server 
 
 
 

Created:
 

 2015/02/26 12:53 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rolf 
 
 
 
 
 
 
 
 
 
 
The webrick puppet master watches its config file for changes. When the file changes, it then will reload the file, and try to apply a new settings catalog. However, depending on what the settings catalog will end up doing, this may throw an error, which results in the master process shutting down. 
You can reproduce this problem by simply starting a puppet master daemon, opening the /etc/puppet/puppet.conf file, and inserting the line: 
 
 
 
 
 
 
ssldir = /var/lib/puppet/ssl2
 
 
 
 
 
 
 
This should cause the master to crash. 
The problem stems from the fact that the master has dropped privileges as part of daemonizing. Therefore there are certain changes to the system that it simply can't 

Jira (PUP-4051) Master unable to reliably reload puppet.conf

2015-02-26 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4051 
 
 
 
   Master unable to reliably reload puppet.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 
 
 
 
 
 
 
 Thewebrickpuppetmasterwatchesits{{config}}fileforchanges.Whenthefilechanges,itthenwillreloadthefile,andtrytoapplyanewsettingscatalog.However,dependingonwhatthesettingscatalogwillendupdoing,thismaythrowanerror,whichresultsinthemasterprocessshuttingdown. Youcanreproducethisproblembysimplystarting Whiledebugginganunrelatedpuppetdbissue,Ichangeddebug_levelon a vagranttestingrecipeIusefortestingroleswithexportedresources.Iaddedlog_level=debugandsuddenlymynodeswouldstartgetting puppet masterdaemon,openingthe{{/etc/puppet/puppet runfailures . conf}}file, Arestartwasneeded and inserting the line:{noformat}ssldir=/var/lib/ nodeswouldthengetsuccessful puppet /ssl2 runs.  {noformat}  This It should cause benotedthat the master catalogwouldcompilejustfine.Inparticular,thefailureswerearoundhieradatafromparentclasses.Icompiledthecatalog to crash verifythehieralookupwasfoundappropriately . Theproblemstemsfromthefact PUP-2834wasclosedaswont-fixbutIthinkminimally thatthe masterhasdroppedprivilegesaspart puppetconfigautoreloadshouldbedisabledonwebrickinstances.Thiskind of daemonizing erroneousbehaviormakestroubleshootingallbutimpossible . Thereforetherearecertainchangestothesystemthatitsimplycan'tperform. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique

2015-02-02 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PUP-3813 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique  
 
 
 
 
 
 
 
 
 
 
Also, verified issue occurs in: 
 
 
 
 
 
 
$ puppet --version 
 
 
 
 
3.7.3
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-170) exported resources with single element arrays aren't arrays on the collected side

2015-01-22 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PDB-170 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: exported resources with single element arrays aren't arrays on the collected side  
 
 
 
 
 
 
 
 
 
 
Same issue on: 
 

puppet --version 3.4.3
 

cat /etc/redhat-release CentOS release 6.6 (Final)
 

ruby --version ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique

2015-01-16 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is propagating to child resources in nested exported resources with same namevar values (diff types) and is conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Summary:
 
 Aliasispropagatingtochildresourcesinnestedexportedresourceswithsamenamevar valus values (difftypes)andisconflictingasnonunique 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is propagating to child resources in nested exported resources with same namevar valus (diff types) and is conflicting as non unique

2015-01-09 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PUP-3813 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Alias is propagating to child resources in nested exported resources with same namevar valus (diff types) and is conflicting as non unique  
 
 
 
 
 
 
 
 
 
 
Is this possibly related to https://tickets.puppetlabs.com/browse/PUP-121? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Affects Version/s:
 
 PUP3.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PUP-3813 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 
 
Updated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Assignee:
 
 Rolf HenrikLindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Assignee:
 
 Rolf HenrikLindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf commented on  PUP-3813 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 
 
I have tried both _ and no separator, same results. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is propagating to child resources in nested exported resources with same namevar valus (diff types) and is conflicting as non unique

2015-01-08 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is propagating to child resources in nested exported resources with same namevar valus (diff types) and is conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Summary:
 
 Aliasis popagating propagating tochildresourcesinnestedexportedresourceswithsamenamevarvalus(difftypes) are andis conflictingasnonunique 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-07 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 
 
 
 
 
 
 
 Ihaveanexportedresourcethatcreatesotherresourceswhenitscollected.Manyofthoseresourcessharethesamenamevarvaluebutisuniquetoeachtype.Forsomereason,analiasisregisteredatthetopexportedresourceandthenpropagatestoallthechildren,regardlessoftype.Ihavebeenabletoreplicatethisissuewithafairlysimplenodes.pp{code} node/puppet.vagrant/inheritsdefault{ import'/etc/puppet/environments/production/manifests/site.pp' node/puppet.vagrant/inheritsdefault{ includepuppet::masterincludepuppet::db}definetest::instance::install(){file{/tmp/${name}:ensure=link,target='/etc/passwd',}-file{/tmp/${name}_2:ensure=link,target='/etc/passwd',}-file{/tmp/${name}_3:ensure=link,target='/etc/passwd',}}definetest::instance(){test::instance::install{test:instance:${name}:install:name=$name}}classprofile::shared_test($instance_name=UNDEF){@@test::instance{test:instance:${name}:name=$instance_name}}node/export1/{class{'profile::shared_test':instance_name='foobar'}}node/node1/{Test::Instance||}{code}Thisresultsin:{code}/tmp/foobar_2cannotcreatealiasfoobar:objectalreadyexists{code}Whenyoucompilethecatalogonthemasteryoucanseethealiaspropagation:{code}{tags:[instance,class,node1,test::instance,test,test:instance:foobar,node],title:test:instance:foobar,exported:false,parameters:{alias:foobar,name:foobar},type:Test::Instance},{tags:[test::instance::install,instance,class,node1,test,test::instance,test:instance:foobar,install,test:instance:foobar:install,node],title:test:instance:foobar:install,exported:false,file:/vagrant/nodes.pp,line:29,parameters:{alias:foobar,name:foobar},type:Test::Instance::Install},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar,exported:false,file:/vagrant/nodes.pp,line:13,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,before:File[/tmp/foobar_2],ensure:link,owner:root,mode:0644},type:File},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar_2,exported:false,file:/vagrant/nodes.pp,line:17,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,before:File[/tmp/foobar_3],ensure:link,owner:root,mode:0644},type:File},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar_3,exported:false,file:/vagrant/nodes.pp,line:21,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,ensure:link,owner:root,mode:0644},type:File}{code}I'vemanagedtostacktracethisdownto:{code}/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:69:in`add_resource'{code}Whencompilingthecatalog,itappearsthattheresourceisadded2x.Thefirsttimeithasproperparameters(withoutanalias)andthenthesecondtimeithastheoriginalparametersplusanalias(andseveralothers?).Thecruxoftheissueseemstoberelatedtothenamevars.Icaneitherchangethemorexplicitlysetthealiasasworkarounds. 
 
 
 

Jira (PUP-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-07 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 
 
 
 
 
 
 
 Ihaveanexportedresourcethatcreatesotherresourceswhenitscollected.Manyofthoseresourcessharethesamenamevarvaluebutisuniquetoeachtype.Forsomereason,analiasisregisteredatthetopexportedresourceandthenpropagatestoallthechildren,regardlessoftype.Ihavebeenabletoreplicatethisissuewithafairlysimplenodes.pp{code}import'/etc/puppet/environments/production/manifests/site.pp'node/puppet.vagrant/inheritsdefault{includepuppet::masterincludepuppet::db}definetest::instance::install(){file{/tmp/${name}:ensure=link,target='/etc/passwd',}-file{/tmp/${name}_2:ensure=link,target='/etc/passwd',}-file{/tmp/${name}_3:ensure=link,target='/etc/passwd',}}definetest::instance(){test::instance::install{test:instance:${name}:install:name=$name}}classprofile::shared_test($ name instance_name =UNDEF){@@test::instance{test:instance:${name}:name=$ name instance_name }}node/export1/{class{'profile::shared_test': name instance_name ='foobar'}}node/node1/{Test::Instance||}  {code}Thisresultsin:{code}/tmp/foobar_2cannotcreatealiasfoobar:objectalreadyexists{code}Whenyoucompilethecatalogonthemasteryoucanseethealiaspropagation:{code}{tags:[instance,class,node1,test::instance,test,test:instance:foobar,node],title:test:instance:foobar,exported:false,parameters:{alias:foobar,name:foobar},type:Test::Instance},{tags:[test::instance::install,instance,class,node1,test,test::instance,test:instance:foobar,install,test:instance:foobar:install,node],title:test:instance:foobar:install,exported:false,file:/vagrant/nodes.pp,line:29,parameters:{alias:foobar,name:foobar},type:Test::Instance::Install},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar,exported:false,file:/vagrant/nodes.pp,line:13,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,before:File[/tmp/foobar_2],ensure:link,owner:root,mode:0644},type:File},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar_2,exported:false,file:/vagrant/nodes.pp,line:17,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,before:File[/tmp/foobar_3],ensure:link,owner:root,mode:0644},type:File},{tags:[test::instance::install,instance,class,node1,test,test::instance,file,test:instance:foobar,install,test:instance:foobar:install,node],title:/tmp/foobar_3,exported:false,file:/vagrant/nodes.pp,line:21,parameters:{group:root,backup:main,target:/etc/passwd,alias:foobar,ensure:link,owner:root,mode:0644},type:File}{code}I'vemanagedtostacktracethisdownto:{code}/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:69:in`add_resource'{code}Whencompilingthecatalog,itappearsthattheresourceisadded2x.Thefirsttimeithasproperparameters(withoutanalias)andthenthesecondtimeithastheoriginalparametersplusanalias(andseveralothers?).Thecruxoftheissueseemstoberelatedtothenamevars.Icaneitherchangethemorexplicitlysetthealiasasworkarounds. 
 
 
  

Jira (PUP-3813) Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique

2015-01-06 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Alias is popagating to child resources in nested exported resources with same namevar valus (diff types) are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rolf 
 
 
 

Summary:
 
 Autocreatedaliases Aliasispopagatingtochildresources innestedexportedresources withsamenamevarvalus(difftypes) areconflictingasnonunique 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3813) Auto created aliases in nested exported resources are conflicting as non unique

2015-01-06 Thread Rolf (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rolf created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3813 
 
 
 
  Auto created aliases in nested exported resources are conflicting as non unique  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/06 5:40 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Rolf 
 
 
 
 
 
 
 
 
 
 
I have an exported resource that creates other resources when its collected. Many of those resources share the same namevar value but is unique to each type. For some reason, an alias is registered at the top exported resource and then propagates to all the children, regardless of type. I have been able to replicate this issue with a fairly simple nodes.pp 
 
 
 
 
 
 
import '/etc/puppet/environments/production/manifests/site.pp' 
 
 
 
 
 
 
 
 
 
node /puppet.vagrant/ inherits default { 
 
 
 
 
  include puppet::master