Project

General

Profile

Bug #13219

Foreman unable to import puppet class with unicode characters.

Added by Arto Pastinen over 3 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
Puppet
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.


Related issues

Related to Kafo - Bug #14473: invalid byte sequence in US-ASCII on UTF-8 manifests under C localeClosed2016-04-05

Associated revisions

Revision 0a70eea0 (diff)
Added by Dmitri Dolguikh over 3 years ago

Fixes #13219: force utf-8 external encoding on puppet classes

History

#1 Updated by Arto Pastinen over 3 years ago

My OS is ubuntu ( lxc container ) 14.04, and foreman 1.10 stable guess..

#2 Updated by Dominic Cleal over 3 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.

#3 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Dmitri Dolguikh
  • Pull request https://github.com/theforeman/smart-proxy/pull/360 added

#4 Updated by Dmitri Dolguikh over 3 years ago

Arto: please give https://github.com/theforeman/smart-proxy/pull/360 a try, should resolve the issue you were seeing.

#5 Updated by Dominic Cleal over 3 years ago

  • Legacy Backlogs Release (now unused) set to 123

#6 Updated by Anonymous over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#7 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #14473: invalid byte sequence in US-ASCII on UTF-8 manifests under C locale added

Also available in: Atom PDF