Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Thomas Buts updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Thomas Buts Affects Version/s: PUP3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen kbarber commented: My concern is that this is a contract to our users, and a decision on the topology should be thought through. A breaking change later might upset people. I'd like to see this actually working somehow, before we make a decision on the topology to be honest. Has someone ran this through Graphite, and has some results for us to see? I see a bit of request.key being thrown around, but this isn't threaded throughout the entire request, (like munge_catalog doesn't have it) some parts are cumulative, other parts seem to be more like they are per request. We need to make sure our direction is clear and its consistent throughout. I'm almost tempted to make sure we understand the impact of per request metric storage, in a way we get per request in the log itself, does this also need to be expressed in graphite? Point being, do we need per request, can we make sure our topology design allows for per request when we go to add it later? Otherwise, can we get the best of both worlds, or at least have a clear way to get per request and cumulative stats. @cprice404's comments are alluding to this concern. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PDB-1017) Node tests broken due to bug in assertion code
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1017 Node tests broken due to bug in assertion code Change By: Ryan Senior Fix Version/s: 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Change By: Jeremy Barlow Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Gavin Williams commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. +1 from me. I've been hit by this with my NetApp types/providers before, but never tracked the issue down... So thank's for that Tomas Doran. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3676) Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-3676 Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server Issue Type: Task Assignee: Unassigned Components: Puppet Server Created: 2014/11/17 8:25 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Jeremy Barlow For Puppet Server, we've been making a conscious effort to avoid having any JRuby OpenSSL functionality be used. This is due to the JRuby OpenSSL functionality being problematic. Whenever a require 'puppet' call is made in Ruby code – which isn't avoidable for Puppet Server – the following chain of requires occurs: puppet/ssl puppet/ssl/host puppet/ssl/key puppet/ssl/base
Jira (PUP-3676) Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3676 Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server Change By: Jeremy Barlow Assignee: JeremyBarlow Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3676) Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3676 Avoid OpenSSL::X509::Name calls in ssl.rb for Puppet Server Change By: Jeremy Barlow Sprint: SERVER2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Jeremy Barlow commented on PUP-3522 Re: Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module This ticket was originally about trying to avoid the require 'openssl' call that puppet/util/monkey_patches performs transitively just by the Puppet Server master Ruby class performing a require 'puppet' call. After further discussion, we decided that, while this is not ideal, that it is not worth trying to avoid this particular code path in Puppet Server. The problem seen with the OpenSSL::X509::StoreError was overcome for Debian by changes made in the packaging of pe-java for Debian, ensuring that some default cacerts were present. We have not seen further related problems with initialization since the pe-java change was made. Broadening the scope of this ticket, I used the Ruby set_trace_func on ~3.7.3 Puppet code to find any references to OpenSSL Ruby objects by the Puppet master during initialization and an agent run. I only found three usages: 1) Use of OpenSSL::X509::Store downstream from the known require 'openssl' call from puppet/util/monkey_patches. 2) Use of OpenSSL::ASN1::ObjectId from Puppet::SSL::Oids (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/ssl/oids.rb#L43). Avoiding the initialization of these objects is being handled as part of PUP-3520. 3) Use of OpenSSL::X509::Name from Puppet::Util::SSL (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/ssl.rb#L7-L13). Avoiding the initialization of these objects is being handled by PUP-3676. Closing out this ticket with follow-up work to be tracked in linked tickets. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 (PDB-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen cprice404 commented: @kbarber I agree; I think the metric IDs warrant some thought and that you guys are much more qualified to decide what they should be than we are. The goal of this PR was just to get the ball rolling and get your terminus code into a state where it won't be broken against Puppet 4 (because the old profiler API has already been removed from Puppet 4: https://github.com/puppetlabs/puppet/commit/357cd6b4951dcda902d81ccd31d727b6641e19dc ). If you would prefer for us to close this out until such time as you guys have bandwidth to come up with metric ids that you are comfortable with, we can do so. Alternately, we could just tweak this a bit more to get it into the right ballpark, and you could go ahead and merge it so that your CI tests won't fail against the puppet master branch, and then you guys can polish them up before you do your next release? Happy to handle it however you like. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1019) Remove ZAML
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-1019 Remove ZAML Change By: Britt Gresham Assignee: BrittGresham Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3654) Deprecate Puppet.newtype
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-3654 Deprecate Puppet.newtype Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3666) 'configtimeout' setting is erroneously named
Title: Message Title Michael Smith commented on PUP-3666 Re: 'configtimeout' setting is erroneously named This looks like it should be tagged for docs. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen kbarber commented: @cprice404 so I think we should leave this open, at least. We want this fixed, my gut says though we should check out how it visualizes in graphite. What's more, this would be a learning exercise for us. But I'm not in the position to work on this now anyway . Plan B might be merge it in as is, and raise a ticket to investigate later, true. Leave it open for now, I'll talk with the team. And we totally appreciate the work you guys have done here, goes without saying I hope. Its an awesome feature, one of my favourites, since I've wanted an alternate to just probing HTTP /metrics/mbean/bleah or directly via JMX for a long time. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3666) 'configtimeout' setting is erroneously named
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-3666 'configtimeout' setting is erroneously named Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen kbarber commented: One question, what does 'request.key' equate to? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Kurt Wall updated an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Kurt Wall QA Contact: NarmadhaPerumal KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1030) PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen
Title: Message Title gepetto-bot commented on PDB-1030 Re: PR (1157): (PUP-3512) Use new Profiler API - fpringvaldsen cprice404 commented: `request.key` refers to a property from the indirector request. In your case it should generally just be the node certname as a string. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1031) ERROR: update or delete on table fact_paths violates foreign key constraint fact_values_path_id_fk on table fact_values
Title: Message Title Erik Lattimore created an issue PuppetDB / PDB-1031 ERROR: update or delete on table fact_paths violates foreign key constraint fact_values_path_id_fk on table fact_values Issue Type: Bug Affects Versions: 2.2.2 Assignee: Unassigned Created: 2014/11/17 10:04 AM Priority: Normal Reporter: Erik Lattimore Hi guys, ever since an upgrade to puppet 3.7 (and a corresponding upgrade of puppetdb at the same time) we have been getting postgres errors. We seem to see the following error on the puppetdb server after every invocation: Nov 17 11:01:52 postgres[6379]: [1859-1] 2014-11-17 11:01:52 EST ERROR: update or delete on table fact_paths violates foreign key constraint fact_values_path_id_fk on table fact_values Nov 17 11:01:52 postgres[6379]: [1859-2] 2014-11-17 11:01:52 EST DETAIL: Key (id)=(78) is still referenced from table fact_values.
Jira (PDB-1031) ERROR: update or delete on table fact_paths violates foreign key constraint fact_values_path_id_fk on table fact_values
Title: Message Title
Erik Lattimore updated an issue
PuppetDB / PDB-1031
ERROR: update or delete on table fact_paths violates foreign key constraint fact_values_path_id_fk on table fact_values
Change By:
Erik Lattimore
Higuys,eversinceanupgradetopuppet3.7(andacorrespondingupgradeofpuppetdbatthesametime)wehavebeengettingpostgreserrors.Weseemtoseethefollowingerroronthepuppetdbserveraftereveryinvocation:{noformat}Nov1711:01:52postgres[6379]:[1859-1]2014-11-1711:01:52ESTERROR:updateordeleteontablefact_pathsviolatesforeignkeyconstraintfact_values_path_id_fkontablefact_valuesNov1711:01:52postgres[6379]:[1859-2]2014-11-1711:01:52ESTDETAIL:Key(id)=(78)isstillreferencedfromtablefact_values.Nov1711:01:52postgres[6379]:[1859-3]2014-11-1711:01:52ESTSTATEMENT:COMMIT{noformat}It'salwaysthesamekeyID(78)thatitcomplainsabout.Wearerunningonpostgres9.1.Fromthefact_pathstable,theentrywithID78is:{noformat}id|value_type_id|depth|name|path+---+---++78|0|0|_timestamp|_timestamp{noformat}Ididn'tthink_timestampwassupposedtomakeitintopuppetdb?Thiscouldbearelicfromtheupgradethough. Inthefact_valuestable,thereare3entrieswhicharereferencingthe_timestampfact:{noformat}id|path_id|value_type_id|value_hash|value_integer|value_float|value_string|value_boolean|value_json-+-+---+--+---+-++---+2134865|78|0|226b3439f249f4fccfc7637e853c2b4a5e967160|||TueOct1413:48:04-04002014||2229630|78|0|14f01c68a6a7621cdcbc1bce80fb7e791b10a7df|||ThuOct1613:59:42-04002014||2172152|78|0|a4c93348ed4c2bb4fa6399512221512bf111f04b|||WedOct1508:38:29-04002014||{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1032) Ezbake: Get pe-puppetdb building with ezbake
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1032 Ezbake: Get pe-puppetdb building with ezbake Issue Type: Task Assignee: Unassigned Created: 2014/11/17 10:48 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber With PDB-663 we get ezbake building puppetdb FOSS, but now we need to get it working with pe-puppetdb as well. This ticket covers all the work necessary to get pe-puppetdb build using ezbake. Add Comment
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title
Eric Thompson commented on PUP-1362
Re: Rubyize yumhelper.py to remove dependency on python
verified on centos5 at SHA 7418f27 with:
[root@jl8pjfyoj16oxoi ~]# puppet apply -e package { 'ca-certificates': ensure = latest, provider = yum }
Notice: Compiled catalog for jl8pjfyoj16oxoi.delivery.puppetlabs.net in environment production in 0.24 seconds
Notice: /Stage[main]/Main/Package[ca-certificates]/ensure: created
Notice: Applied catalog in 1.03 seconds
[root@jl8pjfyoj16oxoi ~]# yum --version
3.2.22
Add Comment
Jira (PDB-1033) Ezbake: fix downstream, make sure they can build our packages in an ezbake world
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1033 Ezbake: fix downstream, make sure they can build our packages in an ezbake world Issue Type: Task Assignee: Unassigned Created: 2014/11/17 10:51 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber With ezbake, its uncertain whether downstream package maintainers can still build our system. This ticket tracks the work require to test this, and fix the problem so they can build. This covers (but not entirely): OpenSUSE, Archlinux, OpenBSD, FreeBSD as far as I'm aware. I have no knowledge on how they build, we'll need to find this out perhaps? Add Comment
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title
Eric Thompson commented on PUP-1362
Re: Rubyize yumhelper.py to remove dependency on python
verified on centos6 at SHA 7418f27 with:
[root@iwmuquwk11l6cwd ~]# yum --version
3.2.29
[root@iwmuquwk11l6cwd ~]# puppet apply -e package { 'ca-certificates': ensure = latest, provider = yum }
Notice: Compiled catalog for iwmuquwk11l6cwd.delivery.puppetlabs.net in environment production in 0.28 seconds
Notice: /Stage[main]/Main/Package[ca-certificates]/ensure: ensure changed '2013.1.95-65.1.el6_5' to '0:2014.1.98-65.0.el6_5'
Notice: Applied catalog in 3.79 seconds
Add Comment
Jira (PDB-1034) Ezbake: switch source based tests to use ezbake somehow and retire that old code
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1034 Ezbake: switch source based tests to use ezbake somehow and retire that old code Issue Type: Task Assignee: Unassigned Created: 2014/11/17 10:53 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber The ezbake work in PDB-663 introduced ezbake but we're not able to shed the old build code until we have source based installations working. This ticket tracks the work necessary to make that happen. Two ideas for now: a) We somehow open source or release ezbake (since we test in EC2 now) so that we can build on a box. This might be a good time to implement the lein plugin idea. b) We do PR testing with packages, but use Roger's pipelining idea to do this. Either way our goals should be: PR tests still work, and that old code is dead. Add Comment
Jira (PDB-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Issue Type: Bug Affects Versions: module-4.1.0 Assignee: Unassigned Created: 2014/11/17 10:55 AM Fix Versions: module-4.2.0 Priority: Normal Reporter: Kenneth Barber In PuppetDB 3.0.0 the terminus package name is now `puppetdb-termini` but our module still uses the old standard. Need to figure out what to do here. The override is to use `terminus_package` parameter in one of the classes, but this seems less optimal for long term use. Add Comment
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title
Eric Thompson commented on PUP-1362
Re: Rubyize yumhelper.py to remove dependency on python
verified on fedora19 at SHA 7b410fe with:
[root@i1b7yhuqyeissda ~]# yum --version
3.4.3
[root@i1b7yhuqyeissda ~]# puppet apply -e package { 'ca-certificates': ensure = latest, provider = yum }
Notice: Compiled catalog for i1b7yhuqyeissda.delivery.puppetlabs.net in environment production in 0.35 seconds
Notice: /Stage[main]/Main/Package[ca-certificates]/ensure: ensure changed '2012.87-10.4.fc19' to '0:2013.1.97-1.fc19'
Notice: Applied catalog in 10.81 seconds
Add Comment
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Change By: Eric Thompson QA Contact: KurtWall EricThompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3272) Remove support for yaml on the network
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3272 Remove support for yaml on the network Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1034) Ezbake: switch source based tests to use ezbake somehow and retire that old code
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1034 Ezbake: switch source based tests to use ezbake somehow and retire that old code Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1033) Ezbake: fix downstream, make sure they can build our packages in an ezbake world
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1033 Ezbake: fix downstream, make sure they can build our packages in an ezbake world Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1032) Ezbake: Get pe-puppetdb building with ezbake
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1032 Ezbake: Get pe-puppetdb building with ezbake Change By: Kenneth Barber Sprint: PuppetDB2015-01-14 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title
Eric Thompson commented on PUP-3591
Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
verified on rhel7 at SHA 7b410fe with:
[root@b13c3d7nyy6h5pc /]# puppet agent -t
Warning: Local environment: production doesn't match server specified node environment test, switching agent to test.
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[/var/lib/puppet/lib/puppet/production_env.rb]/ensure: removed
Notice: /File[/var/lib/puppet/lib/puppet/test_env.rb]/ensure: defined content as '{md5}d41d8cd98f00b204e9800998ecf8427e'
Info: Caching catalog for b13c3d7nyy6h5pc.delivery.puppetlabs.net
Warning: Local environment: test doesn't match server specified environment production, restarting agent run with environment production
Info: Retrieving pluginfacts
Jira (PUP-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-1106 Resource refreshes don't check for failed dependencies Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Eric Thompson commented on PUP-3591 Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment not passing acceptance against PE Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 (HI-293) merging not working
Title: Message Title Rene Last commented on HI-293 Re: merging not working I am also running into this issue. See my question at: http://ask.puppetlabs.com/question/14581/puppet-37-hiera-lookups/ for more details regarding my setup/configuration. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 (HI-293) merging not working
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-293
merging not working
Change By:
Henrik Lindberg
Iamtryingtoimplementhieramerging.hierismyhiera.yaml {code} ---:hierarchy:-fqdn/%{fqdn}-roles/%{role}-os/%{osfamily}-common:backends:-yaml#optionsarenative,deep,deeper:merge_behavior:deeper:yaml::datadir:/etc/puppet/environments/%{environment}/data {code} thenIhave:common.yaml {code} ---classes:-a-b {code} andfqdn/some.host.yaml {code} ---classes:-c-d {code} running {code} hiera--debug-c/etc/puppet/hiera.yamlclassesfqdn=some.hostenvironment=development[c,d] {code} and {code} hiera--debug-c/etc/puppet/hiera.yamlclassesfqdn=blablahostenvironment=development[a,b] {code} sotheblablahosttakeacommon.yamlandappliedaandbclasses..butfqdn=some.hostshouldapplya,b,c,d..andnotonlyc,dInoticedthatotheruseralsofacingthisissue.installedpackagesare: {code} rubygem-deep-merge-1.0.0-1.el6.noarchhiera-1.3.4-1.el6.noarchpuppetlabs-release-6-11.noarchpuppet-3.7.1-1.el6.noarchpuppet-server-3.7.1-1.el6.noarch {code} Regards
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Michael Smith commented on PUP-1106 Re: Resource refreshes don't check for failed dependencies Merged in https://github.com/puppetlabs/puppet/commit/ec03dee5ac403d0c110cb8c65103c0f4a2ee8391 FR should spend more time on possible side-effects and test coverage. I've done some spot testing. PUP-2280 should cover other cases mentioned in the mailing list discussion. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3654) Deprecate Puppet.newtype
Title: Message Title Michael Smith commented on PUP-3654 Re: Deprecate Puppet.newtype Merged https://github.com/puppetlabs/puppet/commit/f2bcf0ead733cd93d1b835556aee3dfe3013511e Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3666) 'configtimeout' setting is erroneously named
Title: Message Title Michael Smith commented on PUP-3666 Re: 'configtimeout' setting is erroneously named Merged https://github.com/puppetlabs/puppet/commit/3c8fb2417473616026c900c34f8b577bc8d525d2 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3272) Remove support for yaml on the network
Title: Message Title Kurt Wall commented on PUP-3272 Re: Remove support for yaml on the network On 3.7.3, Accept: yaml works in an API request: $ curl --cert /var/lib/puppet/ssl/certs/vesfy37tm7pv5m2.delivery.puppetlabs.net.pem \ --key /var/lib/puppet/ssl/private_keys/vesfy37tm7pv5m2.delivery.puppetlabs.net.pem \ --cacert /var/lib/puppet/ssl/ca/ca_crt.pem \ -H Accept: yaml https://vesfy37tm7pv5m2.delivery.puppetlabs.net:8140/production/catalog/vesfy37tm7pv5m2.delivery.puppetlabs.net --- !ruby/object:Puppet::Resource::Catalog name: vesfy37tm7pv5m2.delivery.puppetlabs.net classes: - settings resource_table: ? id001
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Peter Huene commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs As I now have Facter logging going through Puppet's log, do we want Puppet's --debug to enable Facter's debug output? Facter 2.x doesn't have the most useful debug messages, but cfacter has lots of potentially useful information in debug messages (but it might get pretty verbose). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Peter Huene commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs Should we set Facter's trace option with Puppet's --trace? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3269) Remove network access to the Resource indirection
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3269 Remove network access to the Resource indirection Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3678) Invalid module name .DS_Store error running puppet apply
Title: Message Title Jeff McCune moved an issue Puppet / PUP-3678 Invalid module name .DS_Store error running puppet apply Change By: Jeff McCune Workflow: PuppetSupportedProgram Platform Workflow Key: NETDEV PUP - 25 3678 Project: NetworkDeviceTypes Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Change By: Kylo Ginsberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Peter Huene commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs Kylo Ginsberg by the way, I started work on this ticket for testing out the Facter ticket; it's under my pup/2927 branch. If we decide to enable debugging/trace, I'll add the corresponding methods to cfacter's Ruby API. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Kylo Ginsberg commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs Yes, offhand I'd think: if puppet is emitting warning messages, then it emits facter warning messages (and higher) if puppet is emitting debug messages, then it emits facter debug messages (and higher) Re native facter verbosity, I'm inclined to try it this way and then tweak it if we find it's just too chatty. Re trace, I'm less sure. I think it'd be valuable to set trace for facter if it's set for puppet. But not sure what that would mean for native facter Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Peter Huene commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs For native facter, I think we can make it mean what it currently means for Ruby facter: Ruby stack traces are printed. Currently native facter's Ruby API will always log stack traces, so it's treating this option as always on. We don't print stack traces for native exceptions currently since there's no good cross-platform way I know of doing so. Native facter currently supports a - trace option, but it means enable trace level output (highest verbosity). I think we should rename that option to something else and treat -trace as print stack traces for custom fact exceptions for parity with Ruby facter. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Christopher Price updated an issue Puppet / PUP-3626 cannot export file from puppet client via puppetdb to another puppet client Change By: Christopher Price Component/s: PuppetServer Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Christopher Price commented on PUP-3675 Re: generate function calls in templates fail because of permission problem accessing /root What are you running on the server? Puppet Master via webrick or Passenger? Or are you running the new Puppet Server, and if so, what version? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3675 generate function calls in templates fail because of permission problem accessing /root Change By: Henrik Lindberg Assignee: JonathanStanton Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3679) Drop service dependency on the 'ps' fact
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3679 Drop service dependency on the 'ps' fact Issue Type: Improvement Assignee: Unassigned Created: 2014/11/17 5:04 PM Priority: Normal Reporter: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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
Jira (PUP-3679) Drop service dependency on the 'ps' fact
Title: Message Title Kylo Ginsberg commented on PUP-3679 Re: Drop service dependency on the 'ps' fact There's some discussion re motivation in CFACT-151. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3679) Drop service dependency on the 'ps' fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3679 Drop service dependency on the 'ps' fact Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3679) Drop service dependency on the 'ps' fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3679 Drop service dependency on the 'ps' fact Change By: Kylo Ginsberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3511) Refactor Application.run() for external reuse
Title: Message Title Kevin Corcoran commented on PUP-3511 Re: Refactor Application.run() for external reuse Wayne Warren - we can call this resolved. Puppet's CI pipeline is sufficient - no need to wait for Puppet Server's. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Henrik Lindberg commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client Take another look at the documentation for source: https://docs.puppetlabs.com/references/latest/type.html#file-attribute-source Basically you have two resources that should look the same and pull down the same content from the master, but there really is not much meaning in doing it this way (export/collect) since the file will have the same bits as if you use two regular file resources. It is only when the content is specific for one node (say when the content is produced with a template) that it is meaningful to also export it, and import it elsewhere. What you are observing sure looks like an error - if nothing else is should give a better error message, but on the other hand this looks like a somewhat odd use case - but maybe I misunderstood something. To eliminate other problems, try it with simple string content first. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Rob Mattson commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client In the use case I am trying to optimise, the content of the file on the puppet client is a cryptographic identity generated by a process uniqie to the client. The value of the identity(s) are based on an environment which is again unique and it may be exhaustive to forge on the master and stuff down to the client using a local exec/erb on the puppet master. The module I'm working with already executes an scp/ssh session to copy that file to the puppet master. I'm hoping that i can avoid a brain-dead exec running an scp, as I'd rather not incur the ssh key management overhead when there is a perfectly tailored x.509 identity management scheme with a service designed to manage such things (puppet). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Eric Sorenson commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs Yes, setting debug on Puppet ought to invoke facter with debugging enabled. If it didn't, how else would you enable it? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Jonathan Stanton commented on PUP-3675 Re: generate function calls in templates fail because of permission problem accessing /root I am running the puppet master via webrick. This is a development server as I'm testing our code base against Puppet 3.7 with a few agents running currently. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Jonathan Stanton commented on PUP-3675 Re: generate function calls in templates fail because of permission problem accessing /root The exact command I'm running the master with is (as root) : puppet master --confdir=/etc/puppet/master/ --verbose --no-daemonize --debug Once it's running it has transitioned automatically to be running as the puppet user. [root@puppet-dev ~]# ps aux | grep puppet puppet 3578 0.5 1.1 325064 43752 pts/0 Sl+ 22:30 0:01 /usr/bin/ruby /usr/bin/puppet master --confdir=/etc/puppet/master/ --verbose --no-daemonize --debug The puppet software is installed via the puppetlabs repo. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3520) Move the Puppet extension OIDs definitions
Title: Message Title Christopher Price updated an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Nate Wolfe this ticket is missing a story point estimate Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Henrik Lindberg commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client Thanks Rob, that helped explain why you were doing this. Are you trying to avoid having the actual content in the catalog? I am not an expert in this area, see what the folks that no more about the file type and file serving has to say about the best way to do this. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Christopher Price updated an issue Puppet / PUP-3675 generate function calls in templates fail because of permission problem accessing /root Change By: Christopher Price Assignee: JonathanStanton HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3675) generate function calls in templates fail because of permission problem accessing /root
Title: Message Title Christopher Price updated an issue Puppet / PUP-3675 generate function calls in templates fail because of permission problem accessing /root Change By: Christopher Price Component/s: PuppetServer Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Rob Mattson commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client I've no problem with the content of the file being in an appropriately secure location, inaccessible to hosts outside the 'ring of trust'/puppet infrastructure. I believe puppetdb provides this facility. I need the data to get from puppet client to puppet client, where the data originates from a file whose content is not defined in a manifest but the synchronization is. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3642) Remove environment name from URL path
Title: Message Title Christopher Price updated an issue Puppet / PUP-3642 Remove environment name from URL path Change By: Christopher Price Sprint: SERVERnext next candidates Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-84) Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application
Title: Message Title Kylo Ginsberg commented on PUP-84 Re: Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application Agreed. Resolving. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Rob Mattson commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client and, indeed, thankyou for your assistance. if i might match your manual reference: Exported resources allow nodes to share information with each other. This is useful when one node has information that another node needs in order to manage a resource — the node with the information can construct and publish the resource, and the node managing the resource can collect it. https://docs.puppetlabs.com/puppet/latest/reference/lang_exported.html In this case, node 2 constructs and publishes some data and node1 should be able to collect it yes indeed, the construction happens outside puppet (an rpm postinstall clause), however the data replication seems to only operate master(node) node not node node(master) which the above language would imply to me at least. Happy to hear if I'm being unreasonable in my expectations. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-658) facter doesn't parse gnu uptime output
Title: Message Title Kylo Ginsberg commented on FACT-658 Re: facter doesn't parse gnu uptime output After some discussion with Josh Cooper, we agreed that relying on the exact path to uptime for all platforms is the wrong approach, so we're reverting. Two possibilities are: 1) Set the exact path to uptime for Solaris only 2) Make the uptime parsing resilient to gnu uptime output Note that the uptime parser already has a number of different formats it supports, so #2 is probably my preference and would help gnu uptime users on non-Solaris platforms as well. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-658) facter doesn't parse gnu uptime output
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-658 facter doesn't parse gnu uptime output Change By: Kylo Ginsberg Sprint: PlatformClient2014-11-26 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
