on Tuesday 22 November 2011 686f6c6d wrote:
When installing with "<final_reboot config:type="boolean">false</final_reboot>" (as we did until now), (1.) the kexec at the end still does not seem to work,
So do I understand you correctly, that you use final_reboot to fix a broken kexec after the 1st stage? did you try to skip the kexec with forceboot? <forceboot config:type="boolean">true</forceboot>
so (2.) services are not started (but apart from that, the <runlevel> config seems to be applied, which is an improvement) and so (3.) no ssh keys are generated.
I can not reproduce this ssh problem here. Maybe you can send me your complete package list. It's probably a problem with a combination of packages like apparmor or so. This is the package list I am using and I don't see a problem when I use the chroot script:
<software> <do_online_update config:type="boolean">true</do_online_update> <patterns config:type="list"> <pattern>base</pattern> </patterns> <packages config:type="list"> <package>yast2-slp</package> <package>yast2-bootloader</package> <package>yast2-ncurses</package>
<package>less</package> <package>zypper</package> <package>vim</package> </packages> <post-packages config:type="list"> <package>dnsmasq</package> </post-packages> </software>·
After manual reboot I did not see the belated execution of kexec as before. (4.) Creating the ssh keys does not work: The ECDSA ssh key is generated during reboot, but for some reason creating the DSA key fails and so the sshd fails to start (also on subsequent reboots).
at the end of the installation I have:
vbox-ug:~ # l /etc/ssh/ insgesamt 172 drwxr-xr-x 2 root root 4096 23. Nov 09:39 ./ drwxr-xr-x 72 root root 4096 23. Nov 09:39 ../ -rw------- 1 root root 125811 29. Okt 17:40 moduli -rw-r--r-- 1 root root 3056 29. Okt 17:40 ssh_config -rw-r----- 1 root root 3825 29. Okt 17:40 sshd_config -rw------- 1 root root 668 28. Okt 10:25 ssh_host_dsa_key -rw-r--r-- 1 root root 610 28. Okt 10:25 ssh_host_dsa_key.pub -rw------- 1 root root 227 23. Nov 09:39 ssh_host_ecdsa_key -rw-r--r-- 1 root root 174 23. Nov 09:39 ssh_host_ecdsa_key.pub -rw------- 1 root root 985 22. Nov 16:54 ssh_host_key -rw-r--r-- 1 root root 650 22. Nov 16:54 ssh_host_key.pub -rw------- 1 root root 1675 22. Nov 16:54 ssh_host_rsa_key -rw-r--r-- 1 root root 402 22. Nov 16:54 ssh_host_rsa_key.pub
When installing with "<final_reboot config:type="boolean">true</final_reboot>", I am seeing Heisenbugs:
- The first time, the machine rebooted just fine and everything worked
like a charm.
- The next few times (after commenting out unrelated stuff in my
autoyast profile; yes, I am sure I didn't accidentally break things, I'm using diffs and all those shiny things), I saw the same behavior as for kexec, which is to say it did not work because ssh did not come up, seemingly because of the missing DSA key.
- Then, during another install, the machine complained about the
missing DSA key again, but the sshd came up anyway. Repeated installations behaved the same way: The error was displayed, but it in the end it worked.
do you use any special linuxrc parameters? Like doing a VNC or SSH installation?
When using sysvinit-init now, I see the same ssh error message as with systemd. This wasn't there earlier today with sysvinit, but at least now systemd and sysvinit behave the same way.