Jira (PUP-2783) Puppet cannot restart agent after upgrade to puppet 3.4.3,
Title: Message Title
zeng ling hua created an issue
Puppet / PUP-2783
Puppet cannot restart agent after upgrade to puppet 3.4.3,
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Client
Created:
16/Jun/14 2:31 AM
Environment:
OS: Debian 6/7; FreeBSD 7/8/9 puppet: 3.4.3
Priority:
Major
Reporter:
zeng ling hua
1. Problem: After upgrade to puppet 3.4.3, puppet cannot restart agent.
2. puppet defs: (Eg: test.pp) service { puppet: ensure = running, }
file { 'puppet.conf': ensure = present, path = '/etc/puppet/puppet.conf', owner = 'puppet', group = 'puppet', source = '/tmp/puppet.conf', notify = Service['puppet'], }
3. steps as follows: 1) run puppet apply test.pp. After running, threre is a puppet process in backgroud. 2) append a line # just test to the /tmp/puppet.conf file. 3) run puppet apply test.pp again. After running, there is no puppet process in backgroud. In /var/log/syslog, there are log as: puppet-agent[10932]: Could not run: Address already in use - bind(2)
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title
Kenneth Barber commented on an issue
Re: The first request to PuppetDB after DB backend restart fails
Aaron Armstrong thanks for letting me know, Its still in the next spring and I'll make sure I bring up the requirement in next planning.
Add Comment
PuppetDB / PDB-707
The first request to PuppetDB after DB backend restart fails
The first request sent to PuppetDB after its backend DB has been restarted fails. Any subsequent requests are processed normally. h6. Steps to reproduce {code} service pe-postgresql restart curl -i --cacert /opt/puppet/share/puppet-dashboard/certs/pe-internal-dashboard.ca_cert.pem --cert /opt/puppet/share/puppet-dashboard/certs/pe-internal-dashboard...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PDB-337) _timestamp fact
Title: Message Title
Kenneth Barber commented on an issue
Re: _timestamp fact
Daniele Sluijters we would but we're so busy atm ... is anyone bleeding from this problem yet?
BTW - this bug is just in the Ruby terminus code, if you were desperate feel free to raise a patch, I don't presume this is a difficult one to solve.
Add Comment
PuppetDB / PDB-337
_timestamp fact
There appears to be an extra fact called {{_timestamp}} which is being stored for every node but it doesn't come from Facter. It appears that this timestamp denotes when Facts were uploaded by the agent through the master in PuppetDB. Though it's completely innocuous it's not correct for it to show up there.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PDB-337) _timestamp fact
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-337 _timestamp fact Change By: Kenneth Barber Labels: puppetdb trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title
Henrik Lindberg commented on an issue
Re: Add optional type to parameters
For functional reivew:
Parameters in lambdas, defines, classes can now be typed
EPP template parameters can be typed
Untyped parameters accepts anything
Lambdas accepts varargs/captures-rest when last param has splat (e.g. *$param) (the rest of the parameters must comply with given type and are delivered in an Array.
Defines, Classes, and EPP does not accept varargs/captures-rest parameter.
TIP: The new function with accepts any arguments and passes them on to a given lambda and is good for testing lambdas (among other things).
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x,
Jira (PUP-2756) Fix faulty acceptance test for future parser
Title: Message Title Henrik Lindberg commented on an issue Re: Fix faulty acceptance test for future parser Not much to review here... Add Comment Puppet / PUP-2756 Fix faulty acceptance test for future parser This test: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/apply/conditionals/should_evaluate_undef.rb Is faulty for future parser since undef is no longer equal to an empty string. This blocks getting a clean acceptance test run. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-121) Remove relative namespacing
Title: Message Title Henrik Lindberg commented on an issue Re: Remove relative namespacing For functional review: Look at the file spec/integration/parser/future_compiler_spec.rb and when resolving class references, for the general nature of this change. (i.e.. all references are now absolute). Add Comment Puppet / PUP-121 Remove relative namespacing This is the issue where `include apache` actually means “try to declare class `current namespace::apache`, class `parent of current namespace::apache`, and so on, eventually declaring `apache` as a last resort. This bites people in the wild frequently, and seem to be getting a steady stream of customer complaints about it. We seem to have nea... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-121) Remove relative namespacing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-121 Remove relative namespacing Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title
John Bollinger commented on an issue
Re: Exec checks should be turned into metaparameters
Felix Frank wrote:
My reasoning was that a Fact bases solution will likely remove resources conditionally
if $::my_custom_fact { package { foo: } }
so that such resources cannot be safely required by others. If I understand you correctly, your point is that the require value can depend on the fact value as well. That is true, albeit unwieldy.
My point is twofold:
yes, the require value and/or the entire dependent resource can be guarded by the fact as well, but also
in cases where there are dependencies to worry about, they usually need to be guarded that way.
Consider, for example, a standard package / configuration / service module, where the user wants to accommodate an alternative service instead of the standard one (maybe apache on one hand and nginx on the other). You need to either enable or disable the whole chain together – if nginx is already installed, say, it is not sufficient to avoid managing only Package['httpd'].
On the other hand, if you have a dependency between two resources where the second can tolerate the first being unsynced, then that dependency is either inaccurately modeled or unneeded altogether. The innaccurately modeled end is one place defined alternatives could help, for without something like them, some of those cases simply cannot be modeled well.
From a design perspective, it would be consistent to make it possible for the user to require such conditional resources and sync the dependent resources even if the condition of the dependency are not met.
Yes, there is room for users to shoot themselves in the foot.
So I do see potential in such a dangerous feature, at least as a design study. Of course, if we add this at any point in time, getting rid of it again would be quite painful (a Puppet 5 kind of retraction).
You are right: it could be implemented that way, and careful puppeteers could put it to use without shooting themselves in the foot much. It might be an interesting experiment if it could be done in a provisional way, maybe like the future parser has been.
Nevertheless, there are alternative ways to approach the issues that would channel users in more effective directions, that would avoid opening new avenues for module incompatibility, and that would put lower demands on support channels, at least in the long run. But maybe I'm peddling betamaxes.
So a much less dangerous compromise could be to forego the onlyif/unless equivalents for now and only go
Jira (PUP-121) Remove relative namespacing
Title: Message Title Kurt Wall updated an issue Puppet / PUP-121 Remove relative namespacing Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-234 Add Facts showing the UUID of partitions Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Kurt Wall commented on an issue Re: Add Facts showing the UUID of partitions Does not show a partition or block device fact on OS X on facter-2 (SHA=22b6b46673f092841773745110b7cb24a2e8f7e7): breve:facter root# bundle exec facter Unable to add resolve nil for fact productname: You must pass either code or a block Facter::Util::EC2.has_euca_mac? is deprecated; see the Facter::EC2 classes instead Facter::Util::EC2.has_openstack_mac? is deprecated; see the Facter::EC2 classes instead Facter::Util::EC2.has_ec2_arp? is deprecated; see the Facter::EC2 classes instead Unable to add resolve nil for fact productname: You must pass either code or a block architecture = x86_64 domain = wifi.puppetlabs.net facterversion = 2.0.2 fqdn = breve.wifi.puppetlabs.net hardwareisa = i386 hardwaremodel = x86_64 hostname = breve id = root interfaces = lo0,gif0,stf0,en0,fw0,en3,en4,en2,bridge0,p2p0,vmnet1,vmnet8 ipaddress = 10.16.141.15 ipaddress_en0 = 10.16.141.15 ipaddress_lo0 = 127.0.0.1 ipaddress_vmnet1 = 192.168.30.1 ipaddress_vmnet8 = 172.16.205.1 is_virtual = false kernel = Darwin kernelmajversion = 13.2 kernelrelease = 13.2.0 kernelversion = 13.2.0 macaddress = c8:e0:eb:14:69:b1 macaddress_bridge0 = ca:e0:eb:41:27:00 macaddress_en0 = c8:e0:eb:14:69:b1 macaddress_en2 = 10:dd:b1:d3:d3:55 macaddress_en3 = 32:00:19:d3:94:60 macaddress_en4 = 32:00:19:d3:94:61 macaddress_fw0 = 00:0a:27:02:00:52 macaddress_p2p0 = 0a:e0:eb:14:69:b1 macaddress_vmnet1 = 00:50:56:c0:00:01 macaddress_vmnet8 = 00:50:56:c0:00:08 macosx_buildversion = 13D65 macosx_productname = Mac OS X macosx_productversion = 10.9.3 macosx_productversion_major = 10.9 macosx_productversion_minor = 3 memoryfree = 9.31 GB memoryfree_mb = 9534.03 memorysize = 0.00 MB memorysize_mb = 0.00 mtu_bridge0 = 1500 mtu_en0 = 1500 mtu_en2 = 1500 mtu_en3 = 1500 mtu_en4 = 1500 mtu_fw0 = 4078 mtu_gif0 = 1280 mtu_lo0 = 16384 mtu_p2p0 = 2304 mtu_stf0 = 1280 mtu_vmnet1 = 1500 mtu_vmnet8 = 1500 netmask = 255.255.252.0 netmask_en0 = 255.255.252.0 netmask_lo0 = 255.0.0.0 netmask_vmnet1 = 255.255.255.0 netmask_vmnet8 = 255.255.255.0 network_en0 = 10.16.140.0 network_lo0 = 127.0.0.0 network_vmnet1 = 192.168.30.0 network_vmnet8 = 172.16.205.0 operatingsystem = Darwin operatingsystemrelease = 13.2.0 osfamily = Darwin path = /private/var/root/facter/.bundle/gems/ruby/2.0.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/local/MacGPG2/bin:/opt/crossfader/bin:/opt/crossfader/versions/ruby/1.9.3-p448/gemsets/crossfader/ruby/1.9.1/bin:/opt/crossfader/versions/ruby/1.9.3-p448/gemsets/global/ruby/1.9.1/bin:/opt/crossfader/versions/ruby/1.9.3-p448/bin:/Users/kwall/bin processorcount = 8 ps = ps auxwww puppetversion = 3.6.2 rubysitedir = /Library/Ruby/Site/2.0.0 rubyversion = 2.0.0 sp_boot_mode = normal_boot sp_boot_rom_version = MBP101.00EE.B03 sp_boot_volume = Macintosh HD sp_cpu_type = Intel Core i7 sp_current_processor_speed = 2.7 GHz sp_kernel_version = Darwin 13.2.0 sp_l2_cache_core = 256 KB sp_l3_cache = 6 MB sp_local_host_name = breve sp_machine_model = MacBookPro10,1 sp_machine_name = MacBook Pro sp_number_processors = 4 sp_os_version = OS X 10.9.3 (13D65) sp_packages = 1 sp_physical_memory = 16 GB sp_platform_uuid = ADEECF00-F1A3-563A-86B4-D8679D2F9969 sp_secure_vm = secure_vm_enabled sp_serial_number = C02L57Z7FFT1 sp_smc_version_system = 2.3f36 sp_uptime = up 4:16:51:33 sp_user_name = System Administrator (root) sshdsakey =
Jira (PUP-2758) Implement Rake Benchmark task that runs a series of micro benchmarks
Title: Message Title Henrik Lindberg commented on an issue Re: Implement Rake Benchmark task that runs a series of micro benchmarks PUP-2755 fixes 4x calls by looking up the loaders via the compiler instead of via the context. This is needed when running the benchmarks (or they need a more complex setup). Add Comment Puppet / PUP-2758 Implement Rake Benchmark task that runs a series of micro benchmarks As part of the performance work we need to benchmark a series of specific language parsing/evaluation features. Writing one benchmark for each such micro benchmark will hog the lists of benchmarks. Instead we want one benchmark that consists of a set of named benchmarks. When run without options, it runs all of them, and reports the aggeregate time (possi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Adrien Thebo commented on an issue Re: Add Facts showing the UUID of partitions Kurt Wall the facts are only available on Linux, so this is expected. Add Comment Facter / FACT-234 Add Facts showing the UUID of partitions Add facts 'blockdevice_dev_uuid' that show the partitions UUID. It ignores swap and iso9660 (CD/DVD devices). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby Change By: Josh Cooper Summary: Createruby2.0 branches branch forx64inpuppet-win32-ruby Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2514) Remove support to search for Type in String
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2514 Remove support to search for Type in String Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2514) Remove support to search for Type in String
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2514 Remove support to search for Type in String Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-2700 Puppet 3.6.1 File recurse improperly handles spaces in filenames Change By: Andy Parker Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1807) Empty string should not equal undef
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1807 Empty string should not equal undef Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Facter / FACT-197 processorcount counting CPU cores on Solaris Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1807) Empty string should not equal undef
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-1807 Empty string should not equal undef Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1807) Empty string should not equal undef
Title: Message Title
Kurt Wall commented on an issue
Re: Empty string should not equal undef
Verified in SHA=05dfc157fd8e36f5cd87868d6ad56c18cfc9a0b3. An empty string is not equal to undef:
notice == undef
notice '' == undef
notice undef == undef
$x = undef
notice == $x
notice '' == $x
notice $x == $x
notice in $x
notice '' in $x
notice $x in $x
notice undef in $x
# bundle exec puppet apply --parser future pup-1807.pp
Notice: false
Notice: false
Notice: true
Notice: false
Notice: false
Notice: true
Notice: false
Notice: false
Notice: false
Notice: false
Add Comment
Puppet / PUP-1807
Empty string should not equal undef
Currently {{ == undef}}, which is insane. They should not be equal. Only {{undef}} should equal {{undef}}.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-568 Run specs against windows ruby 2.0 x64 Change By: Josh Cooper Assignee: EricSorenson JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper created an issue Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Issue Type: Bug Assignee: Unassigned Created: 16/Jun/14 10:58 AM Fix Versions: 3.7.0 Labels: windows Priority: Normal Reporter: Josh Cooper Add a cell to the Puppet-Specs-Windows-master job to test puppet specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. Add Comment
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper created an issue Facter / FACT-568 Run specs against windows ruby 2.0 x64 Issue Type: Bug Assignee: Eric Sorenson Created: 16/Jun/14 10:56 AM Fix Versions: 2.1 Priority: Normal Reporter: Josh Cooper Add a cell to the Facter-Specs-Windows-master job to test facter specs against ruby 2.0 x64. Due to https://tickets.puppetlabs.com/browse/QENG-785, you will need to look at the job log, and verify that the specs actually pass. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer
Title: Message Title Ethan Brown assigned an issue to Rob Reynolds Puppet / PUP-2738 Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer Change By: Ethan Brown Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-569) Update git setup steps to install architecture specific version of ruby
Title: Message Title Josh Cooper created an issue Facter / FACT-569 Update git setup steps to install architecture specific version of ruby Issue Type: Task Assignee: Eric Sorenson Created: 16/Jun/14 11:25 AM Labels: windows Priority: Normal Reporter: Josh Cooper Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's install_from_git method accepts a :rev parameter so it should be possible to specify the revision to checkout, e.g. 2.0.0-x64. Add Comment
Jira (PUP-2785) Error Max Connections (30) reached - try again later whiile trying rsync yum.puppetlabs.com::packages/yum/el
Title: Message Title Nathanel Sulimanov created an issue Puppet / PUP-2785 Error Max Connections (30) reached - try again later whiile trying rsync yum.puppetlabs.com::packages/yum/el Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Components: Trivial Created: 16/Jun/14 11:29 AM Environment: Linux CentOS 6.5 Priority: Major Reporter: Nathanel Sulimanov [root@mirror1ext puppet]# rsync -avSHP --stats --copy-links --exclude 5* --exclude 7* --exclude SRPMS --exclude sources --exclude apt --exclude apt-enterprise yum.puppetlabs.com::packages/yum/el . @ERROR: max connections (30) reached – try again later rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Josh Cooper Summary: Updategitsetupstepstoinstallarchitecturespecificversionof RunFacteracceptanceagainst ruby 2.0x64 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Summary: Updategitsetupstepstoinstallarchitecturespecificversionof RunPuppetacceptanceagainst ruby 2.0x64 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker updated an issue Puppet / PUP-2755 Move iterative functions to 4x function API Justin Holguin, I think this change has a pretty significant documentation implication. The new function API doesn't tie into the existing puppet doc functionality and so the iterative functions will disappear from the reference docs. That isn't a desirable outcome and so I think we should come up with something to handle this. Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Josh Cooper Summary: Express SupportBundlerworkflowon x64 windowsgemdependencies Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-567) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-567 Support Bundler workflow on x64 Change By: Josh Cooper Summary: Express SupportBundlerworkflowon x64 windowsgemdependencies Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run specs against windows ruby 2.0 x64 Change By: Josh Cooper Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Josh Cooper Summary: Express SupportBundlerworkflowon x64 windowsgemdependencies Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Change By: Kurt Wall Attachment: pup-2426.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Kurt Wall commented on an issue Re: Puppet's v2 environment listing does not display config_version and environment_timeout as well. I could be doing something wrong, but I don't get config_version and environment_timeout from a browser (SHA=05dfc157fd8e36f5cd87868d6ad56c18cfc9a0b3): # bundle exec puppet config print modulepath manifest config_version environment_timeout --environment jenny modulepath = /etc/puppet/environments/jenny/modules manifest = /etc/puppet/environments/jenny/manifests config_version = /etc/puppet/environments/jenny/ver.sh environment_timeout = 42 # bundle exec puppet config print modulepath manifest config_version environment_timeout --environment production modulepath = /etc/puppet/environments/production/modules manifest = /etc/puppet/environments/production/manifests config_version = /etc/puppet/environments/production/3.1416 environment_timeout = 18 When I point a browser at https://master/v2.0/environments, the output is that show in the attached image ( Add Comment Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. We added config_version and environment_timeout settings to directory environment environment.conf. Puppet's v2 environments listing needs to show these environment parameters as well. (lib/puppet/network/http/api/v2/environments.rb) Will also need to update the API docs for v2.0/environments
Jira (FACT-179) fqdn Fact returns nil when hostname or domain are nil
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Facter / FACT-179 fqdn Fact returns nil when hostname or domain are nil Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Andy Parker updated an issue Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs Change By: Andy Parker Sprint: Week2014-6-11to2014-6-18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1057) Remove 'collect' and 'select' iterative function stubs
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1057 Remove 'collect' and 'select' iterative function stubs Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2566) Debian puppet packages set templatedir which triggers deprecation warning
Title: Message Title
Michael Stahnke commented on an issue
Re: Debian puppet packages set templatedir which triggers deprecation warning
We could fix this so that new installations don't have this setting.
Add Comment
Puppet / PUP-2566
Debian puppet packages set templatedir which triggers deprecation warning
If you install puppet from a package, it sets {{templatedir}}: {noformat} [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates {noformat} This causes a deprecation warning every time you run puppet: {noformat} root@ubuntu1310:/var...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2622) Exit code 0 on wrong command
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2622 Exit code 0 on wrong command Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-234 Add Facts showing the UUID of partitions Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1069) Implement feature :upgradeable for OpenBSD package provider
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-1069 Implement feature :upgradeable for OpenBSD package provider Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2622) Exit code 0 on wrong command
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2622 Exit code 0 on wrong command Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014-7-2to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Josh Cooper Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-273) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Hiera / HI-273 Support Bundler workflow on x64 Change By: Josh Cooper Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-568) Run specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-568 Run specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014-6- 25 18 to2014- 7 6 - 2 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014- 7 6 - 2 18 to2014- 7 6 - 9 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1283) Update win32-service gem
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1283 Update win32-service gem Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Josh Cooper Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1760) Update win32-security gem to latest (after string_to_sid fix)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1760 Update win32-security gem to latest (after string_to_sid fix) Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency Change By: Josh Cooper Sprint: Week2014-7-2to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Josh Cooper Story Points: 8 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Josh Cooper Sprint: Week2014-6-25to2014-7-2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency Change By: Josh Cooper Sprint: Week2014- 7 6 - 2 18 to2014- 7 6 - 9 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg commented on an issue Re: Move iterative functions to 4x function API Ironically, we wanted to keep them out of the reference documentation for 3x (since they are experimental), but never got around to doing so... For 4x they should naturally be included. Add Comment Puppet / PUP-2755 Move iterative functions to 4x function API The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker commented on an issue Re: Move iterative functions to 4x function API As an interim solution we'll just put some stub functions in place under the old API so that we still get the documentation. The new functions will take precedence and so shouldn't affect the running of manifests, but will allow the functions to show up in documentation. Add Comment Puppet / PUP-2755 Move iterative functions to 4x function API The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2755 Move iterative functions to 4x function API Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2183) Octal and hexadecimal numbers are not documented
Title: Message Title Andy Parker assigned an issue to Nicholas Fagerlund I just came across this. In puppet 4, it is pretty significant that users understand this since the new parser will treat literal numbers as numbers. Puppet / PUP-2183 Octal and hexadecimal numbers are not documented Change By: Andy Parker Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Andy Parker updated an issue Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Andy Parker Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Andy Parker updated an issue Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2454 User ID's below 1000, not 500, are generally considered system users on OpenBSD Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1075) Allow custom macro definitions in Nagios types
Title: Message Title Andy Parker updated an issue Puppet / PUP-1075 Allow custom macro definitions in Nagios types Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1181) Modulefile dependency should support git repo as source
Title: Message Title Andy Parker updated an issue Puppet / PUP-1181 Modulefile dependency should support git repo as source Change By: Andy Parker Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1181) Modulefile dependency should support git repo as source
Title: Message Title Andy Parker assigned an issue to Pieter van de Bruggen Puppet / PUP-1181 Modulefile dependency should support git repo as source Change By: Andy Parker Assignee: PietervandeBruggen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1543) agent as nonroot: incorrect messaging when attempting to create unauthorized crons
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-1543 agent as nonroot: incorrect messaging when attempting to create unauthorized crons Change By: Andy Parker Assignee: AndyParker KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1543) agent as nonroot: incorrect messaging when attempting to create unauthorized crons
Title: Message Title Andy Parker updated an issue Puppet / PUP-1543 agent as nonroot: incorrect messaging when attempting to create unauthorized crons Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2381) Tags should issue an error when they are invalid
Title: Message Title Andy Parker updated an issue Puppet / PUP-2381 Tags should issue an error when they are invalid Change By: Andy Parker Fix Version/s: future Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1053) Resource defaults and automatic tags are applied after collectors are evaluated
Title: Message Title Andy Parker updated an issue Puppet / PUP-1053 Resource defaults and automatic tags are applied after collectors are evaluated Change By: Andy Parker Fix Version/s: future Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1053) Resource defaults and automatic tags are applied after collectors are evaluated
Title: Message Title Andy Parker updated an issue Puppet / PUP-1053 Resource defaults and automatic tags are applied after collectors are evaluated Change By: Andy Parker Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2381) Tags should issue an error when they are invalid
Title: Message Title Andy Parker updated an issue Puppet / PUP-2381 Tags should issue an error when they are invalid Change By: Andy Parker Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2616) 'json' gem not available on mountain lion
Title: Message Title Andy Parker updated an issue Puppet / PUP-2616 'json' gem not available on mountain lion Change By: Andy Parker Component/s: RE Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2616) 'json' gem not available on mountain lion
Title: Message Title
Andy Parker commented on an issue
Re: 'json' gem not available on mountain lion
Melissa Stone, what can we do here? For windows we produce an all in one install, but for OS X there are just the individual dmg files.
Add Comment
Puppet / PUP-2616
'json' gem not available on mountain lion
Unlike Lion or Mavericks, Mountain Lion appears not to include the 'json' gem: {code} [r...@talos-mtnlion-r5-006.test.releng.scl3.mozilla.com ~]# irb require 'json' LoadError: no such file to load -- json from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2616) 'json' gem not available on mountain lion
Title: Message Title Andy Parker assigned an issue to Melissa Stone Puppet / PUP-2616 'json' gem not available on mountain lion Change By: Andy Parker Assignee: MelissaStone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2786) `puppet cert list ca` returns an error on a working puppet installation
Title: Message Title Nick Walker created an issue Puppet / PUP-2786 `puppet cert list ca` returns an error on a working puppet installation Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 16/Jun/14 3:48 PM Labels: support Priority: Normal Reporter: Nick Walker PE 2.8.3 [root@master283-centos ~]# puppet --version 2.7.23 (Puppet Enterprise 2.8.3) [root@master283-centos ~]# puppet cert list ca err: Could not call list: undefined method `subject_alt_names' for nil:NilClass undefined method `subject_alt_names' for nil:NilClass PE3.2 [root@master323-centos ~]# puppet --version 3.4.3 (Puppet Enterprise 3.2.3) [root@master323-centos ~]# puppet cert list ca --trace Error: undefined method `subject_alt_names' for nil:NilClass /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/ssl/certificate_authority/interface.rb:105:in `format_host' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/ssl/certificate_authority/interface.rb:92:in `block (2 levels) in list'
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper created an issue Facter / FACT-570 Remove windows-pr as a Windows gem dependency Issue Type: Task Assignee: Eric Sorenson Created: 16/Jun/14 3:46 PM Labels: windows Priority: Normal Reporter: Josh Cooper Facter uses the windows-pr gem, and its win32-api dependency, when determining if facter is running as root or not. We need to eliminate usages of this gem now that everything is ffi'ed. The code that needs to be replaced is already in puppet, and just needs to be copied over. Add Comment
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper updated an issue Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper updated an issue Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Sprint: Week2014-6-18to2014-6-25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-392 Validate win32 gems on x64 Change By: Josh Cooper Sprint: Week2014-6- 11 18 to2014-6- 18 25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper updated an issue Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Sprint: Week2014-6- 18 11 to2014-6- 25 18 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Andy Parker assigned an issue to Anthony Ryan Anthony Ryan, thanks for letting us know about this. This isn't really a use case that we try to support, but I don't think there is anything that we did to specifically prevent it. Could you provide as much detail as possible to cover: What you are trying to do including the changes to the package.rb file that you are making. How this used to work. I suppose that it just worked', but knowing any corner cases you were already aware of would be good. What is now happening. For this, please include any --debug and --trace output that you can. Also, including any extra information about variations and how it behaves is really useful. Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Change By: Andy Parker Assignee: AnthonyRyan Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-570 Remove windows-pr as a Windows gem dependency Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Joshua Partlow commented on an issue Re: Puppet's v2 environment listing does not display config_version and environment_timeout as well. Kurt Wall I see environment_timeout and config_version from that sha, both from a curl and in the browser (if I open my .puppet/auth.conf). What do you have environmentpath set to? Add Comment Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. We added config_version and environment_timeout settings to directory environment environment.conf. Puppet's v2 environments listing needs to show these environment parameters as well. (lib/puppet/network/http/api/v2/environments.rb) Will also need to update the API docs for v2.0/environments This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2423) Filebucket server should warn, not fail, if checksum type is not supported
Title: Message Title
Adrien Thebo commented on an issue
Re: Filebucket server should warn, not fail, if checksum type is not supported
There are multiple touchpoints for how a Puppet master and agent when they have differing digest_algorithms. The first is how file resources back up to a remote filebucket, and the second is how Puppet enforces the state of a resource with a `puppet:///` source.
To begin to address this issue I added a `disallowed_digest_algorithms` setting which takes a list of algorithms that cannot be used when interacting with the file bucket and metadata file server. By default this setting is empty which means that both md5 and sha256 algorithms will work out of the box. The following issues only come up when `disallowed_digest_algorithms` includes the digest_algorithm on a given agent.
The first case with backup up files to a remote filebucket is complicated because the filebucket client queries the master to determine if the file has already been backed up (https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/file_bucket/dipper.rb#L48) which was added as part of #5838 (http://projects.puppetlabs.com/issues/5838). When a request is made to the file bucket using a disallowed algorithm that request cannot be answered, but we cannot just out and out fail a HEAD request. HEAD requests cannot return with a body so if a HEAD request fails we cannot return an error message in the body, so when we query the filebucket for a file with an invalid digest algorithm we can only return this message from the server:
Error: Could not back up /tmp/local-bucketed-file: Error 400 on SERVER: Bad Request
Error: Could not back up /tmp/local-bucketed-file: Error 400 on SERVER: Bad Request
Error: /Stage[main]/Main/Node[default]/File[/tmp/local-bucketed-file]/content: change from {md5}dbeefb7ce205108d148794995023388f to {md5}00e4e9a0343ccd13d68af97ba3e955f1 failed: Could not back up /tmp/local-bucketed-file: Error 400 on SERVER: Bad Request
Because we can only return this non-specific error, we cannot determine if an invalid digest was used, or if a valid digest algorithm was used but the associated checksum did not match the expected format (https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/indirector/file_bucket_file/file.rb#L109). As it stands we cannot indicate a specific error when responding to a HEAD request; we could modify the indirector to allow for richer semantics when raising errors from a terminus back into the v1 API, or expose the response object to a terminus but these are both nontrivial changes.
Given that we cannot respond to the actual request, and we can't fail hard, we have two ways to respond - we can always return false, or we can always return true.
If we always return false then we can fail gracefully when the client does a GET or POST, since those can return an error message on the body. Unfortunately if we take this approach, every time a POST is submitted the entire file will have to be uploaded before we can fail. The backup attempt will be run every time the agent runs on the given node, which means that we'll chew up bandwidth while there's a mismatch between server and agent. This problem is mitigated because only files that are changed will be uploaded to the filebucket, and resources that are in sync or created will not have to interact with the filebucket.
If we always return true we bypass all concerns about
Jira (FACT-567) Support Bundler workflow on x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Failed ruby 187 in travis Facter / FACT-567 Support Bundler workflow on x64 Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-231) Hiera's recursion breaks if a backend returns nil
Title: Message Title Eric Timmerman assigned an issue to Eric Timmerman Hiera / HI-231 Hiera's recursion breaks if a backend returns nil Change By: Eric Timmerman Assignee: EricTimmerman Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecate and remove node inheritance Merged to master: 9910fb9 Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2787) Rename Object to Any
Title: Message Title Andy Parker created an issue Puppet / PUP-2787 Rename Object to Any Issue Type: Task Assignee: Andy Parker Components: DSL Created: 16/Jun/14 5:18 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Andy Parker Object has, over time, become the top type of the puppet language's type system. However, Object has too many connections to the word class that we fear that using it will cause some confusion in what is already a confusing system. Calling the top type Any would avoid all of this, be a shorter word, and actually be more naturally indicative as to what it is. Add Comment
