Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.12
Component/s: Management Console
Labels:
None

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

Hide

None

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

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

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

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:

Cluster console

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

4.12.8 (also checked in 4.12.0 and probably in previous versions.

How reproducible:

Always

Steps to Reproduce:

1. Create two deployments with the same selector in spec.template.spec and one replica in each.
2. Go to console to one of the deployments. One pod is shown in the circle.
3. however, clicking on the replicaset tab, we can see two different ones. Same in pods tab.

Actual results:

Both replicaset and set of pods.

Expected results:

Just one replicaset and its pods.

Additional info:

ownerReferences should also be used to identify the object hierarchy

Assignee:: Steve goodwin

Reporter:: Ramon Gordillo Gutierrez

Need Info From:: None

Contributors:: None

QA Contact:: YaDan Pei

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2023/03/28 9:24 PM

Updated:: 2025/07/27 11:36 AM

Resolved:: 2023/05/18 5:45 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates