Bug 30595 – Consider read-only flag

Bug 30595 - Consider read-only flag


Summary:	Consider read-only flag

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Univention Configuration Registry
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Duplicates:	22757 (view as bug list)
Depends on:
Blocks:	23354
	Show dependency tree / graph

Reported:	2013-02-26 20:04 CET by Stefan Gohmann
Modified:	2019-01-03 07:17 CET (History)
CC List:	2 users (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 Stefan Gohmann

2013-02-26 20:04:57 CET

The UCR module should consider the read only flag:

See Bug #23354 for details:

(In reply to comment #2)
> Die ReadOnly-Funktionalität wurde zu UCS-3.0 wieder aus UMC entfernt, die über
> Bug #22755 dort eingeführt wurde.
> Entweder die Bugs sind damit hinfällig oder es fehlt ein Bug gegen UMC-UCR-3.1,
> der die Funktionalität erneut implementiert. Ggf. ist das an Bug #23223
> geplant?

Comment 1 Alexander Kläser

2013-03-04 12:00:34 CET

*** Bug 22757 has been marked as a duplicate of this bug. ***

Comment 2 Moritz Muehlenhoff

2014-06-25 09:30:02 CEST

Again noted during a technical training

Comment 3 Moritz Muehlenhoff

2015-02-27 11:33:36 CET

This affects 4.0-1 (noted in a technical training; someone read that the domain cannot be changed subsequently, but was wondering why it could be changed in UCR).

Comment 4 Stefan Gohmann

2019-01-03 07:17:12 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.