Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 4.13, 4.12, 4.11
Component/s: TALM Operator
Labels:
- talm
- telco-priority-2

Severity:
Important
Regression:
No
Sprint:
CNF RAN Sprint 239, CNF RAN Sprint 240, CNF RAN Sprint 241
sprint_count:
3
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Internal Whiteboard:
Target Version:

4.14.0

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

Description of problem:
The TALM Operator deployment created by the CSV includes the following selector. This matches what is also used OpenShift GitOps.

  selector:
    matchLabels:
      control-plane: controller-manager
  strategy: {}
  template:
    metadata:
      labels:
        control-plane: controller-manager

https://github.com/openshift-kni/cluster-group-upgrades-operator/blob/release-4.12/bundle/manifests/cluster-group-upgrades-operator.clusterserviceversion.yaml#L332C1-L339C50

When looking at the Console UI the Deployment for TALM shows both TALM and OpenShift GitOps on the ReplicaSet and Pods tab.

How reproducible:
Every time.

Steps to Reproduce:

1. Install both TALM and OpenShift GitOps operators.
2. Navigate to the TALM or OpenShift GitOps Deployments in openshift-operators namespace
3. Select the ReplicatSet or Pods tab.

blocks

OCPBUGS-17726 TALM Operator pod selector also selects OpenShift GitOps