Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: 4.18.0
Affects Version/s: 4.16, 4.17
Component/s: TALM Operator
Labels:
- ert:pending-onqa-over-96hrs

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:

4.17.z, 4.16.z
Target Version:

4.18.z
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    IBGU will not include some cluster for the next upgrade, if the cluster labeling fails for a previous step.

Version-Release number of selected component (if applicable):

How reproducible:

    When network failure happens during cluster labeling updates

Steps to Reproduce:

    Start an IBGU for multiple clusters. introduce intermittent network failure. Managed clusters that are not labeled correctly won't be include for the next stage of the upgrade.

Actual results:

    ManagedClusters that are not labeled, are not included in the next stage

Expected results:

    Next stage should not start until all managed clusters are successfully labeled.

Additional info:

Assignee:: Saeid Askari

Reporter:: Saeid Askari

Need Info From:: None

Contributors:: None

QA Contact:: Joshua Clark

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2024/12/16 4:24 PM

Updated:: 2025/10/01 3:29 PM