Bug 30313 – Nameserver settings need to be persistent

Bug 30313 - Nameserver settings need to be persistent


Summary:	Nameserver settings need to be persistent

Status:	CLOSED FIXED

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

Importance:	P5 normal
Target Milestone:	UCC 1.0
Assigned To:	Erik Damrose
QA Contact:	Moritz Muehlenhoff

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-02-06 16:01 CET by Moritz Muehlenhoff
Modified:	2013-03-26 09:14 CET (History)
CC List:	0 users

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 Moritz Muehlenhoff

2013-02-06 16:01:19 CET

Otherwise during image update the LDAP server cannot be resolved.

Comment 1 Moritz Muehlenhoff

2013-02-06 16:09:31 CET

/etc/resolv.conf was added to the list of persistent files.

Comment 2 Erik Damrose

2013-02-07 12:57:29 CET

This does not fix the issue. The resolv.conf is being rewritten while syncing back the persistent ucr variables, and e.g. the persistent variable domainname causes the resolv.conf to be rewritten.

To fix this the ucr variables nameserver{1,2,3} should be made persistent.

Comment 3 Erik Damrose

2013-02-07 13:04:28 CET

The variables have been added in univention-join_1.1.13-1

Comment 4 Moritz Muehlenhoff

2013-02-15 10:25:18 CET

The nameserver variables are now tracked as persistent.

Comment 5 Moritz Muehlenhoff

2013-03-26 09:14:09 CET

UCC 1.0 has been released: 
http://forum.univention.de/viewtopic.php?f=26&t=2417
http://forum.univention.de/viewtopic.php?f=54&t=2418

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