What were you trying to do that didn't work?

A valid configuration without an explicit NM_CONTROLLED=no (the default being yes), and a NetworkManager.service disabled leads to no inhibitor or warning, and network is down post-reboot. It can be a problem to connect afterwards, and some FirstBoot phase tasks are not performed.

What is the impact of this issue to you?

Problems to connect post-reboot

Please provide the package NVR for which the bug is seen:

leapp-upgrade-el8toel9-0.22.0-1.el8_10.noarch

How reproducible is this bug?:

Always

Steps to reproduce

1. Install network-scripts
2. Create an ifcfg like this.

# cat /etc/sysconfig/network-scripts/ifcfg-enp1s0 
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.124.200
PREFIX=24
GATEWAY=192.168.124.1
DNS=192.168.124.1
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME=enp1s0
#UUID=edb53518-75f9-452c-8663-4bd5593e418f
HWADDR=52:54:00:26:7a:6d
DEVICE=enp1s0
ONBOOT=yes

3. Disable NetworkManager.service and reboot
4. leapp upgrade

Expected results

An inhibitor, or at least a high risk is reported.

Actual results

No inhibitor.
Network down post reboot.