Bug #13219
closed
Foreman unable to import puppet class with unicode characters.
Description
I am new with foreman ( used less than 12 hours ), so it is very likely that i have some setup problem.
I just spend 6 hours debugging why foreman is not able to import puppets btsync (mcanevet/btsync) module.
The modules was listed with puppet module list, so i think its fully foreman's problem.
The real problem was that btsync's init.pp file's comment ( ### ) contains unicode characters in developers personal name.
Removing those characters i was able to get to foreman to import the class.
My OS is running with UTF-8 locale, the file command shows that file is utf-8 encoded and foreman's config has utf-8 definition.
Updated by Arto Pastinen over 8 years ago
My OS is ubuntu ( lxc container ) 14.04, and foreman 1.10 stable guess..
Updated by Dominic Cleal over 8 years ago
- Project changed from Foreman to Smart Proxy
- Category set to Puppet
- Priority changed from High to Normal
Likely to be something with Unicode handling on the smart proxy side, and probably very dependent on the version of Ruby the service is running under.
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Anonymous
- Pull request https://github.com/theforeman/smart-proxy/pull/360 added
Updated by Anonymous over 8 years ago
Arto: please give https://github.com/theforeman/smart-proxy/pull/360 a try, should resolve the issue you were seeing.
Updated by Dominic Cleal about 8 years ago
- translation missing: en.field_release set to 123
Updated by Anonymous about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 0a70eea0979b981c1ae46cbcdaf49def285c72a7.
Updated by Dominic Cleal about 8 years ago
- Related to Bug #14473: invalid byte sequence in US-ASCII on UTF-8 manifests under C locale added