Hi,
I'm playing with debian-installer in order to perform fully automatic network
installations of Ubuntu 16.04 for s390x.
I noticed something odd regarding the network-console: it seems to not consider
the values set in the preseed file and keeps asking for the password in the
"Continue installation remotely using SSH" question. It does consider some
other values in preseed file, like the mirror and partitions configuration.
My preseed file contains the following settings for network console:
d-i network-console/password password r00t
d-i network-console/password-again password r00t
d-i network-console/start select continue
The cmdline to start the install process was (I intentionally omitted the
network configuration):
s390-netdevice/choose_networktype=virtio netcfg/use_autoconfig=false
netcfg/disable_autoconfig=true netcfg/get_ipaddress=xxx.xxx.xxx.xx
netcfg/get_netmask=xxx.xxx.xxx.xxx netcfg/get_gateway=xxx.xxx.xxx.xxx
netcfg/get_nameservers=x.xxx.xxx.xxx netcfg/confirm_static=true
priority=critical preseed/url=http://host/preseed2.cfg DEBCONF_DEBUG=developer
By looking at /var/etc/syslog I could notice that it is not able to get the
values from debconf db:
Jun 20 18:40:09 debconf: --> METAGET debian-installer/netcfg/title Description
Jun 20 18:40:09 debconf: <-- 0 Configure the network
Jun 20 18:40:09 debconf: --> METAGET debian-installer/network-console/title
Description
Jun 20 18:40:09 debconf: <-- 0 Continue installation remotely using SSH
Jun 20 18:40:09 main-menu[209]: INFO: Menu item 'network-console' selected
Jun 20 18:40:09 debconf: --> SETTITLE debian-installer/network-console/title
Jun 20 18:40:09 debconf: <-- 0 OK
Jun 20 18:40:09 debconf: --> PROGRESS START 0 1 network-console/key
Jun 20 18:40:09 debconf: <-- 0 OK
Jun 20 18:40:09 debconf: --> PROGRESS STOP
Jun 20 18:40:09 debconf: <-- 0 OK
Jun 20 18:40:09 debconf: --> GET network-console/password
Jun 20 18:40:09 debconf: <-- 0
Jun 20 18:40:09 debconf: --> GET network-console/authorized_keys_url
Jun 20 18:40:09 debconf: <-- 0
Jun 20 18:40:09 debconf: --> INPUT critical network-console/password
Jun 20 18:40:09 debconf: <-- 0 question will be asked
Jun 20 18:40:09 debconf: --> INPUT high network-console/password-again
Jun 20 18:40:09 debconf: <-- 30 question skipped
Jun 20 18:40:09 debconf: --> GO
Jun 20 18:40:13 debconf: <-- 0 ok
Jun 20 18:40:13 debconf: --> GET network-console/password
Jun 20 18:40:13 debconf: <-- 0 r00t
Jun 20 18:40:13 debconf: --> GET network-console/password-again
Jun 20 18:40:13 debconf: <-- 0
Jun 20 18:40:13 debconf: --> SET network-console/password
Jun 20 18:40:13 debconf: <-- 0 value set
Jun 20 18:40:13 debconf: --> SET network-console/password-again
Jun 20 18:40:13 debconf: <-- 0 value set
Jun 20 18:40:13 debconf: --> FSET network-console/password seen false
Jun 20 18:40:13 debconf: <-- 0 false
Jun 20 18:40:13 debconf: --> FSET network-console/password-again seen false
Jun 20 18:40:13 debconf: <-- 0 false
Jun 20 18:40:14 sshd[293]: Server listening on 0.0.0.0 port 22.
Jun 20 18:40:14 sshd[293]: Server listening on :: port 22.
However, when I set those parameters in the boot cmdline, it does work, and
does not ask for the password. Here is the cmdline:
s390-netdevice/choose_networktype=virtio netcfg/use_autoconfig=false
netcfg/disable_autoconfig=true netcfg/get_ipaddress=xxx.xxx.xxx.xx
netcfg/get_netmask=xxx.xxx.xxx.xxx netcfg/get_gateway=xxx.xxx.xxx.xxx
netcfg/get_nameservers=x.xxx.xxx.xxx netcfg/confirm_static=true
priority=critical preseed/url=http://host/preseed2.cfg DEBCONF_DEBUG=developer
network-console/password=r00t network-console/password-again=r00t
network-console/start=continue
The log from /var/log/syslog presents a different output:
Jun 20 18:52:05 debconf: --> METAGET debian-installer/network-console/title
Description
Jun 20 18:52:05 debconf: <-- 0 Continue installation remotely using SSH
Jun 20 18:52:05 main-menu[210]: INFO: Menu item 'network-console' selected
Jun 20 18:52:05 debconf: --> SETTITLE debian-installer/network-console/title
Jun 20 18:52:05 debconf: <-- 0 OK
Jun 20 18:52:05 debconf: --> PROGRESS START 0 1 network-console/key
Jun 20 18:52:05 debconf: <-- 0 OK
Jun 20 18:52:06 debconf: --> PROGRESS STOP
Jun 20 18:52:06 debconf: <-- 0 OK
Jun 20 18:52:06 debconf: --> GET network-console/password
Jun 20 18:52:06 debconf: <-- 0 r00t
Jun 20 18:52:06 debconf: --> GET network-console/authorized_keys_url
Jun 20 18:52:06 debconf: <-- 0
Jun 20 18:52:06 debconf: --> INPUT critical network-console/password
Jun 20 18:52:06 debconf: <-- 30 question skipped
Jun 20 18:52:06 debconf: --> INPUT high network-console/password-again
Jun 20 18:52:06 debconf: <-- 30 question skipped
Jun 20 18:52:06 debconf: --> GO
Jun 20 18:52:06 debconf: <-- 0 ok
Jun 20 18:52:06 debconf: --> GET network-console/password
Jun 20 18:52:06 debconf: <-- 0 r00t
Jun 20 18:52:06 debconf: --> GET network-console/password-again
Jun 20 18:52:06 debconf: <-- 0 r00t
Jun 20 18:52:06 debconf: --> SET network-console/password
Jun 20 18:52:06 debconf: <-- 0 value set
Jun 20 18:52:06 debconf: --> SET network-console/password-again
Jun 20 18:52:06 debconf: <-- 0 value set
Jun 20 18:52:06 debconf: --> FSET network-console/password seen false
Jun 20 18:52:06 debconf: <-- 0 false
Jun 20 18:52:06 debconf: --> FSET network-console/password-again seen false
Jun 20 18:52:06 debconf: <-- 0 false
Jun 20 18:52:06 sshd[294]: Server listening on 0.0.0.0 port 22.
Jun 20 18:52:06 sshd[294]: Server listening on :: port 22.
Am I missing something or is this a bug/issue? Does someone have any tips to
further investigate this problem?
Best regards,
Raphael Silva
Software Engineer
Linux Technology Center - IBM Brazil
--
ubuntu-server mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
