Univention Bugzilla – Full Text Bug Listing |
Summary: | App appliance creation for UCS 4.2 | ||
---|---|---|---|
Product: | UCS | Reporter: | Erik Damrose <damrose> |
Component: | General | Assignee: | Erik Damrose <damrose> |
Status: | CLOSED FIXED | QA Contact: | Jürn Brodersen <brodersen> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, gulden, klaeser |
Version: | UCS 4.2 | ||
Target Milestone: | UCS 4.2-1-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: |
https://forge.univention.org/bugzilla/show_bug.cgi?id=44575 http://forge.univention.org/bugzilla/show_bug.cgi?id=44736 |
||
What kind of report is it?: | Feature Request | 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): | Appliance | |
Max CVSS v3 score: | |||
Bug Depends on: | 43671, 44575, 44995 | ||
Bug Blocks: | 44952, 44956 |
Description
Erik Damrose
2017-05-02 12:55:04 CEST
r79004 update with latest scripts from 4.1-4, remove already merged "-beta" files r79006 merge utils/base-appliance.sh r79007 Update config to ucs 4.2 r79081 adjustments to univention-app-appliance r79083 yaml r79094 Adapt ucs-kt-instance-create to support downloading images ucs-kvm-testenv 1.2.49-7.81.201705041818 As discussed, a part of the QA can start from my perspective - checking if installation is possible with the kopano-core appliance in different system roles and into AD If I try to join the appliance as a backup the package univention-fetchmail-schema gets installed on the backup before the join starts and breaks slapd.conf. The join fails. several revision before this one... r81378 create all appliance variants; reactivated vmware + esxi creation fixed for now. All appliance types can be created. For follow up issues, new bugs will be created I noticed some small thinks: The AD-join is deactivated for kopano. Is that intended? The owncloud appliance can only join as a backup. Joining as a slave does not install the app? The English owncloud first steps help still has some html in it. Already discussed: The kopano appliance can't join a domain because of the fetch mail package. The owncloud appliance has no fast demo mode. What I tested: Installed appliances as a master and checked basic app functionality. Installed owncloud as an AD member and checked basic app functionality. Installed owncload as a backup and checked basic app functionality. I joined a backup into a kopano appliance which was installed as master. I then tried to upgrade that backup to a master which was a bit cumbersome because of the special master packages from kopano. But I guess that doesn't happen very often and isn't really an appliance problem. (In reply to Jürn Brodersen from comment #8) > The owncloud appliance can only join as a backup. Joining as a slave does > not install the app? ''' Waiting for activation of the extension object owncloud:....................................................ERROR: Master did not mark the extension object active within 180 seconds. Registering schema file /usr/share/univention-appcenter/apps/owncloud/owncloud.schema failed Aborting... ERROR Going to remove ownCloud (10.0.1-20170523) ''' It seems adding the ldap extension during the join is the problem here. I can install the app, after the join is complete, without problems and I can't find any errors on the master that the extension failed. Maybe it really is a timeout issue because the master is to busy with the join? Already released. |