Bug 45486 – UDM objects aren't robust against multiple operations

Bug 45486 - UDM objects aren't robust against multiple operations


Summary:	UDM objects aren't robust against multiple operations

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UDM maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-05 11:14 CEST by Florian Best
Modified:	2020-06-22 18:37 CEST (History)
CC List:	1 user (show)

See Also:	45468
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
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 Florian Best

2017-10-05 11:14:16 CEST

UDM objects aren't robust against multiple operations, e.g.
If you .modify() an object twice some extended attributes might be removed.

See also Bug #45468 comment 3 and comment 4.

We should make sure that after any operation like create(), modify(), move() and remove() the internal state is correct again.

Comment 1 Daniel Tröder

2017-10-06 11:01:59 CEST

I think that'd be rather expensive, as it'd require fetching the object again and running open(). At least when UDM hooks are registered for a module.

So I suggest to make this optional, by for example adding a "refresh()" method.

Comment 2 Florian Best

2017-10-06 11:09:38 CEST

Jeah, I thought about a reopen() method.
We could fetch the object again with a post-read-control as we already do in the S4 Connector.