Bug 1265403 - instack-undercloud fails to setup seed vm, parse error while creating ssh key
instack-undercloud fails to setup seed vm, parse error while creating ssh key
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high Severity high
: ---
: 7.0 (Kilo)
Assigned To: James Slagle
Depends On:
Blocks: 1266451
  Show dependency treegraph
Reported: 2015-09-22 16:18 EDT by wes hayutin
Modified: 2016-04-18 02:55 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1266451 (view as bug list)
Last Closed: 2015-09-22 17:03:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
virt-setup.log (12.44 KB, text/plain)
2015-09-22 16:18 EDT, wes hayutin
no flags Details

  None (edit)
Description wes hayutin 2015-09-22 16:18:44 EDT
Created attachment 1076015 [details]

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 17:03:05 EDT
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 17:03:33 EDT
NOT A BLOCKER, the jq rpm from EPEL was installed while testing another patch

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