[Bug 1172381] New: dracut builds incorrect boot arguments
http://bugzilla.opensuse.org/show_bug.cgi?id=1172381 Bug ID: 1172381 Summary: dracut builds incorrect boot arguments Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: per@computer.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- When I install TW on NFS, the system never boots the fist time. I always have to reboot the installer and rebuild the initrd. To me it looks like a lack of /etc/resolv.conf when the first initrd is being built. Built during installation: root=nfs4:rootserver:/srv/nfsroot/mole28:rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2a03:7520:4c68:1:ff99:ffff:0:93cd,local_lock=none,addr=2a03:7520:4c68:1::128 ifname=eth0:00:30:48:d3:75:74 ip=eth0:static When I reboot the installer, and I mount the NFS root on /mnt, followed by cd /mnt mount -o bind /proc proc mount -o bind /dev dev mount -o bind /sys sys mount -o bind /run run chroot . and I rebuild the initrd, I get: root=nfs4:rootserver:/srv/nfsroot/mole28:rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2a03:7520:4c68:1:ff99:ffff:0:6ac8,local_lock=none,addr=2a03:7520:4c68:1::128 ifname=eth0:00:30:48:d3:75:74 ip=eth0:dhcp -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172381 http://bugzilla.opensuse.org/show_bug.cgi?id=1172381#c3 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #3 from Per Jessen <per@computer.org> --- (In reply to Michal Filka from comment #1)
@Per: do you use static network configuration in first installation run?
Hi Michal, no it's all dhcp. If it helps, this is not a new issue, but I have just become so used to working around it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172381 http://bugzilla.opensuse.org/show_bug.cgi?id=1172381#c4 --- Comment #4 from Per Jessen <per@computer.org> --- (In reply to Josef Reidinger from comment #2)
well, yes. Bootloader copy installation kernel parameters to target system parameters. But if I get issue, it is about missing resolv.conf in dracut, maybe issue is that we run dracut in target system and that system maybe missing resolv.conf which lives in during installation in insts-sys and not target system?
That is my guess - when I boot the installer again to rebuild the initrd, I have to additionally do the bind-mount of /run (to get a working resolv.conf). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172381 http://bugzilla.opensuse.org/show_bug.cgi?id=1172381#c5 --- Comment #5 from Per Jessen <per@computer.org> --- Sorry, I think this is a duplicate of bug#1003872 that I opened four years back. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com