Bug 1314414 - 'tripleo.sh -undercloud' install fails with Unicode decode error
Summary: 'tripleo.sh -undercloud' install fails with Unicode decode error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 14:28 UTC by Russell Tweed
Modified: 2017-04-12 13:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 15:45:05 UTC
Target Upstream Version:


Attachments (Terms of Use)
rhos-release-8-director.repo (2.05 KB, text/plain)
2016-03-03 14:34 UTC, Russell Tweed
no flags Details
Full logfile from 'tripleo.sh -undercloud' run (157.42 KB, text/plain)
2016-03-03 14:36 UTC, Russell Tweed
no flags Details
rhos-release-rhel-7.2.repo (1.14 KB, text/plain)
2016-03-03 14:40 UTC, Russell Tweed
no flags Details
Full logfile from 'tripleo.sh -undercloud' run (157.70 KB, text/plain)
2016-03-03 15:42 UTC, Russell Tweed
no flags Details

Description Russell Tweed 2016-03-03 14:28:54 UTC
Description of problem:

Following the instructions from here: http://etherpad.corp.redhat.com/osp8-rhop-release

...the install process can't proceed beyond line #38. It stops with the following error:

line 38: tripleo.sh --undercloud
install fails with the following:

+ set -eu
+ set -o pipefail
+ '[' -z '/etc/yum.repos.d/rhos-release-8-director.repo /etc/yum.repos.d/rhos-release-rhel-7.2.repo' ']'
+ for file in '$DIB_YUM_REPO_CONF'
+ '[' '!' -f /etc/yum.repos.d/rhos-release-8-director.repo ']'
+ sudo cp -L -f /etc/yum.repos.d/rhos-release-8-director.repo /tmp/instack.vzZNiu/mnt/etc/yum.repos.d
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 773, in install
    _run_instack(instack_env)
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 657, in _run_instack
    _run_live_command(args, instack_env, 'instack')
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 346, in _run_live_command
    line = process.stdout.readline().decode()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 4: ordinal not in range(128)
Command 'instack-install-undercloud' returned non-zero exit status 1

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



Steps to Reproduce:
1. Follow instructions at http://etherpad.corp.redhat.com/osp8-rhop-release

Actual results:

Error as above

Expected results:

A completed Undercloud install

Additional info:

Comment 2 Russell Tweed 2016-03-03 14:34:01 UTC
Created attachment 1132812 [details]
rhos-release-8-director.repo

Comment 3 Russell Tweed 2016-03-03 14:36:24 UTC
Created attachment 1132813 [details]
Full logfile from 'tripleo.sh -undercloud' run

Comment 4 Russell Tweed 2016-03-03 14:40:27 UTC
Created attachment 1132816 [details]
rhos-release-rhel-7.2.repo

Comment 5 Russell Tweed 2016-03-03 14:41:20 UTC
Note this is running on RHEL7 with the following versions:

[stack@pod5-infra1 yum.repos.d]$ uname -a
Linux pod5-infra1.cloud.practice.redhat.com 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux

[stack@pod5-infra1 yum.repos.d]$ rpm -qa |grep -i release
redhat-release-server-7.1-1.el7.x86_64
rhos-release-1.0.35-1.noarch

Comment 6 Russell Tweed 2016-03-03 15:42:34 UTC
Created attachment 1132846 [details]
Full logfile from 'tripleo.sh -undercloud' run

Comment 7 James Slagle 2016-03-05 17:20:25 UTC
tripleo.sh is not meant for use with osp-d. it really only works when using the upstream tripleo bits directly.

does your issue reproduce on a clean environment where tripleo.sh has never been run?

Comment 8 Mike Burns 2016-04-07 21:14:44 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.


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