Bug 43882 - Disable domain-join (and executing pending join scripts) during univention-upgrade
Disable domain-join (and executing pending join scripts) during univention-up...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Domain join
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on: 33793
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-15 17:17 CET by Arvid Requate
Modified: 2019-01-03 07:22 CET (History)
4 users (show)

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):
Max CVSS v3 score:
requate: Patch_Available+


Attachments
updater_or_dpkg_lock.patch (1.60 KB, patch)
2017-03-15 17:17 CET, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-03-15 17:17:08 CET
Created attachment 8545 [details]
updater_or_dpkg_lock.patch

During research for Bug #43625 I found that univention-management-console-module-join doesn't check if univention-upgrade is running. It just checks if /var/lib/dpkg/status is locked at one point in time.

The attached patch may give an idea how to fix this.



+++ This bug was initially created as a clone of Bug #33793 +++

If an app is installed, there is a short time window where to join script are already installed but not executed (package is extracted but not installed). If the domain join module is opened in this time window, the module complains about pending join-script. But this is not the right moment to execute these script since the packages are not fully installed/configured.

Better to disable the join module during an app installation.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:22:41 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.