action #67543
closed
Upgrade Test from invis-Server 14.1 to 14.3 (14.2 wird nicht veröffentlicht)
Added by flacco almost 4 years ago.
Updated 3 days ago.
Description
Test an direct upgrade from invis-server 14.1 based on Leap 15.1 to invis-Server 14.3 based on Leap 15.3
It is necessary to do the distribution upgrade step by step: 15.1 -> 15.2 -> 15.3
Before release of 14.2 we should do an upgrade test from 14.1 to 14.2 based on leap 15.1.
14.2 should be just a feature and bugfix release, but to be compatible with the upcoming leap 15.2 we had to build new samba and sssd packages which are much newer than the distribution packages. Installing the invisAD-setup-14 (14.2) package forces an upgrade of sssd and samba. This means a release without a upgrade test is dangerous.
Perhaps we should ship 14.2 as an intermediate package on the way to invis-server 15.0 just like 13.5 was.
Related issues
1 (1 open — 0 closed)
- Category changed from Feature to Test
- Description updated (diff)
- Subject changed from Upgrade Test from invis-Server 14.2 to 14.3 to Upgrade Test from invis-Server 14.1 to 14.2
- Status changed from New to Feedback
The other possibility is to renumber 14.2 to 15.0.
Feedback wanted!
I think 14.1 to the 14.2 is an update, not an upgrade. Thus 14.2 is a 14.2, not an 15. Samba is our package, only updated. sssd and chrony are no changes that I think we change the mayor version number, because these do not break any "APIs" or make something incompatible with the 14.1.
- Status changed from Feedback to In Progress
- % Done changed from 0 to 20
- Subject changed from Upgrade Test from invis-Server 14.1 to 14.2 to Upgrade Test from invis-Server 14.1 to 14.3 (14.2 wird nicht veröffentlicht)
- Due date changed from 2020-06-06 to 2021-10-31
- Target version changed from 14.2 to 14.3
- Description updated (diff)
- % Done changed from 20 to 0
Progress zurück auf 0% gesetzt.
- Description updated (diff)
- Due date changed from 2021-10-31 to 2024-04-30
14.3 noch nicht ganz fertig
- Status changed from In Progress to Workable
Wir sind mittlerweile natürlich auch bei Leap 15.5 angekommen.
Bin mir daher nicht sicher, ob ein Upgrade nicht mehr Arbeit macht, als eine Neuinstallation mit anschließender Migration. Letzteres mache ich in der Praxis fast immer, da es auch die Möglichkeit gibt einen Server mit neuen Festplatten auszustatten.
Hinzu kommt, dass wir auch unsere Leap 15.2 Repos gelöscht haben.
Tests zumindest bis Leap 15.4 habe ich erfolgreich durchgeführt.
- Status changed from Workable to Rejected
Wegen des inzwischen großen Abstands zwischen 14.1 und 14.3 raten wir generell von Upgrades ab. Statt dessen ist die Empfehlung eine Neuinstallation mit anschließender Datenmigration. Hat sich x-fach bewährt.
Also available in: Atom
PDF