Bug #3628: invalid byte-sequence for encoding utf8 when importing facts - Foreman

Actions

Copy link

Bug #3628

closed

invalid byte-sequence for encoding utf8 when importing facts

Added by Dennis Benndorf over 10 years ago. Updated almost 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Facts

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

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 1 (0 open — 1 closed)

Actions

Copy link

Updated by Dominic Cleal over 10 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

Actions

Copy link

Updated by Dennis Benndorf about 10 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!

Actions

Copy link

Updated by Dennis Benndorf about 10 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".

Actions

Copy link