Bug 39433 – Docker App is not fully registered after installation

Bug 39433 - Docker App is not fully registered after installation


Summary:	Docker App is not fully registered after installation

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	UMC - App-Center
Version:	UNSTABLE
Hardware:	Other All

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1
Assigned To:	Dirk Wiesenthal
QA Contact:	Stefan Gohmann

URL:
Keywords:	interim-2

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-29 18:04 CEST by Dirk Wiesenthal
Modified:	2015-11-17 12:11 CET (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 Dirk Wiesenthal

2015-09-29 18:04:35 CEST

This happens when installing through the UMC module. IIRC there is Code to automatically Register Apps over and over again when they are queried in the UMC module. This is to "self heal" in case of broken registration, but it fails with Docker: The App LDAP object is deleted after the Backend created it.

Comment 1 Dirk Wiesenthal

2015-10-19 23:48:57 CEST

Don't know when and why, but I think it works now. There were some semi related bugs. I guess I fixed it along with those. No changelog needed, @QA: just check whether registration is complete and persistent.

Comment 2 Stefan Gohmann

2015-10-27 12:32:15 CET

Yes, it looks good.

Comment 3 Stefan Gohmann

2015-11-17 12:11:48 CET

UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

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