Bug 46298 – Test UCS 4.2 DC with S4-Connector joined into a UCS 4.3 Master

Bug 46298 - Test UCS 4.2 DC with S4-Connector joined into a UCS 4.3 Master


Summary:	Test UCS 4.2 DC with S4-Connector joined into a UCS 4.3 Master

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	Jenkins - Test setups
Version:	unspecified
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	46292 46301
Blocks:
	Show dependency tree / graph

Reported:	2018-02-15 21:33 CET by Arvid Requate
Modified:	2018-04-14 13:47 CEST (History)
CC List:	3 users (show)

See Also:
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:

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