Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
PUP 4.0.0
-
None
-
1
-
Client 2015-07-22, Client 2015-08-19
-
Bug Fix
-
Failure to parse existing non-ASCII characters in user comment field - performed when comment is set by the user type - has been fixed.
Description
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
|
|
|
user { 'bubba' :
|
comment => '™',
|
ensure => present,
|
}
|
[root@marionette tmp]# puppet apply pup-1473.pp
|
Notice: Compiled catalog for marionette.example.com in environment production in 0.40 seconds
|
Notice: /Stage[main]/Main/User[bubba]/ensure: created
|
Notice: Applied catalog in 0.05 seconds
|
[root@marionette tmp]# grep bubba /etc/passwd
|
bubba:x:1029:1029:™:/home/bubba:/bin/bash
|
[root@marionette tmp]# puppet apply pup-1473.pp
|
Notice: Compiled catalog for marionette.example.com in environment production in 0.39 seconds
|
Error: Could not convert change 'comment' to string: incompatible character encodings: UTF-8 and ASCII-8BIT
|
Error: Could not convert change 'comment' to string: incompatible character encodings: UTF-8 and ASCII-8BIT
|
Error: /Stage[main]/Main/User[bubba]: Could not evaluate: Puppet::Util::Log requires a message
|
Notice: Applied catalog in 0.03 seconds
|
[root@marionette tmp]# rpm -qa '*puppet*'
|
puppet-agent-1.0.1-1.el7.x86_64
|
puppetlabs-release-pc1-0.9.2-1.el7.noarch
|
puppetserver-2.0.0-1.el7.noarch
|
puppetdb-terminus-2.3.4-1.el7.noarch
|
puppetdb-2.3.4-1.el7.noarch
|
