Better key handling + logger messages

Bug #1083715 reported by Joshua Harlow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Low
Joshua Harlow

Bug Description

I was creating a VM on gq1, with ‘euca-run-instances -t y.small ami-00000041’.
I saw this in the console output (via euca-get-console-output). I am guessing
the “logger: invalid option” thing can be ignored, but am wondering whether it
is something that can be changed on cloud-init side, so as not to output it?

--ruby

unknown key type ecdsa
2012-11-26 15:30:36,699 - util.py[WARNING]: Failed generating key type ecdsa to
file /etc/ssh/ssh_host_ecdsa_key
Starting cloud-init: Cloud-init v. 0.7.1 running 'modules:config' at Mon, 26
Nov 2012 15:30:37 +0000. Up 17.45 seconds.
Starting cloud-init: Cloud-init v. 0.7.1 running 'modules:final' at Mon, 26 Nov
2012 15:30:37 +0000. Up 17.98 seconds.
logger: invalid option -- '-'
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]
-----BEGIN SSH HOST KEY KEYS-----
ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEAs4Nj3UZ9q8FFYdXeJTAn6/b2lr2uv2cVVU0ZrFRpipdwQ0iaIXO/mGiA2QkIQ3RkM0ygjxNLU0r/2SD68XcpWTSq3XIgJeR0yt46qV8ewQdwfpOSee3E5hzevZKNeigAd3HEMqcDKwAiY+YSgA6quzdmF+X6jNhlaOSb9jQH+uSwvtGmeuMmbQobNmA7Bc9awQYd9r/3C4BV/dep69TMBdTdTScleJ/wQhgWFlXB025JUfEL/SLTxwrNulLw6mbn3cRY4XYAehXUgTlSlTBl6GOxZw83hPGYqYygbqPdatX8i7Jm57obNi/uCpwcWUJtacvpWJVJvUpt//15EbV9NQ==
<email address hidden>
-----END SSH HOST KEY KEYS-----
Cloud-init v. 0.7.1 finished at Mon, 26 Nov 2012 15:30:37 +0000. Datasource
DataSourceConfigDriveNet [net,ver=1][source=/dev/vdb]. Up 18.19 seconds

Related branches

Joshua Harlow (harlowja)
Changed in cloud-init:
assignee: nobody → Joshua Harlow (harlowja)
Revision history for this message
Scott Moser (smoser) wrote :

hm.. the only thing i know that would be using 'logger' straight away is
tools/write-ssh-key-fingerprints

it would seem that your 'logger' doesn't like the '--stderr' option.
possibly its sufficient there to change '--stderr' to '-s'.
generally i prefer the long format options, as they're self documenting. i'd otherwise have no idea what '-s' is.

what os was this ?

Revision history for this message
Joshua Harlow (harlowja) wrote :

$ uname -a
Linux oxy-oxygen-0a-57-5c-76.corp.gq1.yahoo.com 2.6.32-220.23.1.el6.YAHOO.20120713.x86_64 #1 SMP Fri Jul 13 11:40:51 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 6.2 (Santiago)
Release: 6.2
Codename: Santiago

Looking at `man logger` on that VM (a similar one actually) it appears that the older versions of logger don't have the log option :-/

Revision history for this message
Joshua Harlow (harlowja) wrote :

The rhel lacking of ecdsa support can be solved by the following cloud.cfg

ssh_genkeytypes: ['rsa', 'dsa']

Revision history for this message
Scott Moser (smoser) wrote :

pushed fix in revno 746

Changed in cloud-init:
importance: Undecided → Low
milestone: none → 0.7.2
status: New → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote :

fixed in 0.7.2

Changed in cloud-init:
milestone: 0.7.2 → none
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.