Bug 36550 - Reinstalling UVMM-daemon package or app does not result in the same (ldap-)state as a new installation
Reinstalling UVMM-daemon package or app does not result in the same (ldap-)st...
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Virtualization - UVMM
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-10 17:48 CET by Erik Damrose
Modified: 2023-06-28 10:46 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.017
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

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2014-11-10 17:48:47 CET
We create the cloud-relevant ldap containers and objects in the uvmm-schema package's joinscript. However, when uninstalling the uvmm-daemon package (or removing its respective app), the uvmm-daemon unjoin script deletes the base container: cn=Virtual Machine Manager,$ldap_base.

As the uvmm-schema package does not get removed, its joinscript is not executed again when reinstalling uvmm-daemon, so the CloudConnection container is not recreated.

This leads to the following traceback when adding a new EC2 connection.

/var/log/univention/management-console-module-uvmm.log
  File "/usr/sbin/univention-management-console-module", line 119, in <module>
    notifier.loop()
  File "/usr/lib/pymodules/python2.7/notifier/nf_generic.py", line 284, in loop
    step()
  File "/usr/lib/pymodules/python2.7/notifier/nf_generic.py", line 276, in step
    __min_timer = dispatch.dispatcher_run()
  File "/usr/lib/pymodules/python2.7/notifier/dispatch.py", line 72, in dispatcher_run
    if not disp():
  File "/usr/lib/pymodules/python2.7/notifier/threads.py", line 154, in _simple_threads_dispatcher
    task.announce()
  File "/usr/lib/pymodules/python2.7/notifier/threads.py", line 135, in announce
    self._callback( self, self._result )
  File "/usr/lib/pymodules/python2.7/notifier/__init__.py", line 104, in __call__
    return self._function( *tmp, **self._kwargs )
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/uvmm/uvmmd.py", line 140, in _finished
    self._user_callback(thread, result)
  File "/usr/lib/pymodules/python2.7/notifier/__init__.py", line 104, in __call__
    return self._function( *tmp, **self._kwargs )
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/uvmm/cloud.py", line 130, in _finished
    ldap_cloud_connection_add(cloudtype, name, parameter, ucs_images, search_pattern, preselected_images)
  File "/usr/lib/pymodules/python2.7/univention/uvmm/uvmm_ldap.py", line 272, in ldap_cloud_connection_add
    lo.add(dn, modlist)
  File "/usr/lib/pymodules/python2.7/univention/admin/uldap.py", line 398, in add
    raise univention.admin.uexceptions.ldapError, _err2str(msg)
ldapError: No such object

The joinscripts should be adapted, and the creation of the relevant containers and objects moved to the uvmm-daemon package.
Comment 1 Erik Damrose univentionstaff 2014-11-10 17:50:01 CET
Workaround: Force-execute the joinscript 40univention-virtual-machine-manager-schema.inst after reinstalling uvmm-daemon
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:17:35 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.