Bug 1265403

Summary: instack-undercloud fails to setup seed vm, parse error while creating ssh key
Product: Red Hat OpenStack Reporter: wes hayutin <whayutin>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED NOTABUG QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: apevec, lregebro, mburns, rhel-osp-director-maint, srevivo, vincent
Target Milestone: ---   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1266451 (view as bug list) Environment:
Last Closed: 2015-09-22 21:03:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1266451    
Attachments:
Description Flags
virt-setup.log none

Description wes hayutin 2015-09-22 20:18:44 UTC 
Created attachment 1076015 [details]
virt-setup.log

Description of problem:


seed VM not defined
Created machine seed with UUID 74b0e018-cb5e-4d28-9864-5ff0705fdc1a
Seed VM created with MAC 52:54:00:bf:b5:f0
Generating public/private rsa key pair.
Your identification has been saved in /root/.ssh/id_rsa_virt_power.
Your public key has been saved in /root/.ssh/id_rsa_virt_power.pub.
The key fingerprint is:
b2:c7:ea:78:13:71:1e:05:ed:db:8d:83:3f:98:75:a4 virtual-power-key
The key's randomart image is:
+--[ RSA 2048]----+
|        .o       |
|          o      |
|         o       |
|      . o .   .  |
|      .+S. + =   |
|      .+. o E o  |
|      ..o  = o   |
|     .oo  o o    |
|    .oo.     .   |
+-----------------+
parse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 32, column 30
Comment 3 James Slagle 2015-09-22 21:03:05 UTC 
epel was enabled, resulting in a newer jq, which requires some additional escaping.

i shall quote from the puddle etherpad instructions:

    You should *not* enable EPEL 

    (and when we say "not", we mean, if EPEL is enabled, your keyboard will catch on fire and burn you)
Comment 4 wes hayutin 2015-09-22 21:03:33 UTC 
NOT A BLOCKER, the jq rpm from EPEL was installed while testing another patch