Bug 49924 - update_extended_attributes() should be idempotent
update_extended_attributes() should be idempotent
Status: NEW
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-26 16:05 CEST by Florian Best
Modified: 2019-07-26 16:05 CEST (History)
0 users

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): Cleanup
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2019-07-26 16:05:50 CEST
Calling update_extended_attributes() mutliple times should result in a stable outcome.

This is currently not the case, e.g. when removing a extended attribute from LDAP and calling update_extended_attributes() a second time, the extended attribute is still in module.mapping.
Also module.extended_attribute_tabnames is only cleared once.

Everythink which univention.admin.modules.init() does should be idempotent:
* update_extended_options()
* update_extended_attributes()
* etc.