Bug 33523 – new standard container not found until logout/login

Bug 33523 - new standard container not found until logout/login


Summary:	new standard container not found until logout/login

Status:	CLOSED DUPLICATE of bug 33651

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.2
Hardware:	All Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2-x
Assigned To:	UMC maintainers
QA Contact:	Florian Best

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-21 18:00 CET by Philipp Hahn
Modified:	2023-03-25 06:53 CET (History)
CC List:	3 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 Philipp Hahn

2013-11-21 18:00:29 CET

UCS technical training, UCS-3.2-0

Adding an additional standard container (for users) is not found when adding a new (user) object immediately afterwards. Only after a logout/login cycle is the new default container show in the (use) wizard.

If I remember correctly that was working in UCS-3.1-1, so to me it looks like it is related to the new UMC caching?

Comment 1 Alexander Kläser

2013-11-26 13:24:55 CET

(In reply to Philipp Hahn from comment #0)
> ...
> If I remember correctly that was working in UCS-3.1-1, so to me it looks
> like it is related to the new UMC caching?

Yes, this is very likely.

Comment 2 Philipp Hahn

2014-01-13 09:38:21 CET


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