Bug 390719

Summary:	Yast2 bootloader error in clone function
Product:	[openSUSE] openSUSE 10.3	Reporter:	Tamas Sarga <tamas.sarga>
Component:	YaST2	Assignee:	Jozef Uhliarik <juhliarik>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs.tar.gz menu.lst files

Description Tamas Sarga 2008-05-15 11:22:46 UTC

When I tried to clone my existing 10.3 grub entry I chose add button than chose clone radio-button, than chose my existing entry, than did the changes and chose ok.
After it I realized that yast2 created a new entry and modified my already existing entry by the given new parameters.

Comment 1 Robert Vojcik 2008-05-15 12:48:11 UTC

Can you send all yast2 logs ?
If you are unsure follow:
http://en.opensuse.org/Bugs/YaST

Are you use gtk or qt yast interface (kde or gnome) ?

Thanks

Comment 2 Tamas Sarga 2008-05-16 20:32:05 UTC

Yast2 said it can't save y2logs error code 2, but it created the tar.gz, so I attach this.
If it isn't suitable then I can attach my whole /var/log/Yast2 directory in a tar.gz.

Comment 3 Tamas Sarga 2008-05-16 20:34:46 UTC

Created attachment 216102 [details]
y2logs.tar.gz

Comment 4 Jozef Uhliarik 2008-05-19 14:12:33 UTC

I am sure that this is not critical bug but normal bug. (Severity should be decrease)

I just found changing "root" from label "/dev/sda6" to UUID "/dev/disk/by-id/scsi-SATA_WDC_WD2000JB-00WD-WMALL1140913-part6"

Could you write exactly what was modified on already existing sections please?

The perfect would be menu.lst before and after your changes. I tried to reproduce your problem but I was not successful. :(

Comment 5 Tamas Sarga 2008-05-19 17:53:49 UTC

Created attachment 216564 [details]
menu.lst files

Here are 4 menu.lst. in a tar.gz
menu.lst.original is the starting point. I copied it, than I cloned "openSUSE 10.3" entry. The result is in menu.lst.wrong. I changed section name, kernel image, initial ram disk and root device. The last entry openSUSE 11.0 is the cloned entry and the first entry should remain openSUSE 10.3. Than I edited the first openSUSE 11.0 entry and the last were modified. This is menu.lst.nearly.corrected. Than I move the modified entry to the first position give back the default flag to it. This is menu.lst.expected.

Comment 6 Tamas Sarga 2008-05-19 18:02:29 UTC

I don't know what counts as critical bug. I thought that a bug which ccould cause a screwed up system by a theoretically safe clone function was critical, but I accept your choice. Of course the failsafe entry eliminate the risk of the total screwing up. But I'm afraid an end-user could be very confused, if try out something, what results that he can not boot by the default everyday boot entry.

Comment 7 Jozef Uhliarik 2008-05-26 16:59:25 UTC

fixed in version 2.16.17