Hi all, recently I was debugging a reported bug in AutoYaST and it turned out that the YaST log does not match the used AutoYaST profile, the log complained about some wrong custom script but the attached profile did not define anything like that. In this case we could relatively easily find out that the attached profile was not the profile which was really used by AutoYaST. But in other cases it might be more difficult or even impossible. We cannot log the whole AY profile for security reasons (it might contain registration keys, user passwords or other sensitive data) so I slightly improved logging in the "master" branch. Now AutoYaST logs the SHA1 checksum of the profile and rules or classes files if they are used. Then you can easily get the checksum of the attached profile by using a command like "sha1sum autoyast.xml". The checksum must be the same as logged by YaST, simple "grep SHA1 y2log" should find it. If the checksum is not the same than the file used by YaST was different. (Note: This compares the files bitwise, e.g. adding a newline at the end of a XML file does not change the logical content but the SHA1 will be completely different. But as you cannot be sure what users actually changed it should be always a good idea to ask for the real file.) See more details in the GitHub pull request https://github.com/yast/yast-autoinstallation/pull/857 -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8