Bug 41631 – Add a test for setting ucr variables with the ? operator

Bug 41631 - Add a test for setting ucr variables with the ? operator


Summary:	Add a test for setting ucr variables with the ? operator

Status:	CLOSED DUPLICATE of bug 40728

Product:	UCS Test
Classification:	Unclassified
Component:	UCR
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-2-errata
Assigned To:	Jürn Brodersen
QA Contact:	Philipp Hahn

URL:
Keywords:

Depends on:	40728
Blocks:	40913
	Show dependency tree / graph

Reported:	2016-06-21 17:02 CEST by Jürn Brodersen
Modified:	2016-09-29 17:14 CEST (History)
CC List:	5 users (show)

See Also:
What kind of report is it?:	Development Internal
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
proposed test (1.36 KB, text/plain) 2016-06-21 17:02 CEST, Jürn Brodersen	Details
View All 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 Jürn Brodersen

2016-06-21 17:02:13 CEST

Created attachment 7761 [details]
proposed test

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

UCR variables which are set in LDAP aren't set in base.conf if they get set by a joinscript via variable?value syntax. This might cause problems in unjoinscripts when they get removed again but actually aren't removed. Should we change anything here? Reported in Ticket #2016020821000323.

# ucr set --ldap-policy variable?wert
Create variable
# grep variable /etc/univention/base.conf
# ucr get variable
wert
# ucr set variable?wert
Not updating variable
# ucr unset variable
W: The config registry variable 'variable' does not exist

Comment 1 Jürn Brodersen

2016-06-21 17:25:59 CEST

See r70507

*** This bug has been marked as a duplicate of bug 40728 ***