Bug 39551 - missing univention-run-join-scripts in docker-container-mode update scripts
missing univention-run-join-scripts in docker-container-mode update scripts
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Docker
UCS 4.1
Other Linux
: P1 normal (vote)
: UCS 4.1-2-errata
Assigned To: Dirk Wiesenthal
Felix Botner
:
Depends on:
Blocks: 41286 41954
  Show dependency treegraph
 
Reported: 2015-10-15 10:48 CEST by Felix Botner
Modified: 2016-08-09 22:50 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
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:
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 Felix Botner univentionstaff 2015-10-15 10:48:27 CEST
After updating a container there are unconfigured join scripts.

All update scripts in univention-docker-container-mode should call univention-run-join-scripts with the proper credentials.
Comment 1 Stefan Gohmann univentionstaff 2015-10-15 16:08:31 CEST
As discussed we need an interface if join scripts need to be executed. This is needed because the docker container will install errata updates automatically.
Comment 2 Dirk Wiesenthal univentionstaff 2016-07-22 12:42:58 CEST
Added the script in
  univention-docker-container-mode 1.0.12-3.58.201607221238

(basically "univention-run-join-scripts; univention-check-join-status")

Added the execution code in
  univention-appcenter 5.0.21-28.200.201607221241
Comment 3 Dirk Wiesenthal univentionstaff 2016-07-25 10:17:07 CEST
I have put univention-run-join-scripts into the update_packages script
  univention-docker-container-mode 1.0.12-4.59.201607251006
  univention-appcenter 5.0.21-29.201.201607251015
Comment 4 Felix Botner univentionstaff 2016-07-25 14:02:09 CEST
OK - run join scripts during software update
   (c -> container, h -> host)
   c -> univention-install univention-appcenter=5.0.21-25.197.201607191724
   c -> univention-upgrade --check --setucr
   c -> ucr get update/available
    yes
   h -> univention-app upgrade-search dudle
   h -> ucr get appcenter/apps/dudle/update/available 
    yes
   h -> univention-app info
    UCS: 4.1-2 errata220
    App Center compatibility: 4
    Installed: dudle=1.1.0-1
    Upgradable: dudle
   h -> univention-app upgrade dudle
    ...
    Running 30univention-appcenter.inst skipped (already executed)
    Joined successfully
    ...
   c -> univention-check-join-status
    Joined successfully

OK - run join scripts if only univention-check-join-status fails
   c -> univention-check-join-status
   c -> ucr get update/available
    no
   h -> univention-app upgrade-search dudle
   h -> univention-app info
    UCS: 4.1-2 errata220
    App Center compatibility: 4
    Installed: dudle=1.1.0-1
    Upgradable: dudle
   h -> ucr get appcenter/apps/dudle/update/available 
    yes
   h -> univention-app upgrade dudle
    ...
    Running 30univention-appcenter.inst done
    Joined successfully
    Container is already running
    ...
   c -> univention-check-join-status
    Joined successfully

OK - YAML

I have no idea who calls "univention-upgrade --check --setucr" in the container to update update/available and who calls "univention-app upgrade-search dudle" on the host to update appcenter/apps/dudle/update/available on the host, and there currently is no UMC integration.