Re: [Kiwi-devel] Having Problem with KIWI and suse-ec2-guest
Robert Schweikert
On 02/27/2012 12:28 PM, matthew...@uwclub.net wrote:
>
>
> On Mon 4:30 PM , "MarcusSchäfer" m...@suse.de sent:
> Hi Marcus,
>
> wow! thanks for the swift reply ;-)
>
> I have followed the tutorial steps at the URL you provided, that has got me this far.
>
> I can confirm that I have checked config.sh and config.xml to make sure that sshd service gets started.
>
> I also tried passing "/etc/init.d/sshd restart" in the AWS instance Userdata.
sshd needs to be running so you can access the running instance.
However, this has nothing to do with the host key.
The errors with the ami-tools is a known bug: 721507
> ec2:failed to retrieve ec2-ami-tools from S3
> ec2:unable to update ec2-ami-tools
I've had not time to poke this yet, but Chris is now looking after the
problem and it should get addressed soon.
> ec2:failed
ec2:BEGIN SSH HOST KEY FINGERPRINTS
> ec2:/etc/ssh/ssh_host_key.pub: no such file or directory
> ec2:/etc/ssh/ssh_host_dsa_key.pub:no such file or directory
> ec2:/etc/ssh/ssh_host_rsa_key.pub: no such file or directory
Host key generation, i.e. a key-pair by which the machine is identified,
and not the user, usually happens on firstboot/installation. When you
install a system from scratch, at the end you'll will see a message and
get a graphical representation of the host key. This mechanism is, in
general, independent of KIWI.
There are some potrential culprits at play. Your host key is not getting
generated because
- of recent changes in the suse-ami-tools package
- you may be leaving out some basic package in config.xml
- you have customized/overwritten scripts that usually generate the host
key.
Sorry, but I forgot were exactly the host key gets generated. It is
probably easiest to work backwards from your setup and look at all the
files you have in your overlay tree.
For information on host key generation see the following:
http://www.geekride.com/how-to-generate-ssh-host-keys/
You can also add a work around into /etc/init.d/boot.local, check the
presence of the host key, and if it does not exist create one. However,
that the host keys are missing indicates an underlying issue and the
boot.local hack is only a dirty work around.
HTH,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rjsc...@suse.com
rsch...@ca.ibm.com
781-464-8147
matthew...@uwclub.net
thanks for the sanity check :-)
I solved the prob with the boot.local hack, I found something in testing using the boot.local
even though I have enabled "suseInsertService sshd" in my config.sh it fails to start, and AWS UserData to start sshd is ignored unless I put it manually
into /etc/init.d/boot.local along with a script to delete and recreate the SSH keys.
Anyhow, the hack has resolved my issue in the short term, so thanks again for the help - KIWI is amazing, keep up the good work ;-)
best regards
Matt
On Mon 6:37 PM , "Robert Schweikert" rjsc...@suse.com sent:
> Hi,
>
> On 02/27/2012 12:28 PM, mat
> rjschwei@su
> se.comrschweik@
> ca.ibm.com781-464-8147
>
> _______________________________________________
> Kiwi-devel mailing list
> K
> iwi-devel@lists.berlios.dehttps://lists.berlios.de/mailman/listinfo/kiwi-devel
>
>
>