Project

General

Profile

Bug #3628

invalid byte-sequence for encoding utf8 when importing facts

Added by Dennis Benndorf over 5 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Facts
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When importing hosts and facts in foreman 1.3.1 with

foreman-rake puppet:import:hosts_and_facts

I get the following error message:

rake aborted!
PG::CharacterNotInRepertoire: FEHLER:  ungültige Byte-Sequenz für Kodierung »UTF8«: 0xe46973
: INSERT INTO "fact_values" ("created_at", "fact_name_id", "host_id", "updated_at", "value") VALUES ($1, $2, $3, $4, $5) RETURNING "id" 

All other hosts are imported correctly, but this one. It is the only Windows-Server in this setup.


Related issues

Related to Foreman - Bug #1560: Foreman and windows-1250 encoding (puppet facts)Resolved2012-03-30

History

#1 Updated by Dominic Cleal over 5 years ago

  • Subject changed from invalid byte-sequence for encoding utf8 to invalid byte-sequence for encoding utf8 when importing facts
  • Category set to Facts

#2 Updated by Dennis Benndorf over 5 years ago

This bug does affects all Windows-Servers we have, so having one Windows in Puppet blocks importing Facts into Foreman. Rake aborts importing all server which follow in the list!

#3 Updated by Dennis Benndorf over 5 years ago

The Problem seems to be the same as Bug #1560 "Foreman and windows-1250 encoding (puppet facts)".
There is an umlaut in a time fact "Mitteleuropäische Zeit".

#4 Updated by Markus Frosch over 4 years ago

  • Related to Bug #1560: Foreman and windows-1250 encoding (puppet facts) added

#5 Updated by Markus Frosch over 4 years ago

This PR should fix it, but it is only in master until now:
https://github.com/theforeman/puppet-foreman/pull/274

#6 Updated by Dominic Cleal over 4 years ago

  • Status changed from New to Feedback

It'll be in Foreman 1.8.

#7 Updated by Michael Moll about 2 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF