On Tue, Nov 22, 2011 at 14:42, Uwe Gansert email@example.com wrote:
can you try to add a chroot-script and report me if it helps?
Here it helps and then I know how to fix it but systemd seems to be more magic than it looks like on the first sight and I need to be sure it works everywhere.
<chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <source><![CDATA[ insserv autoyast ]]></source> </script>
Ah, I misunderstood your reply in the other thread. Removing my <remove-package> entry for systemd and inserting your snippet and, of course, "</chroot-scripts>" changes things, but it does not work completely as it did in 11.4:
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 (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. 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).
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.
(The sshd error message is, for all the described cases: "Generating /etc/ssh/ssh_host_dsa_key. DSA keys must be 1024 bits Starting SSH daemonCould not load host key: /etc/ssh/ssh_host_dsa_key done" (or, most of the time, "fail").)
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.