Bug 304836

Summary:	Relax-NG validation error on bootloader
Product:	[openSUSE] openSUSE 10.3	Reporter:	Stephan Rickauer <sles>
Component:	AutoYaST	Assignee:	Uwe Gansert <ug>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P4 - Low	CC:	fhassel, sles
Version:	Beta 2
Target Milestone:	---
Hardware:	i386
OS:	openSUSE 10.3
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	XML Validation Error with fresh boot loader config yast log of failure to write boot loader boot loader section of autyast xml2, generated with autoyast 10.3 b2

Description Stephan Rickauer 2007-08-27 13:56:05 UTC

Validation of an autyast.xml file that has been generated with SuSE 10.0 fails on the bootloader part with 10.3. Since it is obvious "something" must have changed between 10.0 and 10.3, I've cleared the entire boot loader part out of the xml file manually. After loading the file into AutoYast it will validate ok.

However, when I then go to Bootloader config and choose to "Configure | Other | Propose new configuration", validation will fail again, though the bootloader section has been generated freshly.

Error message:

/usr/bin/xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng /tmp/YaST2-20863-Fp1ujs/valid.xml
/tmp/YaST2-20863-Fp1ujs/valid.xml:4: element bootloader: Relax-NG validity error : Element profile has extra content: bootloader
/tmp/YaST2-20863-Fp1ujs/valid.xml fails to validate

Comment 1 Stephan Rickauer 2007-08-30 12:19:24 UTC

Created attachment 160947 [details]
XML Validation Error with fresh boot loader config

Comment 2 Stephan Rickauer 2007-08-30 12:22:23 UTC

The above screen shot shows the validation error with a _fresh_ autoyast file, once the boot loader config has been added. This means the issue is independent from importing an old file as previously reported.

I'll raise priority, since our Institute currently can't continue testing the auto installation, due to this bug.

Comment 3 Uwe Gansert 2007-08-30 12:51:08 UTC

why can't you continue testing? it's actually more a warning than an eror and nothing bad happened that might stop you from using autoyast.

Comment 4 Stephan Rickauer 2007-08-30 13:14:21 UTC

Because the file that is generated with AutoYaST (the one that doesn't validate) will not finish the auto installation. It stops with a boot loader error. Thus, I was/am assuming the problem of the failing validation is linked to the failing auto installation. Both deal with boot loader problems.

I'll post a screen shot in a couple of minutes.

Comment 5 Stephan Rickauer 2007-08-30 13:41:17 UTC

Well, the message isn't such complicated to justify a screen shot ;) It says: "An error ocurred during boot loader installation. Retry boot loader configuration?"

Comment 6 Uwe Gansert 2007-08-30 13:51:08 UTC

okay, but that is independent from the validation error (at least I think so).
attach the bootloader section and the /var/log/YaST2/y2log file when the error pops up please

Comment 7 Stephan Rickauer 2007-08-31 09:57:55 UTC

Created attachment 161177 [details]
yast log of failure to write boot loader

Comment 8 Stephan Rickauer 2007-08-31 10:01:27 UTC

Created attachment 161180 [details]
boot loader section of autyast xml2, generated with autoyast 10.3 b2

Comment 9 Uwe Gansert 2007-09-03 09:57:07 UTC

I assume a problem with the software section.
Please set confirm to true and check the proposal screen if every dependency could be resolved or if the resolver throws an error.
If the resolver run is okay, then make sure that you have the pattern "yast-installation modules" chosen. If you did that too and still have problems, please attach the complete autoyast profile (you can x-out root password)

Comment 10 Stephan Rickauer 2007-09-04 13:40:02 UTC

you were right, it is a software section problem. Thanks for your help.

Comment 11 Stephan Rickauer 2007-09-04 13:42:22 UTC

Ups, shouldn't have closed the bug. Reopening, but setting priority to low and severity to minor, since it doesn't stop me from testing any further.

Comment 12 Uwe Gansert 2007-09-14 11:18:52 UTC


*** This bug has been marked as a duplicate of bug 211014 ***