Bug 46298

Summary:	Test UCS 4.2 DC with S4-Connector joined into a UCS 4.3 Master
Product:	UCS Test	Reporter:	Arvid Requate <requate>
Component:	Jenkins - Test setups	Assignee:	UCS maintainers <ucs-maintainers>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P5	CC:	botner, requate, scheinig
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Linux
What kind of report is it?:	---	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?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:
Bug Depends on:	46292, 46301
Bug Blocks:

Description Arvid Requate

2018-02-15 21:33:06 CET

As seen in Bug #46292 it would be important to have a Jenkins setup to test a UCS 4.2 server joined into a UCS 4.3 Master.

The Bug #46292 would also not have been detected if the S4-Connector would not have been on the UCS 4.2 system. Instead of UCS 4.3 Master and UCS 4.2 Backup we could also setup an UCS@school 4.2 Slave joined into a UCS@school 4.3 Master.

That's a generic situation: UCS X.(N-1) DC joined into a Master with UCS X.N.

A re-join should be tested as well in that setup.