After iPXE boot DNS not working.

[Jan Robinson]

Hello All

Would you please assist?

We are booting a PXE build just fine but the DNS is not working.
IP configuration is working.

We continued testing since last October - (Wait for it.. I think I was working back then.)

Direction will be appreciated.

dracut.cmdline:
ip=${ip}::${gateway}:${netmask}:${hostname}:eth0:none:${dns}:15.30.252.2

The PXE installed server a VMWARE VM SLES15.3
Linux ldocker03 5.3.18-150300.59.43-default
dracut-kiwi-oem-dump-9.24.36-1.1.x86_64
dracut-kiwi-lib-9.24.36-1.1.x86_64
dracut-kiwi-oem-repart-9.24.36-1.1.x86_64
dracut-kiwi-live-9.24.36-1.1.x86_64

Kiwi server
kiwi101 5.3.18-59.27-default
kiwi-systemdeps-core-9.24.36-1.1.x86_64
kiwi-pxeboot-9.24.36-1.1.x86_64
kiwi-tools-9.24.36-1.1.x86_64
kiwi-systemdeps-9.24.36-1.1.x86_64
python3-kiwi-9.24.36-1.1.x86_64
kiwi-boot-descriptions-1.2.0-2.51.x86_64
kiwi-man-pages-9.24.36-1.1.x86_64

<type image="oem" filesystem="ext4" installpxe="true" initrd_system="dracut" installboot="install" kernelcmdline="splash rd.kiwi.ramdisk ramdisk_size=4096000">
    <!-- <bootloader name="grub2" console="console" timeout="10"/> -->
<oemconfig>
    <oem-skip-verify>true</oem-skip-verify>
    <oem-unattended>true</oem-unattended>
    <oem-unattended-id>/dev/ram0</oem-unattended-id>
    <oem-device-filter>/dev/sd</oem-device-filter>
    <oem-swap>false</oem-swap>
    <oem-multipath-scan>false</oem-multipath-scan>
</oemconfig>

boot.ipxe
kernel http://kiwi101.abcgroup.net/ldocker03.abcgroup.net.kernel console=ttyS0,115200 console=tty1 debug initrd=vmware initrd=boot/initrd rd.neednet=1 ip=${ip}::${gateway}:${netmask}:${hostname}:eth0:none:${dns}:15.30.252.2 rd.debug rd.kiwi.debug rd.kiwi.install.pxe rd.kiwi.ramdisk ramdisk_size=4096000 rd.kiwi.install.image=http://kiwi101.bmwgroup.net/pxe-result/SLES15-MiniOS-VMW-OEM-PXE.DEFAULT.x86_64-15.3.xz module_blacklist=vmwgfx root="/dev/mapper/ram0p1"

# ls -l /etc/resolv.conf  /run/netconfig/re
lrwxrwxrwx 1 root root 26 Jun  2 18:12 /etc/resolv.conf -> /run/netconfig/resolv.conf
-rw-r--r-- 1 root root  0 Jun  2 18:12 /run/netconfig/resolv.conf

This directory is empty: /etc/tmpfiles.d/

Tried this set to : NETCONFIG_DNS_POLICY=""
Does not help.

Please see attached log file.

Thank you so much.
Jan

[Roger Oberholtzer]

Is the DNS info obtained via DHCP? If so, in your image, is there
already an /etc/resolv.conf file? We have had issues where we put that
file in the kiwi image (expecting it to be a default when DHCP is not
used), but more recent versions (e.g. 15.3 that I know of), act
differently when this file is present and not made by dhcp. Removing
/etc/resolv.conf solved our DNS/DHCP issue.

> --
> You received this message because you are subscribed to the Google Groups "kiwi" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kiwi-images...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kiwi-images/6e5730b1-f0cc-47ea-abab-cd8a1a49affan%40googlegroups.com.



--
Roger Oberholtzer

[Jan Robinson]

Hi Roger

We are not using DHCP.
The image does not contain an /etc/resolv.conf

All IP information is from here:

dracut.cmdline:
ip=${ip}::${gateway}:${netmask}:${hostname}:eth0:none:${dns}:15.30.252.2

This is acknowledged in the log file and dns1 and dns2

But resolv.conf not populated.

The expectation is that it should.

Some info as a side note from a Sles15.4 build: 

This same kiwi configuration config.xm is used to build a 15.4 image.

This error out to the emergency shell.  (ram disk error)

In this shell the /etc/resolv.conf is created with the correct dns information.

Thank you,

Jan