Bug 246684

Summary:	Reading fstab when upgrading
Product:	[openSUSE] openSUSE 10.3	Reporter:	Lukas Ocilka <locilka>
Component:	Update Problems	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	aj
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Lukas Ocilka 2007-02-19 08:48:38 UTC

Copied from bug #245701 comment #2 (Thomas Fehr 2007-02-15 03:22:08 MST):

Update is doing its own fstab reading so if it detects a certain mount-by 
method it needs to put this information into TargetMap, since bootloader 
gets its information from TargetMap.

The mount-by method is specified by the key "mount_by" in the map describing
a partition. This can have the values `device, `id, `path, `label or `uuid.
New default is `id since SLES10 SP1 and SL 10.3 (it was `device before).

Lukas, maybe you should get rid of doing your own fstab analysation in update
code. E.g. there is a function Storage::ReadFstab which gets a directory 
with fstab (and potentially cryptotab) as parameter and returns a list of maps
with read fstab entries. I use this function when doing the "Import existing
fstab" in expert partitoner. No idea if it currently fits you needs but maybe
you should look into using it. If you need any changes just tell me.

BTW this same problem will hit when doing an update from SLES10.

Comment 1 Stefan Fent 2007-02-19 09:06:55 UTC

*** Bug 245701 has been marked as a duplicate of this bug. ***

Comment 2 Berthold Gunreben 2007-02-26 14:19:04 UTC

This always is a problem when updating from a SP release to a newer release. The installer will not be able to mount its root filesystem in this case.

Comment 3 Thomas Fehr 2007-02-26 14:29:27 UTC

y2log files would be necessary, there was a fix in this regard by me on 
last Thursday. Which build did you get this bug?

So far I cannot see how upgrading from any SLES10 SP release to any other release
should differ from an upgrade from SLES9. Mounting a root fs from a SLES10 SP is
not different as mounting a root fs from SLES10 GA or SLES9. 
Either both should work or both should fail. In builds available on Thursday
both failed.

Comment 4 Lukas Ocilka 2007-02-27 07:46:07 UTC

Please, attach y2log

It seems, that the problem, you have mentioned, has been already repaired by Thomas. Update uses this fstab-reading for own (another) purpose.

Comment 5 Berthold Gunreben 2007-02-27 09:27:42 UTC

sorry for the confusion, I obviously fell over a bug in beta1 that has been fixed in beta3.

Comment 6 Lukas Ocilka 2007-02-27 09:35:52 UTC

OK, changing to to enhancement for 10.3.
Such change will not be made for Beta5 in SLES10 SP1.

Comment 7 Lukas Ocilka 2007-08-01 21:06:03 UTC

for 'after 10.3'

Comment 8 Bugzilla Account Maintenance 2008-09-02 18:07:47 UTC

Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."