(In reply to Luiz Angelo Daros de Luca from comment #7) > 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). OK, that could be a bug. Please reopen the bug and assign it to the wickedd maintainer. > > 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. Yes, that's a valid request which we are currently not support. At least in the configuration file. Lets wait what the wickedd maintainer says. If it is not a bug, stay this bug open as an enhancement for the next release. > > 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? Let's do it :-)