Uninstall Open Liberty operator 1.3.0 panel shows double deployed OpenLibertyApplication (Operand instances)

[tam512]

Bug Report

In OCP 4.14, I have 3 OpenLibertyApplication installed using Open Liberty operator (OLO) 1.3.0 . The olapps were deployed with v1

apiVersion: apps.openliberty.io/v1
kind: OpenLibertyApplication

Below are 3 installed olapps:

% oc get olapps -A
NAMESPACE   NAME                   IMAGE                                                                                                                                         EXPOSED   RECONCILED   RESOURCESREADY   READY   AGE
ebuy-wlo    ebuy-olf-j11-intub22   docker-na-public.artifactory.swg-devops.com/hyc-wassvt-team-image-registry-docker-local/instanton/24.0.0.1/ebuy:ol-full-java11-intel-ub22     true      True         True             True    27h
ebuy-wlo    ebuy-olf-j17-amdub22   docker-na-public.artifactory.swg-devops.com/hyc-wassvt-team-image-registry-docker-local/instanton/24.0.0.1/ebuy:ol-full-java17-amd-ub22       true      True         True             True    27h
ebuy-wlo    ebuy-olk-j11-rh90      docker-na-public.artifactory.swg-devops.com/hyc-wassvt-team-image-registry-docker-local/instanton/24.0.0.1/ebuy:ol-kernel-java11-amd-rhel90   true      True         True             True    27h

But when I uninstall the OLO 1.3.0 in OpenShift console, the "Uninstall Operator" pop up shows with 6 operand instances as following screen capture:

What did you do?

A clear and concise description of the steps you took (or insert a code snippet).

What did you expect to see?

Expect to see 3 operand instances in the Uninstall Operator panel

What did you see instead?

See 6 operand instances in the Uninstall Operator panel

Environment

• Kubernetes version information: v1.27.6+f67aeb3

% oc version
Client Version: 4.14.0-202310201027.p0.g0c63f9d.assembly.stream-0c63f9d
Kustomize Version: v5.0.1
Server Version: 4.14.1
Kubernetes Version: v1.27.6+f67aeb3

• OpenShift version information (if applicable):

4.14.1

Possible solution

Additional context

I did not see this behavior when installing WebSphere Liberty operator 1.3.0.
I see this problem on both Firefox and Chrome browsers