Project

General

Profile

Actions

action #67543

closed

Upgrade Test from invis-Server 14.1 to 14.3 (14.2 wird nicht veröffentlicht)

Added by flacco about 4 years ago. Updated 3 months ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Test
Target version:
Start date:
2020-06-01
Due date:
2024-04-30
% Done:

0%

Estimated time:

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 open0 closed)

Related to invisAD-setup - action #98042: Release invis-Server 14.3In Progressflacco2021-09-032024-05-31

Actions
Actions #1

Updated by flacco about 4 years ago

  • Category changed from Feature to Test
Actions #2

Updated by flacco about 4 years ago

  • Description updated (diff)
Actions #3

Updated by flacco about 4 years ago

  • Subject changed from Upgrade Test from invis-Server 14.2 to 14.3 to Upgrade Test from invis-Server 14.1 to 14.2
Actions #4

Updated by flacco about 4 years ago

  • Status changed from New to Feedback

The other possibility is to renumber 14.2 to 15.0.
Feedback wanted!

Actions #5

Updated by ingogoeppert about 4 years ago

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.

Actions #6

Updated by flacco over 3 years ago

  • Status changed from Feedback to In Progress
  • % Done changed from 0 to 20

To prevent upgrade problems i've created a neu samba stable sub-repository in OBS called "413" (https://build.opensuse.org/project/show/spins:invis:15:stable:samba:413)

We should do this for every as stable testet samba version in spins:invis:15:unstable:samba.

Actions #7

Updated by flacco almost 3 years ago

  • 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
Actions #8

Updated by flacco almost 3 years ago

Actions #9

Updated by flacco almost 3 years ago

  • Description updated (diff)
  • % Done changed from 20 to 0

Progress zurück auf 0% gesetzt.

Actions #10

Updated by flacco almost 3 years ago

  • Description updated (diff)
Actions #11

Updated by flacco 5 months ago

  • Due date changed from 2021-10-31 to 2024-04-30

14.3 noch nicht ganz fertig

Actions #12

Updated by flacco 5 months ago

  • 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.

Actions #13

Updated by flacco 3 months ago

  • 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.

Actions

Also available in: Atom PDF