Bug 1273453 - sshpw failed on f23 TC1
Summary: sshpw failed on f23 TC1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 23
Hardware: ppc64le
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-20 13:13 UTC by Menanteau Guy
Modified: 2015-10-20 14:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 14:03:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Menanteau Guy 2015-10-20 13:13:04 UTC
Impossible to get a ssh connection to anaconda when using sshpw options in grub command.

I am trying to install f23 TC1 on ppc64le VM 
http://ppc.koji.fedoraproject.org/compose/23_TC1/23_TC1/Server/ppc64le/iso/Fedora-Server-DVD-ppc64le-23_TC1.iso
using following grub command:
linux /ppc/ppc64/vmlinuz inst.sshd sshpw --username=test testpassw0rd --plaintext;
initrd /ppc/ppc64/initrd.img;
boot

When I get to the following panel:

Starting installer, one moment...
anaconda 23.19.6-1 for Fedora 23_TC1 (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * if the graphical installation interface fails to start, try again with the
   inst.text bootoption to start text installation
 * when reporting a bug add logs from /tmp as separate text/plain attachments
13:06:18 X startup failed, falling back to text mode
================================================================================
================================================================================
VNC

X was unable to start on your machine.  Would you like to start VNC to connect t
o this computer from another computer and perform a graphical installation or co
ntinue with a text mode installation?

 1) Start VNC

 2) Use text mode

  Please make your choice from above ['q' to quit | 'c' to continue |
  'r' to refresh]:

I try to connect thru ssh to the VM machine using "ssh test@vm55"
and it fails with "Permission denied, please try again."
Using "ssh root@vm55" succeed...

Note that in syslog, there is:
12:36:27,212 ERR sshd: error: Could not load host key: /etc/ssh/ssh_host_dsa_key
but it seems not linked to the problem:

[anaconda root@vm55 tmp]# ls -al /etc/ssh/ssh*key
-rw-r-----. 1 root ssh_keys  227 Oct 20 12:41 /etc/ssh/ssh_host_ecdsa_key
-rw-r-----. 1 root ssh_keys  387 Oct 20 12:41 /etc/ssh/ssh_host_ed25519_key
-rw-r-----. 1 root ssh_keys 1675 Oct 20 12:41 /etc/ssh/ssh_host_rsa_key

[anaconda root@vm55 tmp]# ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key

[anaconda root@vm55 tmp]# ls -al /etc/ssh/ssh*key
-rw-------. 1 root root      672 Oct 20 12:46 /etc/ssh/ssh_host_dsa_key
-rw-r-----. 1 root ssh_keys  227 Oct 20 12:41 /etc/ssh/ssh_host_ecdsa_key
-rw-r-----. 1 root ssh_keys  387 Oct 20 12:41 /etc/ssh/ssh_host_ed25519_key
-rw-r-----. 1 root ssh_keys 1675 Oct 20 12:41 /etc/ssh/ssh_host_rsa_key

[anaconda root@vm55 tmp]# chgrp ssh_keys /etc/ssh/ssh_host_dsa_key
[anaconda root@vm55 tmp]# systemctl restart sshd 

ssh root without password still succeed when ssh test@vm55 still fails

Comment 1 Martin Kolman 2015-10-20 13:23:42 UTC
The sshpw command needs to be in a kickstart file, not on the boot command line.

Comment 2 David Shea 2015-10-20 14:03:16 UTC
As comment 1 states, sshpw needs to be in a kickstart. This is documented with the inst.sshd option at https://github.com/rhinstaller/anaconda/blob/master/docs/boot-options.rst#instsshd, and the kickstart command is described at https://github.com/rhinstaller/pykickstart/blob/master/docs/kickstart-docs.rst#sshpw


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