Bug 44736 - App appliances who join into a UCS domain do not install DefaultPackagesMaster
App appliances who join into a UCS domain do not install DefaultPackagesMaster
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: General
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-02 11:42 CEST by Erik Damrose
Modified: 2019-01-03 07:22 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.103
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017053121000371
Bug group (optional): Appliance
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 2017-06-02 11:42:31 CEST
App appliances who join into a UCS domain do not install DefaultPackagesMaster. If e.g. the kopano appliance is joined as a slave into an existing domain, the fetchmail schema package is not installed on the master, and the domain join will fail.
Comment 1 Florian Best univentionstaff 2017-06-02 11:49:16 CEST
Did you use the VM from Christina? I removed the univention-fetchmail{-schema,} package from it to workaround a failing slapd restart.
Comment 2 Erik Damrose univentionstaff 2017-06-02 12:03:46 CEST
@Comment 1: It was a separate installation. And i looked into the installation code
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:22:04 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.