Hi, Thank you for sending the log files. This happens cause you are using classes for partitioning. When the main control file is not found, autoyast expects a complete control file and will operate in no-class, no-rules mode. The popup complaining about missing control file is just a help for you to determine that your network and autoinstall setup is working. No one wants to get prompted during an automated installation :-) Anas Robert Alonso wrote:

Has anyone else experienced this?

I've got my info file set to point to a directory. Hence, yast should look for the control file first by hex IP address and then 'default'. Well, I forgot to symlink the control file with default, so it couldn't find a control file. So up comes a prompt asking me to explicitly name the file. I enter the name and it begins to process it, but dies when creating partition plans saying that there is an error with the partition plans - please check the syntax of the control file. I tried a few times with the same result. However, when I created 'default' and linked it to the exact same file, it works. So the bug appears to be that although it prompts the user to explicitly name the control file, it doesn't actually process it.

If you have any hints or info, please let me know.

Thanks, Robert

p.s. I also tried explicitly naming the control file in the info file, and that works fine.