Hello Uwe, yes, the patch works and the init script is fetched from NFS! Thanks! Just a little detail: The log file of the init script contains the line "redirecting to systemctl" plus a lot of non-ascii characters following it, before it eventually contains the real script log. I am currently trying to reproduce the hang at "Configuring lan" reliably. I managed to do it once with a completely manual installation, hence it has nothing to do with AuoYaST! Best regards, Joschi Brauchle On 08/07/2012 01:40 PM, Uwe Gansert wrote:
On 07.08.2012 11:46, Joschi Brauchle wrote:
For me it looks like the /etc/resolv.conf is indeed empty like Christopher mentioned (at least inside the chrooted system, did not check outside). If I manually add a nameserver, the chroot script can mount the NFS server.
yes I know but that has always been the case For 12.2 I had to move some code from the 2nd to the 1st stage because of systemd. That included fetching the init-scripts. That step does not work for nfs for some reason in the 1st stage. I'll move the fetching back to 2nd stage and will only activate the autoyast service in stage1. That sould solve it. You can easily try that by changing
inst_autoconfigure.ycp
index 850d773..7a32eb9 100644 --- a/src/clients/inst_autoconfigure.ycp +++ b/src/clients/inst_autoconfigure.ycp @@ -243,8 +243,7 @@ Please wait while the system is being configured. logStep( _("Executing Post-Scripts")); AutoinstScripts::Write("post-scripts", false);
- // moved to 1st stage to fix issue with systemd - //AutoinstScripts::Write("init-scripts", false); + AutoinstScripts::Write("init-scripts", false);
// Just in case, remove this file to avoid reconfiguring... SCR::Execute(.target.remove, "/var/lib/YaST2/runme_at_boot");
if you do that change, it should work again. My complete patch is a bit bigger but for your test the patch is sufficient. Would be cool if you could test that on 12.2 It's enough to patch it in the installed system before you start yast. You can patch that via chroot script for example
Also, the (possibly related) problem that YaST hangs at the next step "Configuring lan" and the process list suggests that systemd is waiting for some kind of password/input (process name is: "/bin/systemd-tty-ask-password-agent --watch") persists after creating a valid resolv.conf.
I don't see that here. Network config works fine. At the moment I can not imagine what triggers that.