Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Jeremy Barlow can you please confirm that what I described above would be sufficient so that we can unblock the language team from estimating the work? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5034) issue in file_line resource
Title: Message Title
Kedar Anwardekar updated an issue
Puppet / PUP-5034
issue in file_line resource
Change By:
Kedar Anwardekar
whenitriedlikethis,file_line{'test2':path=$test::confdir/balancer,line=#testconfig#\n#Includenamesinclusters.,}puppetdoesnotfollowidempotency,andaddstheselineeverytimepuppetagentrun
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5011 Helper methods for enumerating manifest files in environments Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5034) issue in file_line resource
Title: Message Title
Kedar Anwardekar created an issue
Puppet / PUP-5034
issue in file_line resource
Issue Type:
Bug
Assignee:
Kylo Ginsberg
Components:
Catalog Application, Client
Created:
2015/08/12 11:32 PM
Priority:
Minor
Reporter:
Kedar Anwardekar
when i tried like this, file_line { 'test2': path = $kp_params::confdir/balancer, line = # Load balancing clusters config #\n# Include (same) CMS serving MPs in both the clusters., }
puppet does not follow idempotancey, and adds these line every time puppet agent run
Add Comment
Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments FWIW, this is not necessarily what I was expecting that we were going to be asking for in this ticket. In working on the 'classes-per-environment' feature, we ended up merging this code: https://github.com/puppetlabs/puppet-server/blob/13abb5a957cde4280ca120c7b91ec320e9e56d1c/src/ruby/puppet-server-lib/puppet/server/master.rb#L70-L81 Which makes calls to Puppet.settings.clear_environment_settings, and also makes a call to Puppet.lookup(:environments) and holds a long-lived reference to the result of that call, from within Puppet Server's ruby extensions. My gut feeling is that those are low-level implementation methods that are risky for us to depend on as an API contract. I believe that Jeremy Barlow wrote the code that way because he needed a way to get the latest configuration info for a directory environment (parsed from environments.conf), ensuring that the data he retrieved wasn't cached. So, IMO, the minimum requirements for this ticket would actually just be provide some Puppet API to request the latest configuration information for a given environment. I could see us taking it one step further from there and also including some file glob patterns in the result seems like it would be a win. Asking the Puppet ruby code to walk the file system and return a complete list of files to us across language interop boundaries seems excessive and expensive at first glance and I'm not sure that I feel like we actually need to take this that far. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1080 Re: CFacter fails to link (libboost_log vs libboost_log-mt) Peter Huene it's actually still an issue, however I'm working around it by forcing leatherman to link with boost_log: http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/facter/patches/patch-vendor_leatherman_logging_CMakeLists_txt?rev=1.1content-type=text/x-cvsweb-markup Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5035) undefined method `keys' for nil:NilClass in static_compiler
Title: Message Title
Taylan Develioglu created an issue
Puppet / PUP-5035
undefined method `keys' for nil:NilClass in static_compiler
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/08/13 12:55 AM
Priority:
Normal
Reporter:
Taylan Develioglu
get_child_resources() can return nil if the source attribute of the file resource points to a file instead of a directory.
This results in a raised NoMethodError with the static compiler set as the catalog terminus and a file resource declared that has the recurse parameter set to true, e.g.:
file { '/etc/puppet.conf':
recurse = true,
source = 'puppet:///modules/puppet/puppet.conf',
}
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title Pierre Radermecker commented on PUP-1244 Re: Yum provider using version-release to validate installation. Is there a possibility to have a fix in 3.x ? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5034) issue in file_line resource
Title: Message Title
Kedar Anwardekar updated an issue
Puppet / PUP-5034
issue in file_line resource
Change By:
Kedar Anwardekar
whenitriedlikethis,file_line{'test2':path=$ kp_params test ::confdir/balancer,line=# Loadbalancingclusters test config#\n#Include (same)CMSservingMPs names in boththe clusters.,}puppetdoesnotfollow idempotancey idempotency ,andaddstheselineeverytimepuppetagentrun
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1163) Facts for VMware hosts ala EC2 facts
Title: Message Title Gareth Rushgrove created an issue Facter / FACT-1163 Facts for VMware hosts ala EC2 facts Issue Type: Improvement Assignee: Unassigned Created: 2015/08/13 12:51 AM Priority: Normal Reporter: Gareth Rushgrove Interesting conversation on twitter https://twitter.com/cdenneen/status/631647908845236224 I was hoping with the ec2 metadata now as built in facts same would come for @VMware These would be similar to the EC2 facts I would imagine, ie. accessing the vSphere API from the instance and returning details about that same host. Add Comment
Jira (PUP-5034) issue in file_line resource
Title: Message Title Kylo Ginsberg commented on PUP-5034 Re: issue in file_line resource Morgan Haskel: should this be in the modules project? Kedar Anwardekar: can you provide the version of puppet and version of the stdlib module that you're using? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5028) 100% cpu
Title: Message Title Maxim Kozin commented on PUP-5028 Re: 100% cpu We have hardware nodes with libvirt-lxc and LXC containers under puppet. Puppet run on both type servers, but hang only on libvirt-lxc nodes. Yes, we use custom facts which communicate with libvirt and execute some external command Code in attachment. Moreover - backtrace in gdb show that we loop in libvirt code, in poll() on nonexistent fd with timeout = -1: #0 pthread_sigmask (how=how@entry=2, newmask=optimized out, newmask@entry=0x7fff36a73900, oldmask=oldmask@entry=0x0) at ../nptl/sysdeps/pthread/pthread_sigmask.c:53 #1 0x7f185bcc213d in virNetClientIOEventLoop (client=client@entry=0x45c4ea0, thiscall=thiscall@entry=0x3748920) at rpc/virnetclient.c:1518 #2 0x7f185bcc28eb in virNetClientIO (thiscall=0x3748920, client=0x45c4ea0) at rpc/virnetclient.c:1786 #3 virNetClientSendInternal (client=client@entry=0x45c4ea0, msg=msg@entry=0x45c31b0, expectReply=expectReply@entry=true, nonBlock=nonBlock@entry=false) at rpc/virnetclient.c:1958 #4 0x7f185bcc3cf3 in virNetClientSendWithReply (client=client@entry=0x45c4ea0, msg=msg@entry=0x45c31b0) at rpc/virnetclient.c:1986 #5 0x7f185bcc4502 in virNetClientProgramCall (prog=prog@entry=0x45c4e30, client=client@entry=0x45c4ea0, serial=serial@entry=7, proc=proc@entry=2, noutfds=noutfds@entry=0, outfds=outfds@entry=0x0, ninfds=ninfds@entry=0x0, infds=infds@entry=0x0, args_filter=args_filter@entry=0x7f186c795700 __GI_xdr_void, args=args@entry=0x0, ret_filter=ret_filter@entry=0x7f186c795700 __GI_xdr_void, ret=ret@entry=0x0) at rpc/virnetclientprogram.c:329 #6 0x7f185bc9c992 in callFull (priv=priv@entry=0x45c9140, flags=flags@entry=0, fdin=fdin@entry=0x0, fdinlen=fdinlen@entry=0, fdout=fdout@entry=0x0, fdoutlen=fdoutlen@entry=0x0, proc_nr=proc_nr@entry=2, args_filter=0x7f186c795700 _GI_xdr_void, args=args@entry=0x0, ret_filter=0x7f186c795700 _GI_xdr_void, ret=ret@entry=0x0, conn=0x45c9140) at remote/remote_driver.c:6575 #7 0x7f185bcb494c in call (conn=0x45c9140, ret=0x0, ret_filter=optimized out, args=0x0, args_filter=optimized out, proc_nr=2, flags=0, priv=0x45c9140) at remote/remote_driver.c:6597 #8 doRemoteClose (priv=0x45c9140, conn=0x45c4ad0) at remote/remote_driver.c:1228 #9 0x7f185bcb4b7c in remoteConnectClose (conn=0x45c4ad0) at remote/remote_driver.c:1271 #10 0x7f185bc4bd5f in virConnectDispose (obj=0x45c4ad0) at datatypes.c:154 #11 0x7f185bbcb183 in virObjectUnref (anyobj=optimized out) at util/virobject.c:265 #12 0x7f185bc4bca3 in virDomainDispose (obj=0x45c4cf0) at datatypes.c:255 #13 0x7f185bbcb183 in virObjectUnref (anyobj=anyobj@entry=0x45c4cf0) at util/virobject.c:265 #14 0x7f185bc57969 in virDomainFree (domain=0x45c4cf0) at libvirt.c:2272 #15 0x7f1860495419 in domain_free (d=optimized out) at domain.c:95 #16 0x7f186d609191 in run_final (objspace=0x1766940, objspace=0x1766940, obj=63470080) at gc.c:1418 #17 finalize_list (objspace=objspace@entry=0x1766940, p=0x3c87a00) at gc.c:1432 #18 0x7f186d609240 in finalize_deferred (objspace=objspace@entry=0x1766940) at gc.c:1452 #19 0x7f186d60a03e in rb_gc_finalize_deferred () at gc.c:1461 #20 0x7f186d7107a5 in rb_threadptr_execute_interrupts (th=th@entry=0x1766590, blocking_timing=blocking_timing@entry=0) at thread.c:1956 #21 0x7f186d7109ec in rb_threadptr_execute_interrupts (th=th@entry=0x1766590, blocking_timing=blocking_timing@entry=0) at thread.c:1898 #22 0x7f186d6f35e4 in vm_call0_body (th=th@entry=0x1766590, ci=ci@entry=0x7fff36a74120, argv=optimized out) at vm_eval.c:238 #23 0x7f186d6f497b in vm_call0 (defined_class=optimized out, me=0x1857bf0, argv=optimized out, argc=1, id=1408, recv=59393760, th=0x1766590) at vm_eval.c:49 #24 rb_call0 (recv=59393760, mid=1408, argc=1, argv=optimized out, scope=CALL_FCALL, self=24898920) at vm_eval.c:324 #25 0x7f186d63fe21 in
Jira (PUP-5028) 100% cpu
Title: Message Title Maxim Kozin updated an issue Puppet / PUP-5028 100% cpu Custom facts with libvirt-lxc and external commands Change By: Maxim Kozin Attachment: lxc.rb Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4630) auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase
Title: Message Title Brice Figureau commented on PUP-4630 Re: auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase The allow and deny rules are sorted based on their length, if I remember correctly. So longer rules are tested before shorter rules (independently of allow/deny), with the exception of global allow or global deny which short-circuit everything. This is to be able to write something as: ``` allow *.domain.org deny test.domain.org ``` In a top-to-bottom ordering, test.domain.org would always be allowed, but with length rule ordering, it wouldn't. Other systems have a sorting (Apache for instance) where all allow are treated before all deny (or the reverse with the use of a specific directive), but this doesn't allow all cases to be implemented correctly (except allow all this, deny all the others). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5035) undefined method `keys' for nil:NilClass in static_compiler
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5035 undefined method `keys' for nil:NilClass in static_compiler Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Chris Rigby created an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Issue Type:
Bug
Affects Versions:
PUP 3.8.2
Assignee:
Unassigned
Components:
Language
Created:
2015/08/13 8:12 AM
Environment:
CentOS 6.7, Puppet 3.8.2, KVM
Priority:
Normal
Reporter:
Chris Rigby
First noticed after updating to 3.8.2. Compilation will fail with error:
Error: Could not parse for environment production: Syntax error at 'application' at line 1:7 on node build.setup
Investigation concurred that if you have a class named application, and the --parser future options specified, the compilation will fail:
{{[root@build puppet]# puppet apply -e 'class application {}' Notice: Compiled catalog for build.setup in environment production in 0.04 seconds Notice: Finished catalog run in 0.01 seconds [root@build puppet]# puppet apply -e 'class application {}'
Jira (PUP-5036) `--parser future` breaks `class application {}`
Title: Message Title
Chris Rigby updated an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Change By:
Chris Rigby
Firstnoticedafterupdatingto3.8.2.Compilationwillfailwitherror:{{Error:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup}}Investigationconcurredthatifyouhaveaclassnamed{{application}},andthe{{--parserfuture}}optionsspecified,thecompilationwillfail: { { code:java} [root@buildpuppet]#puppetapply-e'classapplication{}'Notice:Compiledcatalogforbuild.setupinenvironmentproductionin0.04secondsNotice:Finishedcatalogrunin0.01seconds[root@buildpuppet]#puppetapply-e'classapplication{}'--parserfutureError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setupError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup {code } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Chris Rigby updated an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Change By:
Chris Rigby
Firstnoticedafterupdatingto3.8.2.Compilationwillfailwitherror:{{Error:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup}}Investigationconcurredthatifyouhaveaclassnamed{{application}},andthe{{--parserfuture}}optionsspecified,thecompilationwillfail:{code :java }[root@buildpuppet]#puppetapply-e'classapplication{}'Notice:Compiledcatalogforbuild.setupinenvironmentproductionin0.04secondsNotice:Finishedcatalogrunin0.01seconds[root@buildpuppet]#puppetapply-e'classapplication{}'--parserfutureError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setupError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup{code} Fixedbyrollingbackto3.8.1:{code}Installed:puppet.noarch0:3.8.1-1.el6Complete![vagrant@gems01puppet]$puppetapply-e'classapplication{}'Notice:Compiledcatalogforgems01.247.otbeach.cominenvironmentproductionin0.01secondsNotice:Finishedcatalogrunin0.02seconds[vagrant@gems01puppet]$puppetapply-e'classapplication{}'--parserfutureNotice:Compiledcatalogforgems01.247.otbeach.cominenvironmentproductionin0.24secondsNotice:Finishedcatalogrunin0.02seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Chris Rigby updated an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Change By:
Chris Rigby
Firstnoticedafterupdatingto3.8.2.Compilationwillfailwitherror:{{Error:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup}}Investigationconcurredthatifyouhaveaclassnamed{{application}},andthe{{--parserfuture}}optionsspecified,thecompilationwillfail:{code}[root@buildpuppet]#puppetapply-e'classapplication{}'Notice:Compiledcatalogforbuild.setupinenvironmentproductionin0.04secondsNotice:Finishedcatalogrunin0.01seconds[root@buildpuppet]#puppetapply-e'classapplication{}'--parserfutureError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setupError:Couldnotparseforenvironmentproduction:Syntaxerrorat'application'atline1:7onnodebuild.setup{code}Fixedbyrollingbackto3.8.1:{code}Installed:puppet.noarch0:3.8.1-1.el6Complete![vagrant@ gems01 build puppet]$puppetapply-e'classapplication{}'Notice:Compiledcatalogfor gems01 build . 247.otbeach.com setup inenvironmentproductionin0.01secondsNotice:Finishedcatalogrunin0.02seconds[vagrant@ gems01 build puppet]$puppetapply-e'classapplication{}'--parserfutureNotice:Compiledcatalogfor gems01 build . 247.otbeach.com setup inenvironmentproductionin0.24secondsNotice:Finishedcatalogrunin0.02seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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
Jira (PUP-4781) filemode retrieved by static_compiler should be stringified
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4781 filemode retrieved by static_compiler should be stringified Change By: Josh Cooper Fix Version/s: PUP4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5018) Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist
Title: Message Title Rob Reynolds commented on PUP-5018 Re: Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist Merged into stable at https://github.com/puppetlabs/puppet/commit/d70c351b0bde0b36aa528ddf7a4129fa34a96a0c Merged into master at https://github.com/puppetlabs/puppet/commit/7a87738f9aaafcfe5171d71820047df418471e76 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1875) Disable fedora 20 test cells
Title: Message Title Melissa Stone commented on PDB-1875 Re: Disable fedora 20 test cells This change brought to you by the letter D Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4952) acceptance test curl fails on sles-10
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4952 acceptance test curl fails on sles-10 Change By: Josh Cooper Release Notes Summary: Changetoanacceptancetesttonotusethesystemcurl+opensslonsles Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Change By:
Henrik Lindberg
Priority:
Normal Major
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Jeremy Barlow commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments In working on the 'classes-per-environment' feature, we ended up merging this code: https://github.com/puppetlabs/puppet-server/blob/13abb5a957cde4280ca120c7b91ec320e9e56d1c/src/ruby/puppet-server-lib/puppet/server/master.rb#L70-L81 Which makes calls to Puppet.settings.clear_environment_settings, and also makes a call to Puppet.lookup(:environments) and holds a long-lived reference to the result of that call, from within Puppet Server's ruby extensions. My gut feeling is that those are low-level implementation methods that are risky for us to depend on as an API contract. I agree with that. I'd also like to not have that in Puppet Server code and instead have the logic behind this new API in core Puppet code do whatever needs to be done to get the latest data for an environment (bypassing settings caching, etc.) when called. So, IMO, the minimum requirements for this ticket would actually just be provide some Puppet API to request the latest configuration information for a given environment. Christopher Price, I'm not quite sure we're aligned on what latest configuration information for a given environment is. I'm thinking you might mean something like provide the full list of paths (post-setting variable interpolation) that an environment would process for its modulepath and manifest settings, assuming that these are the two settings that constrain the full range of files that could be considered. I had been considering the minimal amount of information that comes out of this new API would be everything which would be needed to deduce the full list of manifest files which would need to be parsed per environment. In digging through the source code behind Puppet::Node::Environment, e.g., lines like https://github.com/puppetlabs/puppet/blob/4.2.1/lib/puppet/node/environment.rb#L274, it became clear to me that the way manifest enumeration is done isn't just a simple glob of */.pp under each directory in an environment's modulepath and manifest setting in all cases. I'd really like to have code behind this new API exercise the same logic which core Puppet uses to enumerate the available manifest files in an environment, if possible - including any special rules that would prohibit certain files from being considered based on naming restrictions, etc. If the API were to return back a list of the set of paths with .pp files that need to be parsed at a level of granularity that includes the individual modules, that might satisfy my concern. For example, if the production environment's settings (post-processing for defaults and interpolation) were to be... manifest: /etc/puppetlabs/code/production/manifests modulepath: /etc/puppetlabs/code/modules ..., but bogus-named /etc/puppetlabs/code/modules/my-bad-module and /etc/puppetlabs/code/environment/production/modules/another-bad-module directories (since the - character is illegal) were present, the call to get info for one
Jira (PUP-4329) Filebucket fails to update file resource if checksum doesn't match the configured checksum type
Title: Message Title Michael Smith commented on PUP-4329 Re: Filebucket fails to update file resource if checksum doesn't match the configured checksum type Jeremy Adams I misread your report. Bad Request definitely isn't helpful, and setting the checksum type in puppet.conf (I think they have to match on agent and file bucket host) should work. Your report isn't what this ticket is reporting. I'll take a quick look into it. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Michael Smith commented on PUP-4740 Re: Add missing query parameters to Puppet HTTPS API docs PUP-5032 may affect this, so holding off until a decision is made about changing the behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5036
`--parser future` breaks `class application {}`
Change By:
Henrik Lindberg
Fix Version/s:
PUP3.8.3
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Henrik Lindberg commented on PUP-5036
Re: `--parser future` breaks `class application {}`
The change caused a regression when used as a name of a class.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1127) Too many environment vars on the command line causes overflow
Title: Message Title Rob Reynolds commented on FACT-1127 Re: Too many environment vars on the command line causes overflow Usually there is a reason attached to the won't fix. I'll take a stab at it. Passing environment variable related FACTER variables to facter is kind of a misuse of the intention of overriding the facter variables. We don't want to fix this at this time. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4941) Reserve keywords 'application', 'consumes', and 'produces'
Title: Message Title
Matthaus Owens commented on PUP-4941
Re: Reserve keywords 'application', 'consumes', and 'produces'
on el6, I'm not seeing any warnings generated. I get a syntax error with the future parser, and no change with 3.x parser.
[root@jixh53ns9hrbnpc ~]# puppet apply -e 'class application { notify {$osfamily:}} include application' --parser=future
Error: Could not parse for environment production: Syntax error at 'application' at line 1:7 on node jixh53ns9hrbnpc.delivery.puppetlabs.net
Error: Could not parse for environment production: Syntax error at 'application' at line 1:7 on node jixh53ns9hrbnpc.delivery.puppetlabs.net
and
[root@jixh53ns9hrbnpc ~]# puppet apply -e 'class application { notify {$osfamily:}} include application'
Notice: Compiled catalog for jixh53ns9hrbnpc.delivery.puppetlabs.net in environment production in 0.03 seconds
Notice: RedHat
Notice: /Stage[main]/Application/Notify[RedHat]/message: defined 'message' as 'RedHat'
Jira (PUP-5036) `--parser future` breaks `class application {}`
Title: Message Title
Garrett Guillotte commented on PUP-5036
Re: `--parser future` breaks `class application {}`
application, consumes, and produces are reserved words in the future parser as of 3.8.2, although the notes suggest they should only produce a warning when used.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1828) puppetdb 3.0.2 2015-08-03 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1828 puppetdb 3.0.2 2015-08-03 Release Change By: Wyatt Alt Scope Change Category: Adopted Scope Change Reason: thiswasplannedworkforwhichticketsdidn'texistatplanningtime Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4952) acceptance test curl fails on sles-10
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4952 acceptance test curl fails on sles-10 Change By: Josh Cooper Fix Version/s: PUP4.2.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1912) `puppetlabs-puppetdb` (the PuppetDB module) related tickets
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-1912 `puppetlabs-puppetdb` (the PuppetDB module) related tickets Issue Type: Epic Assignee: Unassigned Created: 2015/08/13 2:49 PM Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1890 URI.unescape mangles UTF-8 paths producing invalid ASCII strings Change By: Owen Rodabaugh CS Priority: NeedsPriority Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1152) facter partitions don't work on Centos 4/5, sles10, fedora
Title: Message Title Michael Smith commented on FACT-1152 Re: facter partitions don't work on Centos 4/5, sles10, fedora Should we add an acceptance test to confirm that partitions is not empty? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title
William Hopper commented on PUP-4929
Re: Acceptance test for packages has dependency on rubygems.org
Michael Smith is this different than doing the following?
GEM_SOURCE=http://rubygems.delivery.puppetlabs.net be rake ci:test:aio SUITE_VERSION=1.2.1.82.g50fe91e SHA=50fe91efa6b06c6d99571f83a2027bd604e44637 CONFIG=config/nodes/fedora-20-x86_64.yaml TESTS=tests/resource/package/common_package_name_in_different_providers.rb
Running it like this already results in the test using GEM_SOURCE:
...
rrgjjshdyyves5l.delivery.puppetlabs.net (agent-2012r2-x86_64-rubyx64) 13:30:00$ env PATH=/opt/puppetlabs/puppet/bin:${PATH} gem source --clear-all
*** Removed specs cache ***
rrgjjshdyyves5l.delivery.puppetlabs.net (agent-2012r2-x86_64-rubyx64) executed in 0.19 seconds
rrgjjshdyyves5l.delivery.puppetlabs.net (agent-2012r2-x86_64-rubyx64) 13:30:01$ env PATH=/opt/puppetlabs/puppet/bin:${PATH} gem source --add
Jira (PUP-5018) Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5018 Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist Change By: Ryan Gard QA Risk Assessment: Medium QA Status: Reviewed QA Contact: RyanGard Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1159) Facter cross-compile fails because Ruby isn't present
Title: Message Title Michael Smith commented on FACT-1159 Re: Facter cross-compile fails because Ruby isn't present Facter in AIO hard-codes the Ruby path, so acceptance testing is tricky. This came up as a result of Matthaus Owens's work cross-compiling for Solaris Sparc, so I think his validation should be sufficient. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5018) Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist
Title: Message Title Rob Reynolds commented on PUP-5018 Re: Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist Passed stable specs https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet/job/platform_aio-puppet_stage-unit_stable/397/ Passed master specs https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet/job/platform_aio-puppet_stage-unit_master/175/ But did not pass acceptance due to newly found beaker issue (JIRA ticket yet to be determined). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Shaigy Nixon commented on FACT-1150 Re: Don't pick scope:link over scope:global IP addresses Validated on sles-10-x86_64: evdmi0pnlt6w4fo:/etc/sysconfig/network # facter --version 3.0.2 (commit 32b5cf62ed2e682f8d0e00d9a59eb7ccf44afdb0) evdmi0pnlt6w4fo:/etc/sysconfig/network # ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:8F:8F:59 inet addr:10.32.121.15 Bcast:10.32.127.255 Mask:255.255.240.0 inet6 addr: 2001:db8:0:f101::1/64 Scope:Global inet6 addr: fe80::250:56ff:fe8f:8f59/64 Scope:Link
Jira (FACT-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Shaigy Nixon assigned an issue to Unassigned Facter / FACT-1150 Don't pick scope:link over scope:global IP addresses Change By: Shaigy Nixon Assignee: ShaigyNixon Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-891) dynamic library support cannot determine first_load on AIX
Title: Message Title Peter Huene commented on FACT-891 Re: dynamic library support cannot determine first_load on AIX Branan Riley and I talked about this two weeks ago. We came to the conclusion that dynamic_library::load should always treat it as first load. The only place that shouldn't treat it as first load should be the dynamic_library::find_by* functions, which Facter already uses to search for MRI symbols. This should fix things for AIX and BSD. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1159) Facter cross-compile fails because Ruby isn't present
Title: Message Title Eric Thompson commented on FACT-1159 Re: Facter cross-compile fails because Ruby isn't present Michael Smith i take it this isn't really tested in CI? should we validate xcompiling with ruby missing? should we ticket creation of a job with ruby-less machines for CI? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4476) Add a 'puppet lookup' command line application as UI to lookup function
Title: Message Title Hailee Kenney commented on PUP-4476 Re: Add a 'puppet lookup' command line application as UI to lookup function Henrik Lindberg which (if any) of the options should be required? And if they're not required what should their default value be? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5036) `--parser future` breaks `class application {}`
Title: Message Title
Peter Huene commented on PUP-5036
Re: `--parser future` breaks `class application {}`
I'd also expect this to output ok without an error or warning:
define foo($application) {
notice $application
}
foo { bar:
application = ok # most keywords should be an acceptable attribute name
}
Instead it errors on application = ok.
Add Comment
Jira (FACT-1155) Failing facter tests on solaris 10 i386
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1155 Failing facter tests on solaris 10 i386 Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-3045) exec resource with timeout doesn't kill executed command that times out
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3045 exec resource with timeout doesn't kill executed command that times out Change By: Geoff Nichols Affects Version/s: PUP3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1152) facter partitions don't work on Centos 4/5, sles10, fedora
Title: Message Title Josh Cooper updated an issue Facter / FACT-1152 facter partitions don't work on Centos 4/5, sles10, fedora Change By: Josh Cooper Fix Version/s: FACT3.0.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5018) Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist
Title: Message Title Ryan Gard updated an issue Puppet / PUP-5018 Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist Change By: Ryan Gard Attachment: console.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1908) Config Managment related tickets
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-1908 Config Managment related tickets Issue Type: Epic Assignee: Unassigned Created: 2015/08/13 12:27 PM Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 (FACT-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Shaigy Nixon assigned an issue to Peter Huene Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Change By: Shaigy Nixon Assignee: ShaigyNixon PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1635) Import/Export Improvements
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1635 Import/Export Improvements Change By: Andrew Roetker Epic Name: Import/Export Improvements /Anonymization Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1909) max-frame-size isn't tunable
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1909 max-frame-size isn't tunable Issue Type: Bug Affects Versions: PDB 2.3.6 Assignee: Unassigned Created: 2015/08/13 1:41 PM Priority: Normal Reporter: Wyatt Alt schema validation is for a string, when it should be an int Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith commented on PUP-4929 Re: Acceptance test for packages has dependency on rubygems.org I guess I should've included the failure. I think it's the gem provider itself, not Beaker's calls to gem, that was hitting rubygems.org. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1744) Querying facts in puppetdb with some invalid regex expressions return invalid results.
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1744 Querying facts in puppetdb with some invalid regex expressions return invalid results. Change By: Andrew Roetker Affects Version/s: PDBmodule-4.3.0 Affects Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1813) Run the state-overview queries as a single query.
Title: Message Title Andrew Roetker commented on PDB-1813 Re: Run the state-overview queries as a single query. This is not a requirement for Scott Walker but we should probably do this anyways (running state-overview in a single query) to eliminate the race condition across multiple queries, or at least run all the queries in the same database transaction. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1908) Config Managment / App Management / external PuppetDB requirements related tickets
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1908 Config Managment / App Management / external PuppetDB requirements related tickets Change By: Andrew Roetker Summary: ConfigManagment /AppManagement/externalPuppetDBrequirements relatedtickets Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1907) Items related to the PuppetDB metrics dashboard
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-1907 Items related to the PuppetDB metrics dashboard Issue Type: Epic Assignee: Unassigned Created: 2015/08/13 12:21 PM Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-5028) 100% cpu
Title: Message Title
Peter Huene commented on PUP-5028
Re: 100% cpu
Ignore my last comment. I was incorrectly looking at the polls in virNetClientSetTLSSession and not virNetClientIOEventLoop where the backtrace is showing the problem lies.
Looking at virNetClientIOEventLoop, a bad descriptor to poll should break it out of the loop:
repoll:
ret = poll(fds, ARRAY_CARDINALITY(fds), timeout);
if (ret 0 (errno == EAGAIN || errno == EINTR))
goto repoll;
ignore_value(pthread_sigmask(SIG_SETMASK, oldmask, NULL));
virObjectLock(client);
if (ret 0) {
Jira (PDB-1864) Smoke test packages
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1864 Smoke test packages Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4941) Reserve keywords 'application', 'consumes', and 'produces'
Title: Message Title
Ryan Whitehurst commented on PUP-4941
Re: Reserve keywords 'application', 'consumes', and 'produces'
I see the same thing as Matthaus Owens on CentOS 7:
bash-4.2$ lsb_release -d
Description:CentOS Linux release 7.0.1406 (Core)
bash-4.2$ puppet --version
3.8.2
bash-4.2$ puppet apply -e 'class application {}'
Notice: Compiled catalog for openstack-controller1-dev in environment production in 0.02 seconds
Notice: Finished catalog run in 0.06 seconds
bash-4.2$ puppet apply --parser future -e 'class application {}'
Jira (PUP-5028) 100% cpu
Title: Message Title
Peter Huene commented on PUP-5028
Re: 100% cpu
Indeed, it looks like libvirt ignores legitimate errors from poll and only checks for needing to poll again.
I suspect this would fix it:
if (ret 0) {
if (errno == EAGAIN || errno == EINTR) {
goto repoll;
}
}
ignore_value(pthread_sigmask(SIG_SETMASK, oldmask, NULL));
if (ret 0) {
goto error;
}
Note that there's two places where poll is called that could enter an infinite loop.
Unfortunately, there's little Puppet or Facter can do to work around this bug, especially if it's occurring during a Ruby GC. This will need to be
