Booting KIS images via AOE requires special setup that might be better handled directly by kiwi

[Glidos]

Problem description

1. A KIS image, that boots successfully when placed on local disc, fails to boot when served via aoe because the aoe kernel module isn't loaded.

2. If alterations are made to arrange for the aoe module to be loaded then, although the system boots successfully, there can be a one-minute stall in the process because aoe discovery is performed by the aoe kernel module only every minute, unless triggered by other means.

Expected behaviour

kiwi's dracut modules handle the loading of the aoe kernel module and the triggering of aoe discovery

Steps to reproduce the behaviour

Follow these instructions to create a KIS image: https://osinside.github.io/kiwi/building_images/build_kis.html
Follow these instructions to setup for booting via aoe: https://osinside.github.io/kiwi/working_with_images/network_overlay_boot.html

Workarounds for the problems

1. Add rd.modules_load=aoe to the boot command line. The system will then boot but with a one-minute stall while waiting for aoe discovery.

2. Arrange for aoe discovery when the network comes up by adding files to the root of the appliance description:
   a) Add the file <desc-dir>/root/lib/dracut/hooks/initqueue/online/aoe-discover.sh (the name must have the .sh extension) containing

#! /usr/bin/bash

logger -t "aoe-discover" "Link up"
if [[ -e /dev/etherd/discover ]]; then
    echo > /dev/etherd/discover
    logger -t "aoe-discover" "Discover triggered"
fi

b) Add the file <desc-dir>/root/etc/dracut.conf.d/aoe-discover.conf containing:

install_items+=" /lib/dracut/hooks/initqueue/online/aoe-discover.sh "

OS and Software information

• KIWI version: 9.24.61
• Operating system host version: OpenSUSE Leap 15.4
• Operating system target version: OpenSUSE Leap 15.4
• Open Build Service version (N/A if not using OBS): not used
• Koji version (N/A if not using Koji): not used