Bug 48158 – Allow having master a lower version than backup/ slave

Bug 48158 - Allow having master a lower version than backup/ slave


Summary:	Allow having master a lower version than backup/ slave

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Update - Release updates
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-11-16 10:21 CET by Christian Völker
Modified:	2021-05-14 16:34 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018111521000763
Bug group (optional):	API change
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christian Völker

2018-11-16 10:21:40 CET

customer requests to allow having the master server a lower version than backup/ slave servers.

As the master server is very important the updates here will be performed some time after a new release to make sure any possible issues have been fixed when upgrading.

But it blocks the upgrade of the other servers as they can not be upgrades as long as the master is not. 

Once the master is upgraded the other servers have to be updated very quickly as they might run out of maintenance...

Comment 1 Philipp Hahn

2018-11-16 10:31:31 CET

You can already do that:
 ucr set update43/ignore_version=true

It is not recommended as it might break in unexpected situations: We just had the situation, where an new LDAP attribute was added and it was added the the attributes to be index by the LDAP server. It was added on the backup, but the schema update was not yet installed on the master. This broke slapd.
So again: it is not recommended as we do not test this scenario!

Comment 2 Arvid Requate

2018-11-19 20:02:40 CET

Ok, worksforme then?

Comment 3 Christian Völker

2018-11-20 08:39:46 CET

Well, I was aware of such a switch.

But the request is not to overwrite recommended settings and increase the chance to break your system.

The request is to have this possibility as part of the product and allow (and test and support and so on) to have mixed environments.

Without the risk of loosing data. I thought the term "master server is very important" is clear for this scenario...

Comment 4 Ingo Steuwer

2021-05-14 15:41:14 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.