Comment # 7 on bug 902464 from Luiz Angelo Daros de Luca

yast tried to start wicked as I would expect and it gave me an error
(attachment 611139 [details]). If it succeeded, everything would work. Shouldn't the
error be a bug?
Maybe something is missing in systemd deps but I'm no expert to debug it. There
is a valid config and network is brough up after yast without intervention.
However, I cannot restart wicked(d).

Anyway, as you tell me, there is no place in autoyast to run a script in the
installed system context with network. It would be the perfect place to join a
windows domain :-) I don't see "save the settings of the ask section in a 
temporary file" as a solution as it would not allow me to check if the
operation has succeeded (i.e.: password was right). It would be a blind shot.

In the worst case, it is a regression for me as it worked for OS13.1 and before
(I guess since 12.1).

Can I reopen it?