Bug 36697 – No connection to LDAP server causes image to be always mounted read-writeable

Bug 36697 - No connection to LDAP server causes image to be always mounted read-writeable


Summary:	No connection to LDAP server causes image to be always mounted read-writeable

Status:	CLOSED WORKSFORME

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

Importance:	P5 normal
Target Milestone:	---
Assigned To:	UCC maintainers
QA Contact:

URL:
Keywords:	interim-3

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-14 13:21 CET by Michael Grandjean
Modified:	2023-06-28 10:33 CEST (History)
CC List:	3 users (show)

See Also:	35363
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 Michael Grandjean

2014-11-14 13:21:26 CET

This should be backported to UCC 1.0, but keep Bug #35363 in mind

+++ This bug was initially created as a clone of Bug #31683 +++

The initramfs script ucc mounts the image RO or RW depending on several options. To get the correct setting it calls the script get_boot_mount_option.sh. This script checks the LDAP for a value, then the local ucr config, and returns 'RW' if nothing is configured otherwise.

The script however is executed with 'bash -e'. When trying to determine the LDAP value (by calling univention-ucc-boot-option) and the LDAP server cannot be reached (Because it is down, or because the local network is down, ...), univention-ucc-boot-option exits with an error value, which causes the shellscript to terminate immediately.

get_boot_mount_option.sh should not be started with bash -e.

Comment 1 Moritz Muehlenhoff

2014-12-10 12:09:22 CET

As discussed, we don't plan to backport this to UCC 1.0