Bug 36272 - Move delete and edit into the UMC module
Move delete and edit into the UMC module
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Virtual machines (UVMM)
UCS 4.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-22 15:16 CEST by Stefan Gohmann
Modified: 2023-06-28 10:51 CEST (History)
5 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.023
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:
best: Patch_Available+


Attachments
Add edit functionality (11.46 KB, patch)
2014-10-30 16:02 CET, Dirk Wiesenthal
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-10-22 15:16:55 CEST
Currently, the UVMM UMC module uses the UDM cloud connection module for modifying and removing a cloud connection. For the creation a wizard is used.

The UMC module should not switch to the UDM module because it makes the usability difficult.
Comment 1 Dirk Wiesenthal univentionstaff 2014-10-30 15:57:38 CET
Not for UCS 4.0 anymore.
Comment 2 Dirk Wiesenthal univentionstaff 2014-10-30 16:02:01 CET
Created attachment 6266 [details]
Add edit functionality

This is how far I have come.

There is still an issue with the UDM call (the None in modlist is wrong).

But the real issue here is that I did not find a way to edit connections on the fly. Removing and adding a new one seems to be the easiest way but this is tricky as a misconfiguration in the new connections should re-add the old connection - which requires parameter that I do not have anymore (probably need to read from LDAP).

Alternatively one could just restart uvmmd (which re-reads LDAP) but this causes tracebacks when there is a concurrent request because the socket does not exist for a short time.
Comment 3 Florian Best univentionstaff 2014-11-25 16:31:03 CET
hm, maybe it is better to use the ldap connection from the user (as UDM does it) not the machine connection!
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:16: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.