Jira (PUP-3368) nagios_contact no longer is able to parse utf-8 from nagios config files
Title: Message Title Matthias Saou commented on PUP-3368 Re: nagios_contact no longer is able to parse utf-8 from nagios config files I have the exact same problem on a RHEL6 client node (nagios server). Previously working environment : Puppet master : RHEL6 with puppet-3.7.5 and ruby-1.8.7.374, puppetserver-1.0.8. Client node : RHEL6 with puppet-3.7.5 and ruby-1.8.7.374. New non-working environment : Puppet master : RHEL7 with puppet-agent-1.8.3, puppetserver-2.7.2 (Completely new node) Client node : RHEL6 with puppet-agent-1.8.3 (OS unchanged) The puppet-agent includes its own ruby 2.1.0 from what I can see. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title
Matthias Saou updated an issue
Puppet / PUP-4633
User resource fails with UTF-8 comment on 2nd run
Change By:
Matthias Saou
I'm seeing something similar to PUP-1473 but only on the 2nd and subsequent runs :{code}[root@marionette tmp]# cat pup-1473.pp # pup-1473.ppuser { 'bubba' : comment => '™', ensure => present,}[root@marionette tmp]# puppet apply pup-1473.pp Notice: Compiled catalog for marionette. ovh example . 0x3e.net com in environment production in 0.40 secondsNotice: /Stage[main]/Main/User[bubba]/ensure: createdNotice: Applied catalog in 0.05 seconds[root@marionette tmp]# grep bubba /etc/passwdbubba:x:1029:1029:™:/home/bubba:/bin/bash[root@marionette tmp]# puppet apply pup-1473.pp Notice: Compiled catalog for marionette. ovh example . 0x3e.net com in environment production in 0.39 secondsError: Could not convert change 'comment' to string: incompatible character encodings: UTF-8 and ASCII-8BITError: Could not convert change 'comment' to string: incompatible character encodings: UTF-8 and ASCII-8BITError: /Stage[main]/Main/User[bubba]: Could not evaluate: Puppet::Util::Log requires a messageNotice: Applied catalog in 0.03 seconds[root@marionette tmp]# rpm -qa '*puppet*'puppet-agent-1.0.1-1.el7.x86_64puppetlabs-release-pc1-0.9.2-1.el7.noarchpuppetserver-2.0.0-1.el7.noarchpuppetdb-terminus-2.3.4-1.el7.noarchpuppetdb-2.3.4-1.el7.noarch{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this gr
Jira (PUP-4633) User resource fails with UTF-8 comment on 2nd run
Title: Message Title Matthias Saou created an issue Puppet / PUP-4633 User resource fails with UTF-8 comment on 2nd run Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/05/20 3:59 AM Priority: Normal Reporter: Matthias Saou I'm seeing something similar to PUP-1473 but only on the 2nd and subsequent runs : [root@marionette tmp]# cat pup-1473.pp # pup-1473.pp
Jira (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Matthias Saou commented on PUP-3918 Re: There should be a Node Terminus that uses a local YAML file like an External Node Classifier. I personally don't really care, though I think this would be nice to have "out of the box" given how trivial it seems to me to just read the yaml from a file. Also, the use case of wanting to copy/paste as-is an ENC YAML output to debug using puppet apply seems quite valid to me : It's so much easier and less error prone than to have to translate the YAML to Puppet DSL, or even to Hiera YAML since the ENC classes+parameters hash needs to be split up into a classes array + separate parameters for the Hiera auto lookup (unless I'm mistaken). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Matthias Saou commented on PUP-3918 Re: There should be a Node Terminus that uses a local YAML file like an External Node Classifier. I would also really like this feature. I tried the yaml node_terminus, and as some others have mentioned, it's not suitable because it expects some other kind of YAML. My use case is having a custom ENC, where changes are difficult to make since it's on production, and developers want to be able to quickly replicate a node's entire state. It's trivial to extract a node's YAML from the ENC, and once a developer has it, it needs to be used with "puppet apply". Here is my current workaround : $ cat .cat #!/bin/bash # Silly script, required for now. See : # https://tickets.puppetlabs.com/browse/PUP-3918 exec cat `dirname $0`/apply.yaml And I execute something along these lines : puppet apply -v --show_diff \ --hiera_config=/dev/null \
