Kopano-meet update to 1.2.1_0-2 fails

Apps & App Center
#1

When trying to update kopano-meet the update fails either via command line or web gui with the following error:


Failed to configure: Kopano Meet: kopano/docker/INSECURE: None is not a valid option
Failed to configure: Kopano Meet: kopano/docker/INSECURE: None is not a valid option
#2

Hi @raceface2nd,

ist that a message that is printed by a container or does it comes from UCS? Can you post your appcenter.log?

#3

This message has been printed while executing univention-app upgrade kopano-meet.

Here is an extract of the log:

Starting kopano_kwmserver ...  done 
   
Starting kopano_grapi     ...  done 
   
Starting web              ...  done 
   
Starting kopano_kapi      ...  done 
   
Starting kopano_meet      ...  done 
   
Starting kopano_ssl       ...  done 
   
Starting kopano_konnect   ...  done 
 
 19049 actions.start.progress           20-02-09 20:26:26 [   DEBUG]: 100
 19049 docker.base.container.b567       20-02-09 20:26:29 [   DEBUG]: Using container.b567 for container b5677e7808fb57bf5b6e6a329b6df5179f04f7d5d2c5506f967eb5923540c08d
 19049 docker.base.container.b567       20-02-09 20:26:29 [   DEBUG]: Calling docker exec -u root b5677e7808fb57bf5b6e6a329b6df5179f04f7d5d2c5506f967eb5923540c08d rm -f /etc/timezone /etc/localtime
 19049 docker.base                      20-02-09 20:26:29 [    INFO]: Running command: docker cp /etc/timezone b5677e7808fb57bf5b6e6a329b6df5179f04f7d5d2c5506f967eb5923540c08d:/etc/timezone
 19049 docker.base                      20-02-09 20:26:30 [    INFO]: Running command: docker cp /etc/localtime b5677e7808fb57bf5b6e6a329b6df5179f04f7d5d2c5506f967eb5923540c08d:/etc/localtime
 19049 actions.configure                20-02-09 20:26:32 [   DEBUG]: Calling configure
 19049 actions.configure.progress       20-02-09 20:26:32 [   DEBUG]: 0
 19049 actions.configure                20-02-09 20:26:32 [    INFO]: Configuring 4.3/kopano-meet=1.2.1_0-2
 19049 settings                         20-02-09 20:26:32 [    INFO]: Unsetting kopano/docker/TURN_USER
 19049 settings                         20-02-09 20:26:32 [    INFO]: Setting kopano/docker/FQDN_MEET to 'domain.anonymized'
 19049 settings                         20-02-09 20:26:32 [    INFO]: Setting kopano/docker/FQDN_SSO to 'ucs-sso.domain.anonymized'
 19049 actions.configure                20-02-09 20:26:32 [CRITICAL]: Failed to configure: Kopano Meet: kopano/docker/INSECURE: None is not a valid option
 19049 actions.configure.progress       20-02-09 20:26:32 [   DEBUG]: 100
 19049 packages                         20-02-09 20:26:32 [   DEBUG]: Releasing LOCK
 19049 actions.upgrade                  20-02-09 20:26:32 [CRITICAL]: Failed to configure: Kopano Meet: kopano/docker/INSECURE: None is not a valid option
 19049 actions.upgrade                  20-02-09 20:26:32 [ WARNING]: Aborting...
 19049 utils                            20-02-09 20:26:32 [   DEBUG]: send_information: action=upgrade app=kopano-meet value=None status=413
 19049 utils                            20-02-09 20:26:32 [   DEBUG]: tracking information: {'status': 413, 'uuid': 'e3b9c70c-8cef-4dc8-8c13-51b9becbdcf3', 'app': u'kopano-meet', 'version': u'1.2.1_0-2', 'role': 'domaincontroller_master', 'action': 'upgrade', 'system-uuid': '49d7bf26-4a01-49f6-a3e0-e3ca75c0203e'}
 19049 actions.upgrade-search           20-02-09 20:26:32 [   DEBUG]: Calling upgrade-search
 19049 actions.upgrade-search.progress  20-02-09 20:26:32 [   DEBUG]: 0
 19049 actions.upgrade-search           20-02-09 20:26:32 [   DEBUG]: Checking 4.3/kopano-meet=1.2.1_0-2
 19049 actions.upgrade-search           20-02-09 20:26:32 [    INFO]: Executing interface update_available for kopano-meet
 19049 actions.upgrade-search           20-02-09 20:26:32 [    INFO]: No interface defined
#4

hm… so he fails setting kopano/docker/INSECURE during configure. Which is strange since the value both has a default value already set and also already did exist prior to this.

I saw something similar, but with another option once in my test environment. For me the app was still installed and going into the settings did properly configure the app.

Can you post the output of ucr dump | grep kopano/docker | grep -v PASSWORD?

#5

Update: I decided to initialise these ucr variables already in the preinst script going forward, this way they will always be set when the app is calling configure.

On your local system you could execute the following:

eval "$(ucr shell)"
ucr set \
        kopano/docker/INSECURE?'no' \
        kopano/docker/GRID_WEBAPP?'no' \
        kopano/docker/MEET_GUEST_ALLOW?'no' \
        kopano/docker/MEET_GUEST_REGEXP?'^group/public/.*' \
        kopano/docker/FQDN_MEET?"$hostname.$domainname" \
        kopano/docker/FQDN_SSO?"$(ucr get ucs/server/sso/fqdn)"

This will enable you to install/update the app.

Edit: change is in https://stash.z-hub.io/projects/K4U/repos/kopano-apps/commits/02615972c8e26960d909f81dd91db2347b681026

Mastodon