Loading...

XML

Word

Printable

Type: Epic
Resolution: Obsolete
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: Two Node Fencing
Labels:
None

Epic Name:
TNF Lifecycle
Activity Type:
Product / Portfolio Work
Parent Link:
OCPSTRAT-1551Two Node OpenShift with Fencing (TNF) - GA
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Size:
S

Target Version:
None
Release Blocker:
None

Story Points:
14

As a developer of TNF, I need:

To ensure that upgrades between z-streams and y-streams work as expected in TNF
To ensure that MCO upgrade events behave correctly in TNF
To be able to replace a control-plane node in TNF

Acceptance Criteria

Node restart scenarios have been tested by development
Instructions and automation for replacing a control plane node in TNF exists

TNF Enhancement Proposal

split to

OCPEDGE-1793 Ensure upgrades work in TNF clusters

New

OCPEDGE-1796 TNF clusters should offer validation for fencing setup

In Progress

OCPEDGE-1792 Ensure MCO reboots work and pod-disruption budgets make sense in TNF clusters

Release Pending

Assignee:: Unassigned

Reporter:: Jeremy Poulin

Contributors:: None

QA Contact:: None

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2024/12/20 3:22 PM

Updated:: 2025/09/16 11:27 AM

Resolved:: 2025/04/22 3:12 PM