Jira (PUP-10247) Support ruby 2.7
Title: Message Title Hadmut Danisch commented on PUP-10247 Re: Support ruby 2.7 Get that damned thing up and running, or drop out of the production process. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.64152.1589624460022%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Hadmut Danisch commented on PUP-10247 Re: Support ruby 2.7 Is there a timeline about when to expect having puppet work properly with recent linux distributions such as Ubuntu 20.04? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.61081.1589364120023%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Hadmut Danisch commented on PUP-10247 Re: Support ruby 2.7 puppet5 can't install ruby gems (using gem as package provider) under ruby 2.7, since it calls the gem command with options such as --nodoc, which do not exist anymore in gem, and cause the gem command to fail. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.61078.1589364000112%40Atlassian.JIRA.
Jira (PUP-10467) Several incompatibilities between puppet 5 and later ruby libs keep it from running
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-10467 Several incompatibilities between puppet 5 and later ruby libs keep it from running Issue Type: Bug Affects Versions: PUP 5.5.10 Assignee: Unassigned Created: 2020/04/25 10:40 AM Priority: Normal Reporter: Hadmut Danisch Puppet Version: 5.5.10 Puppet Server Version: 5.5.10 OS Name/Version: Ubuntu 20.04 Hi, I just tried to tried to upgrade my puppet server (which was running on Ubuntu 18.04 for two years) to Ubuntu 20.04 which was released on Thursday. Ubuntu comes with puppet 5.5.10, but I don't see the the code lines causing trouble have changed in 5.5.19. Trouble on both the puppet master and client. The master can't deliver certificates it just has created because of: Apr 25 18:45:55 puppet puppet-master[4109]: Server Error: can't modify frozen String: "" Apr 25 18:45:55 puppet puppet-master[4109]: /usr/lib/ruby/vendor_ruby/puppet/network/http/response.rb:14:in `encode!' It tries to modify a frozen value and ruby aborts. Thus, master is not working. The client, in contrast, is working, but issues tons of warning messages, most of the kind /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete some others. So both master and agent seem to be not compatible with recent ruby versions. While it keeps the master from running, the agent mostly works. Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-7435) Add support for snap packages
Title: Message Title Hadmut Danisch updated an issue Puppet / PUP-7435 Add support for snap packages Change By: Hadmut Danisch Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.184760.1491554952000.9773.1577697600683%40Atlassian.JIRA.
Jira (PUP-7435) Add support for snap packages
Title: Message Title Hadmut Danisch commented on PUP-7435 Re: Add support for snap packages Sorry to say that, but that discussion is bigoted nonsense. snap has become an established package source, offering plenty of software, and is beginning to replace several ubuntu packages. Some pieces of important software is available as a snap only. And other software gets newer versions only as a snap. Puppet's denial to support the package format is just rendering puppet into beeing unable to install machines in a clean way. snapd comes with a description of it's REST API at https://github.com/snapcore/snapd/wiki/REST-API , so it should be quite simple to tell snapd to install or uninstall a requested package. Unfortunately and in contrast, I did not find a detailed description about how to implement a package provider for puppet. Strange enough, there's a module for that, https://forge.puppet.com/kemra102/snapd , but not exactly maintained, not yet complete, and based on the command line snap tool, not the REST API. So it should be a small and simple task to implement this for someone familiar with the internals of puppet for this REST API. So if you want puppet to be able to configure today's systems, puppet needs to keep up with today's systems. And if puppet is not able to properly install current systems anymore, than this is not just a feature request anymore. It's a bug, since installation becomes partly impossible (in a clean way without workarounds). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PUP-9715) puppet cert sign lacks hashsum parameter
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-9715 puppet cert sign lacks hashsum parameter Issue Type: Improvement Assignee: Unassigned Components: Networking Created: 2019/05/22 2:22 AM Priority: Normal Reporter: Hadmut Danisch Hi, on puppet master the client's public key needs to be signed with puppet cert sign clientname There's two ways to do it: 1) the interactive way where the sha256 hash sum is shown and a human confirms to have checked this 2) the --assume-yes way to blindly sign a key without verifying. That's insufficent /insecure if clients need to be registered automatically, e.g. with an external script there show be a command like puppet cert sign clientname hashsum or just puppet cert sign hashsum which signs the client only if the hashsum is equal to the one given on command line (e.g. fetched directly from the client) And on the client side there should be some simple command to display the corresponding hash of the cert request, in order to automatically fetch the hash sum from the client and pass it to the master/server to sign that particular hash. regards Add Comment
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Hadmut Danisch commented on PUP-9480 Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts BTW, the host resource seems to be somewhat broken by design, since the leading entity and key in /etc/hosts is the ip address and not the host name. A better way would be to bind host names to ip addresses and not ip addresses to host names. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Issue Type: Improvement Affects Versions: PUP 5.4.0 Assignee: Unassigned Created: 2019/02/07 2:34 AM Priority: Normal Reporter: Hadmut Danisch Hi, an old problem, known at least since 2011, still exists in puppet and is causing more and more trouble: the host resource and put a host into /etc/hosts with either its ipv4 or ipv6 address, but not with both. Since it is state of the art today and normal that machines have both addresses, this really causes headache and problems. I wonder why a problem know for at least 8 years still exists, if https://puppet.com/docs/puppet/5.5/types/host.html is still correct. regards Add Comment
Jira (PUP-8981) exclude parameter for resource type tidy
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-8981
exclude parameter for resource type tidy
Issue Type:
Improvement
Affects Versions:
PUP 5.4.0
Assignee:
Unassigned
Created:
2018/07/04 5:13 AM
Priority:
Normal
Reporter:
Hadmut Danisch
Puppet Version: 5.4.0 ** Hi, I'd be happy if the tidy resource would have an additional parameter (similar to matches) which excludes files from beeing deleted. Reason: I'm using puppet to install several files to machines, where every now and then a new version needs to be installed, e.g. /somedir/datafile-20180503.txt After some time, there's lots of these files occupying and wasting disk space, although only the latest is actually used. Therefore, I need to install the latest file (like /somedir/datafile-20180503.txt ) and remove all older /somedir/datafile-*.txt files. Currently tidy does not allow that, since limits are possible only through age. Would be great if I could use something like {{tidy { '/somedir': }} matches => [ 'datafile-*.txt' ], keep => [ 'datafile-20180503.txt' ]; } or maybe a given count of newest files , e.g. keep => 1 regards Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-8979) failure due to uncontrolled provider= nil
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-8979 failure due to uncontrolled provider= nil Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Components: Server Created: 2018/07/02 8:02 AM Priority: Normal Reporter: Hadmut Danisch Puppet Version: 5.5.2 Puppet Server Version: OS Name/Version: Alpine Linux 3.7 I am trying to run puppet master on Alpine Linux instead of Ubuntu to get a smaller footprint (and smaller virtual machine). When starting puppet master --no-daemonize it aborts with the useless error message: Error: Could not create resources for managing Puppet's files and directories in sections [:main, :master, :ssl, :metrics]: undefined method `exists?' for nil:NilClass Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :master, :ssl, :metrics]: undefined method `exists?' for nil:NilClass undefined method `exists?' for nil:NilClass That "undefined method `exists?' for nil:NilClass" should never occur, since it is a loss of control. To the best I could debug so far this happens in /usr/local/bundle/gems/puppet-5.5.2/lib/puppet/type/user.rb:496 in def exists? provider.exists? end since the variable provider is nil. If I understand this correctly, puppet looks for the useradd command and does not find it, because alpine linux just offers the adduser command and not the useradd command. As far as I understand puppet uses it's own resource classes to create it's directory structure, and that's where it fails, because the user resource cannot determine it's provider. Even if puppet does not want to run under alpine, it should never ever keep running with an uncontrolled nil value and then issue a pointless error message. regards
Jira (FACT-1314) facter generates wrong fqdn
Title: Message Title Hadmut Danisch created an issue Facter / FACT-1314 facter generates wrong fqdn Issue Type: Bug Affects Versions: FACT 2.3.0 Assignee: Unassigned Created: 2016/01/16 9:01 AM Environment: Ubuntu 15.10 Priority: Normal Reporter: Hadmut Danisch This bug is related to PUP-5719 and was part of it, since I found the same problem in puppet and facter. However, I was asked to open a separate bug for facter. Both puppet and facter calculate the fully qualified domain name of the client wrong: They call 'hostname' to determine the machine's name. If it has a domain component, they chop it off, and then they attach the first domain name in the search list in /etc/resolv.conf. This can be wrong, because the machine's domain part is not necessarily the same as the first in the search list (e.g. Network Manager dynamically generates this list). There's no point in first chopping off the correct domain part and attaching the wrong then.
Jira (PUP-5719) puppet and facter generate wrong fqdn
Title: Message Title Hadmut Danisch commented on PUP-5719 Re: puppet and facter generate wrong fqdn > Where does puppet itself calculate the hostname like this? I honestly thought it always asked facter. When generating the client certificate for the first contact with the puppet server. I had put a custom fact into /etc/facter/facts.d to workaround the facter problem, which helped with this problem, but puppet itself still used the wrong name for generating the client name (workaround: configure in /etc/puppet/puppet.conf). Facter version: 2.3.0 (I'll open a new ticket) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5719) puppet and facter generate wrong fqdn
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-5719 puppet and facter generate wrong fqdn Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Client Created: 2016/01/15 5:53 PM Priority: Normal Reporter: Hadmut Danisch Both puppet and facter calculate the fully qualified domain name of the client wrong: They call 'hostname' to determine the machine's name. If it has a domain component, they chop it off, and then they attach the first domain name in the search list in /etc/resolv.conf. This can be wrong, because the machine's domain part is not necessarily the same as the first in the search list (e.g. Network Manager dynamically generates this list). There's no point in first chopping off the correct domain part and attaching the wrong then.
Jira (PUP-4276) different package types share namespace
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-4276 different package types share namespace Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Components: Language Created: 2015/03/20 1:19 PM Priority: Normal Reporter: Hadmut Danisch Hi, I wanted to install both the ubuntu-package mediainfo and the ruby gem mediainfo. This wasn't possible with puppet, since both use the package resource (the latter with provider gem) and thus share the same namespace. Therefore two different resources with the same name can't coexist. Even using a different name or alias runs into an error message that the package already exists.
Jira (FACT-773) inconsistency: missing network
Title: Message Title Hadmut Danisch created an issue Facter / FACT-773 inconsistency: missing network Issue Type: Improvement Affects Versions: FACT 1.7.5 Assignee: Eric Sorenson Created: 2014/12/30 6:02 AM Priority: Normal Reporter: Hadmut Danisch facter reports ipadresses, netmasks and networks. But: it reports ipaddress both for each network adapter and a common one, i.e. ipadress and ipaddress_eth0,... same with netmask but not for network, there's only the ones with network adapters like netmask_eth0 although it is possible to calculate the network from ipadress and mask, it does not make sense to have this inconsistency. and, btw., a regular CIDR notation like 10.0.0.0/16 as an additional info would be nice and make life easier. Add Comment
Jira (PUP-3797) Firewall module blocking machine
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-3797
Firewall module blocking machine
Issue Type:
Bug
Assignee:
Unassigned
Created:
2014/12/30 7:15 AM
Environment:
ubuntu linux 14.04
Priority:
Normal
Reporter:
Hadmut Danisch
Hi,
the firewall module can block a machine completely.
e.g. something like
firewallchain { 'INPUT:filter:IPv4': policy = 'drop', purge = true; }
and
firewall { '010 ssh': proto = tcp, port = 22, action ="" accept; }
then the firewallchain is executed before the firewall resource, because firewall implicitely requires firewall resource. So the chain is purged and set to drop before any rules are applied.
If you are connected to the machine through ssh and use puppet like puppet agent --test or puppet apply...
then the ssh connection is interrupted once the chain is purged and set to drop. But the accept rule is never applied, since puppet waits for printing the line about the firewallchain (or other resource that might be applied meanwhile) which is not possible because of the blocked ssh connection. Thus puppet is waiting forever and the machine is completely blocked. No access if this is a remote server machine.
Jira (PUP-2640) mysql_grant not idempotent
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-2640
mysql_grant not idempotent
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Andy Parker
Components:
Modules
Created:
22/May/14 1:53 PM
Environment:
Ubuntu 14.04 with puppet 3.4.3 and puppet-module-puppetlabs-mysql Version: 2.1.0-2
Priority:
Normal
Reporter:
Hadmut Danisch
I'm using ressources like
mysql_grant { 'blog@192.168.160.%-blog_danisch.de': ensure = 'present', options = ['GRANT'], privileges = ['ALL'], table = 'blog_danisch.de.*', user = 'blog@192.168.160.%', }
which do work well, but do not detect that they already had succeeded before. Everytime I call puppet, I get a
Notice: /Stage[main]/Hadmut::Application::Blogdevelop/Mysql_grant[blog@192.168.160.%-blog_danisch.de]/ensure: created
regards
Jira (PUP-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch commented on an issue Re: wrong dependency: puppet-common uninstallable No. I've made an empty dummy package dmidecode to resolv the dependency on that. It's just that there is no facter 1.7.0 package. Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 19/May/14 1:14 PM Priority: Normal Reporter: Hadmut Danisch Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards Add Comment
Jira (PUP-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch commented on an issue Re: wrong dependency: puppet-common uninstallable In my case Raspbian (Debian on Raspberry Pi) Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch commented on an issue Re: wrong dependency: puppet-common uninstallable No, it's a different problem. CPR-5 is about facter depending on dmidecode, which is not available on non-x86 architectures. This report is about puppet-common depending on a facter version that hasn't been release yet. Different problem. Seems as if you repo is sort of a mess... Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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
Jira (PUP-1890) Wrong encoding type for file
Title: Message Title
Hadmut Danisch commented on an issue
Re: Wrong encoding type for file
Meanwhile I have upgraded all my machine to Ubuntu 14.04. Problem still persists.
Puppet uses /usr/bin/ruby which claims to be ruby 1.9.3p484, although it's a symlink and might point to ruby2.0 on other machines, depending on the way of installation.
Momot___.ttf is attached.
Add Comment
Puppet / PUP-1890
Wrong encoding type for file
Hi, I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2). I am distributing a directory of ttf fonts from the server to the clients, the rule is file{/usr/local/share/fonts/FreeFonts: ensure = directory, mode = 0444, recurse = true, ...
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
Jira (PUP-1890) Wrong encoding type for file
Title: Message Title Hadmut Danisch updated an issue Puppet / PUP-1890 Wrong encoding type for file Change By: Hadmut Danisch Attachment: Momоt___.ttf 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-1890) Wrong encoding type for file
Title: Message Title Hadmut Danisch commented on an issue Re: Wrong encoding type for file Output of puppet agent --test --trace: Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:210:in `sub' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:210:in `get_from_source' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:220:in `chunk_file_from_source' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:191:in `each_chunk_from' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:170:in `block in write' /usr/lib/ruby/vendor_ruby/puppet/util/checksums.rb:51:in `md5_stream' /usr/lib/ruby/vendor_ruby/puppet/type/file/checksum.rb:30:in `sum_stream' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:169:in `write' /usr/lib/ruby/vendor_ruby/puppet/type/file.rb:816:in `write_content' /usr/lib/ruby/vendor_ruby/puppet/type/file.rb:726:in `block in write' /usr/lib/ruby/vendor_ruby/puppet/util.rb:428:in `replace_file' /usr/lib/ruby/vendor_ruby/puppet/type/file.rb:724:in `write' /usr/lib/ruby/vendor_ruby/puppet/type/file/content.rb:150:in `sync' /usr/lib/ruby/vendor_ruby/puppet/type/file/ensure.rb:65:in `block (2 levels) in module:Puppet' /usr/lib/ruby/vendor_ruby/puppet/property.rb:197:in `call_valuemethod' /usr/lib/ruby/vendor_ruby/puppet/property.rb:498:in `set' /usr/lib/ruby/vendor_ruby/puppet/property.rb:581:in `sync' /usr/lib/ruby/vendor_ruby/puppet/type/file/ensure.rb:183:in `sync' /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:191:in `sync' /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:128:in `sync_if_needed' /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:81:in `perform_changes' /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:174:in `apply' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:187:in `eval_resource' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `call' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `block (2 levels) in evaluate' /usr/lib/ruby/vendor_ruby/puppet/util.rb:327:in `block in thinmark' /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' /usr/lib/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `block in evaluate' /usr/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:108:in `evaluate' /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:164:in `block in apply' /usr/lib/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination' /usr/lib/ruby/vendor_ruby/puppet/transaction/report.rb:108:in `as_logging_destination' /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:163:in `apply' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:125:in `block in apply_catalog' /usr/lib/ruby/vendor_ruby/puppet/util.rb:161:in `block in benchmark' /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' /usr/lib/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:124:in `apply_catalog' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:192:in `run' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:44:in `block (4 levels) in run' /usr/lib/ruby/vendor_ruby/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:44:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:114:in `with_client' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:41:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:79:in `run_in_fork' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:40:in `block in run' /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call' /usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run' /usr/lib/ruby/vendor_ruby/puppet/agent.rb:38:in `run'
Jira (PUP-2081) module postgresql lacks parameter
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-2081
module postgresql lacks parameter
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Andy Parker
Components:
Modules
Created:
27/Mar/14 1:33 PM
Priority:
Normal
Reporter:
Hadmut Danisch
Hi,
manifests/params.pp of the postgressmodules contains in the debian case the lines
/manifests/params.pp: $datadir = pick($datadir, /var/lib/postgresql/$ {version}/main) ./manifests/params.pp: $confdir = pick($confdir, /etc/postgresql/${version}
/main)
which uses /main as a fixed server directory.
But sometimes several postgresql instances with different names and parameters are needed. Although it is possible to override the complete $datadir and $confdir variables (which is odd, it should be possible to just pass the name instead of 'main') it is not possible to have multiple class instances with different $datadir settings.
Should be a rather a macro/define than a class and use a parameter for the server name with default value 'main'.
Jira (PUP-1890) Wrong encoding type for file
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-1890
Wrong encoding type for file
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Unassigned
Created:
07/Mar/14 12:53 PM
Priority:
Normal
Reporter:
Hadmut Danisch
Hi,
I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2).
I am distributing a directory of ttf fonts from the server to the clients, the rule is
file {/usr/local/share/fonts/FreeFonts: ensure = directory, mode = 0444, recurse = true, purge = true, source = puppet:///modules/hadmut/soft/Daten/Fonts/Installation/FreeFonts, }
This works with a great number of font files, but fails with one particular font:
Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII Wrapped exception: invalid byte sequence in US-ASCII Error: /Stage[main]/Hadmut::Application::X11_common/File[/usr/local/share/fonts/FreeFonts/Momоt___.ttf]/ensure: change from absent to file failed: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
For some reason Puppet assumes that this is an US-ASCII text file, but it should treat this as a binary.
Jira (FACT-377) Does not detect LXC virtualization
Title: Message Title Hadmut Danisch created an issue Facter / FACT-377 Does not detect LXC virtualization Issue Type: Bug Assignee: Eric Sorenson Created: 07/Mar/14 2:57 PM Environment: Ubuntu 14.04 / Facter 1.7.5 Priority: Normal Reporter: Hadmut Danisch Facter does not detect when run in an LXC virtual environment. It reports is_virtual = false and virtual = physical. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
