Installer change proposal

Ask questions about your setup or get help installing ZCS server (ZD section below).
Post Reply
User avatar
gabrieles
Outstanding Member
Outstanding Member
Posts: 233
Joined: Tue Feb 14, 2017 9:40 am

Installer change proposal

Post by gabrieles »

Hi all.
we, like you all, are still feeling the burns from the blastwave of the P32.
We have tens of customers stuck, they don't want absolutely to install P32, and at the same time, can't install new servers.
It's an old problem and one of the weirdest thing IMHO of this all: you can't install a fresh ZCS without having to deal with the last patch, tested or not tested, stable or not.

It's weird, not only customers don't want to upgrade to a toxic patch, but either we can't install alternative servers!
If we want to debug the process of patching from a low level patch to a P32, we can't because it is not possible a fresh install without the last patch.
If we have a particular customer that can't upgrade, and want to build up a parallel staging infrastructure to reproduce issues, you can't.
Yes, tecnhically you can, but downgrading is a hell, especially when dealing with core packages.

Even the NG modules, on a fresh install, are installed as an old version (and you have to yum/apt upgrade after install). It is unstable, and bugged, but you can choose what version upgrade to.

It's not the first time that a we plan something with a customer (upgrade/rolling upgrade/fresh install) and everything blows up for a toxic patch, and must be postponed to who-knows-when (hoping that the new date will not coincide with another toxic release!!!).

Am I the only one that would prefer a zimbra-patch-p0 hardcoded at install time? What am I missing of the big plan?
Post Reply