Bug 1176561 - invalid byte sequence in US-ASCII
Summary: invalid byte sequence in US-ASCII
Keywords:
Status: CLOSED DUPLICATE of bug 1175399
Alias: None
Product: Red Hat OpenStack Installer
Classification: Retired
Component: openstack-foreman-installer
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jason Guiditta
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks: 1177026
TreeView+ depends on / blocked
 
Reported: 2014-12-22 10:59 UTC by Asaf Hirshberg
Modified: 2014-12-30 14:07 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-30 14:07:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Asaf Hirshberg 2014-12-22 10:59:04 UTC
Description of problem:
while deploying using the latest puddle an ha-neutron environment. the deployment have failed and when i tried to run puppet got this error:
(puppet agent -tvd)
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node mac441ea1733991.example.com: invalid byte sequence in US-ASCII
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


Version-Release number of selected component (if applicable):


How reproducible:
2/2

Steps to Reproduce:
deploy using latest puddle on bare metal an ha-neutron.

Comment 1 Alexander Chuzhoy 2014-12-23 21:24:55 UTC
The workaround that worked on Asaf's setup:
Need to add
Encoding.default_external = Encoding::UTF_8
Encoding.default_internal = Encoding::UTF_8

To the bottom of /etc/puppet/rack/config.ru file and restart the httpd service on the staypuft machine.

Comment 2 Asaf Hirshberg 2014-12-24 09:29:52 UTC
I have tried that workaround, when I using it I get the following message on all 3 controllers: 

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Local ip for ovs agent must be set when tunneling is enabled at /etc/puppet/environments/production/modules/neutron/manifests/agents/ovs.pp:32 on node mac441ea1733991.example.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


reproducible: 3/3

Comment 3 Alexander Chuzhoy 2014-12-24 13:26:17 UTC
That's because the interface used for tenant traffic doesn't have an IP on it.
Simply configure the interface with IP from the range used for tenant and retry running puppet.

Comment 4 Arthur Berezin 2014-12-30 14:07:28 UTC

*** This bug has been marked as a duplicate of bug 1175399 ***


Note You need to log in before you can comment on or make changes to this bug.