Comment # 41 on bug 902464 from Tom Burkart

(In reply to Stefan Schubert from comment #40)
> Regarding wickedd: The error happens before YaST will be called at all. OK,
This may well be the case, however, I have noticed that YaST does try to start
the network but it fails.  I have not managed to figure out why.

> the starting order will be influenced by YaST. But as I described before,
> the order is the same as in SLES12-SP1. Anyway, an error will be reported
> but has no influence to the following installation and booting workflow. So
> I think it is not so harmful.
The influence of the installation and booting workflow is as follows:  All of
my post-installation configuration will fail if the network is dead.  Of course
any Stage 2 package installation will also fail.

Ever since bug 932605 was marked a duplicate of this one, we are now dealing
with two similar bugs that are quite different.

In comment 38 I explained the workaround I found that allows me to "continue
working" but as I use it for "unattended installs" it is really annoyingly
seriously broken as I now have to watch the install to go into Single user mode
and start the networking component manually.

This is frustrating as I normally fix this sort of thing myself but I am unsure
how to dissect AutoYaST to try to ascertain how to fix it.  As a result, any
help in fixing this would be greatly appreciated.