-
Notifications
You must be signed in to change notification settings - Fork 322
UI shows incorrect cached elements for Pods list in Service details view #15529
Copy link
Copy link
Closed
Labels
JIRAQA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/dashboardkind/bugpriority/2status/backport-candidate
Milestone
Description
SURE-10760
Setup
- Rancher version:
2.12.1 - Rancher UI Extensions: n/a
- Browser type & version: any
Describe the bug
With ui-sql-cache off, the list of pods is cached (at least when viewing a Service details view) incorrectly. Check repro steps for more information
To Reproduce
- Provision a Rancher v2.12.1 cluster.
- Disable the
ui-sql-cacheFeature Flag. - Create a
Servicewithout any matching selector like the following (import YAML):
apiVersion: v1
kind: Service
metadata:
name: emptyservice
spec:
selector:
bla: irrelevant
type: ClusterIP
ports:
- name: http
port: 80
protocol: TCP
targetPort: http
- Click on the
emptyservice(details view for Service). The list under the pods tab should be empty. - Click on
Workloads->Pods: - Click again on
Service Discovery->Services->emptyservice(details view for Service). - See the list of all pods (which shouldn't be related to this Service)
Result
emptyservice shows incorrectly the list of all Pods
Expected Result
emptyservice should not show any Pod associated
Screenshots
Screen.Recording.2025-09-26.at.10.13.34.mov
Additional context
-
With
ui-sql-cacheon the Service details view Pod's list briefly shows the incorrectly the list of all Pods, but right after updates to the correct value (this was validated in the scenario where we've disabledui-sql-cachefirst, then re-enabled it) -
Pertinent question is if
findLabelSelectoraction andmatchingLabelSelectorgetter are ready to work withui-sql-cacheoff
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
JIRAQA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/dashboardkind/bugpriority/2status/backport-candidate