Page 1 of 1

Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 13, 2018 8:34 am
by msquadrat
Hi folks,

just a quick heads up: I just tried to upgrade our first 8.8.8 test system to 8.8.9 (based on Ubuntu 16.04) and it failed due to a package conflict. The install.log says

Code: Select all

dpkg: considering removing zimbra-mbox-admin-common in favour of zimbra-mbox-admin-console-war ...
Package zimbra-mbox-admin-common is on hold, not touching it.  Use --force-hold to override.
dpkg: regarding .../zimbra-mbox-admin-console-war_1.0.0.1528703004-1.u16_amd64.deb containing zimbra-mbox-admin-console-war:
 zimbra-mbox-admin-console-war conflicts with zimbra-mbox-admin-common
  zimbra-mbox-admin-common (version 1.0.0.1521723166-1.u16) is present and installed.

dpkg: error processing archive /usr/local/src/zcs-NETWORK-8.8.9_GA_2055.UBUNTU16_64.20180703080917/packages/zimbra-mbox-admin-console-war_1.0.0.1528703004-1.u16_amd64.deb (--install):
 conflicting packages - not installing zimbra-mbox-admin-console-war
 …
 Configuring zimbra-network-modules-ng
Checking mailboxd running.
mailboxd is not running.
Mailbox is not running...

Please deploy zimlets after starting up the mailbox.
Run as zimbra user
zmzimletctl -l deploy /opt/zimbra/zimlets/com_zextras_zextras.zip
zmzimletctl -l deploy /opt/zimbra/zimlets/com_zextras_client.zip
zmmailboxdctl restart
Errors were encountered while processing:
 /usr/local/src/zcs-NETWORK-8.8.9_GA_2055.UBUNTU16_64.20180703080917/packages/zimbra-mbox-admin-console-war_1.0.0.1528703004-1.u16_amd64.deb


The installer ends with

Code: Select all

ERROR: Unable to install required packages
WARNING: REMOTE PACKAGE INSTALLATION FAILED.
To proceed, review the instructions at:
https://wiki.zimbra.com/wiki/Recovering_from_upgrade_failure
Failure to follow the instructions on the wiki will result in complete data loss.


I'll see how good that linked document is and try to find out what the actual issue was. Luckily this was only a test system :-)

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 13, 2018 9:08 am
by msquadrat
Ok, I found the error and got the system up and running again based on the linked article (and ignoring the scary warnings about the hosed license file).

The core issue: Since the switch to package updates from the repos we pin all Zimbra packages on Ubuntu via

Code: Select all

apt-mark hold 'zimbra-*'

to avoid accidental/unexpected updates of Zimbra packages. (On CentOS we use yum-versionlock to do the same.)

To update Zimbra packages we then run

Code: Select all

apt-get upgrade --ignore-hold --only-upgrade 'zimbra-*'


Since the install.sh doesn't make use of --ignore-hold I ran into the issue at hand. Had I read our documentation properly I'd have run the required command

Code: Select all

apt-mark unhold 'zimbra-*'

before the upgrade.

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Thu Jul 26, 2018 12:33 pm
by andreaswolske
Hi,
msquadrat wrote:just a quick heads up: I just tried to upgrade our first 8.8.8 test system to 8.8.9 (based on Ubuntu 16.04) and it failed due to a package conflict. The install.log says


... same here on RHEL/CentOS 7.x The upgrade failed with RPM dependency errors:

Code: Select all

error: Failed dependencies:
zimbra-common-core-jar >= 1.0.0.1531215702 is needed by (installed) zimbra-patch-8.8.8.7.1531521983-2.r7.x86_64


Manually removing the the patch did the trick:

Code: Select all

rpm -e --nodeps zimbra-patch-8.8.8.7.1531521983-2.r7.x86_64
./install.sh --force-upgrade --skip-activation-check --skip-upgrade-check


HTH

Andreas

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 27, 2018 1:56 pm
by milauria
I got the same problem and fixed it with you suggestion
Thanks for the tip !

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 27, 2018 2:36 pm
by L. Mark Stone
andreaswolske wrote:Hi,
msquadrat wrote:just a quick heads up: I just tried to upgrade our first 8.8.8 test system to 8.8.9 (based on Ubuntu 16.04) and it failed due to a package conflict. The install.log says


... same here on RHEL/CentOS 7.x The upgrade failed with RPM dependency errors:

Code: Select all

error: Failed dependencies:
zimbra-common-core-jar >= 1.0.0.1531215702 is needed by (installed) zimbra-patch-8.8.8.7.1531521983-2.r7.x86_64


Manually removing the the patch did the trick:

Code: Select all

rpm -e --nodeps zimbra-patch-8.8.8.7.1531521983-2.r7.x86_64
./install.sh --force-upgrade --skip-activation-check --skip-upgrade-check


HTH

Andreas


Andreas,

Just to be clear, are you saying that the 8.8.9 installer endeavors to deploy a zimbra-common-core-jar version of a lesser number than that installed/required by 8.8.8 Patch7?

Worth opening a Support Case for that for sure if I understand it correctly.

Thanks,
Mark

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 27, 2018 3:11 pm
by andreaswolske
Hi Mark,

L. Mark Stone wrote:
Andreas,

Just to be clear, are you saying that the 8.8.9 installer endeavors to deploy a zimbra-common-core-jar version of a lesser number than that installed/required by 8.8.8 Patch7?
Worth opening a Support Case for that for sure if I understand it correctly.

Thanks,
Mark


I don't think so. The information I can see in /tmp/install* points to zimbra-patch-8.8.8.7.1531521983-2.r7.x86_64.rpm which can't be removed by the installer without violating other package dependencies.
Removing the patch was just a quick workaround to get to update done.
The problem from my point of view is, that the installer does not check if patch rpms are present and tries to remove zimbra-common-core-jar* beforehand which can't be done without removing zimbra-patch-* with the very same command. It seems to me that the error is rather to be found in packages.sh (installer). I'll look into it and keep you posted.

Have a great weekend.

BR

Andreas

Re: Upgrade from 8.8.8p6 to 8.8.9 failed

Posted: Fri Jul 27, 2018 3:14 pm
by L. Mark Stone
If you have a Network Edition system you can use to access the Support Portal and file a bug report, please do so once you are ready. If not, please post the results of your discovery and I can do the same.

Zimbra have committed to me that they do monitor these forums for important bugs impacting multiple users, but wouldn't hurt to raise an issue like this formally as well.

Mark