Bug 34610 – always add cryptsetup to initrd

Bug 34610 - always add cryptsetup to initrd


Summary:	always add cryptsetup to initrd

Status:	CLOSED FIXED

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	initrd
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	UCC 2.0
Assigned To:	Felix Botner
QA Contact:	Moritz Muehlenhoff

URL:
Keywords:	interim-2

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-04-23 14:18 CEST by Felix Botner
Modified:	2014-06-12 09:20 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2014-04-23 14:18:49 CEST

Comment 1 Felix Botner

2014-04-23 14:20:18 CEST

In UCC 1.0 crypsetup was available in the initrd but not with UCC 2.0. Better we always add the crypsetup tools to the initrd.

Comment 2 Felix Botner

2014-04-23 15:48:31 CEST

added 

more initramfs-tools/conf-hooks.d/ucc 
# always include cryptsetup
# https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730
export CRYPTSETUP=y

to univention-ucc-initramfs

no changelog entry necessary, regression in UCS 2.0

Comment 3 Moritz Muehlenhoff

2014-04-28 13:55:23 CEST

The crypto hooks are correctly added. No changelog needed, since it fixes an upstream regression compared to UCC 1.0.

Comment 4 Moritz Muehlenhoff

2014-06-12 09:20:06 CEST

UCC 2.0 has been released:
 http://docs.univention.de/release-notes-ucc-2.0.html

If this error occurs again, please use "Clone This Bug".