SLES Private Image Creation
Background
Some customers encountered network issues after creating private images based on our latest SLES 15 SP6 image. The problem was related to DHCP lease files not being properly cleaned up.
To prevent this, in addition to using sysprep or a custom cleanup script before creating a private image from an OTC instance, the DHCP lease information must be cleared. Otherwise, it can cause DHCP-related issues.
Solution
The issue was caused by leftover lease files from wicked. To resolve this, delete the lease files before creating an image from the instance:
ls -l /var/lib/wicked/duid.xml
ls -l /var/lib/wicked/lease*
rm /var/lib/wicked/duid.xml /var/lib/wicked/lease*