Bug 305105

Summary: boot.crypto insserv -r'd after update
Product: [openSUSE] openSUSE 10.3 Reporter: Christian Boltz <suse-beta>
Component: Update ProblemsAssignee: Thomas Fehr <fehr>
Status: VERIFIED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: lnussel
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Christian Boltz 2007-08-28 00:45:47 UTC 
updating 10.2 to 10.3 beta2, using Factory tree

It seems something[tm] run   insserv -r boot.crypto

Result: I was no longer asked for the passphrase to mount my encrypted partition on boot.

After   insserv boot.crypto   it works again - but it should never have been removed.

y2logs: http://www.cboltz.de/tmp/y2logs-103b2.tar.bz2 (too large for bugzilla)
Comment 1 Ludwig Nussel 2007-08-29 12:33:46 UTC 
boot.crypto moved from aaa_base to cryptsetup and therefore the symlink gets removed when updating aaa_base. The cryptsetup package however cannot know that and therefore doesn't enable boot.crypto. yast however knows when updating from <= 10.2 to 10.3. Since previously boot.crypto got enabled unconditionally on every update of aaa_base it should be fine for yast to unconditionally enable boot.crypto when upgrading from distros <= 10.2. OTOH yast needs to rewrite crypttab anyways so it can actually guess when enabling boot.crypto makes sense.
Comment 2 Katarina Machalkova 2007-08-30 08:26:11 UTC 
y2-storage issue (Thomas?)
Comment 3 Thomas Fehr 2007-08-30 09:40:58 UTC 
It is not the case that YaST2 rewrites /etc/cryptotab during update.
boot.crypto needs still to be able to handle /etc/cryptotab.
On a 10.2 system there is no /etc/crypttab.

Added explicit call to "/sbin/insserv /etc/init.d/boot.crypto" to update code
when updating from <=10.2.
Comment 4 Ludwig Nussel 2007-08-30 10:30:48 UTC 
Arent't you rewriting fstab due to the hda->sda move? If so the same has to be done for cryptotab, no?
Comment 5 Thomas Fehr 2007-08-30 10:35:22 UTC 
This is done only when disk device names have changed, but it is unrelated to the
crypto changes between 10.2 and 10.3 and this code is not new in 10.3 but is 
there much longer.
Comment 6 Christian Boltz 2008-08-10 22:31:31 UTC 
Even if I'm late: verified, did not happen again :-)