Hi, after my latest debugging of installer failure I found one important thing how clients works in Yast. It behaves like scripts, but with one big difference -> if invoked via WFM.Call then it is not completelly thrown away. It have benefits like storing some data, but one big drawback. You can mess global namespace during run of script. And exactly this happen in the latest issue. I use `include Yast` on top level and it includes all modules to global namespace. Result is collision between Yast::FileUtils and ::FileUtils in ruby, which is used for file manipulation. So my general recommendation is to not use global namespace in scripts and also in other places, otherwise you risk collission with ruby own libraries. Example of my fix can be seen in [1] Josef [1] https://github.com/yast/yast-network/pull/135 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org