APIM 4.3.0 locally DP runs K8s Rancher and mixing up subscription information

[dushansachinda]

Tharindu already aware of this issue. We worked on troubleshooting and creating this ticket per his request

Rancher 1.11.0

1. Run CP separately locally, update apk agent respectively to connect local CP
2. API publishing and subscription events seems update at DP layer successfully
3. However, the when execute try-out, API invocation failing
4. We had troubleshooting at APK level and following information has discovered

dushan:apk-agent dushan$ kubectl get applicationmappings -n apk -o yaml
apiVersion: v1
items:

• apiVersion: cp.wso2.com/v1alpha2
  kind: ApplicationMapping
  metadata:
  creationTimestamp: "2024-05-17T04:39:35Z"
  generation: 1
  name: cbdfe466-d970-4c4b-9392-da7296252d08
  namespace: apk
  resourceVersion: "13534"
  uid: e332ea0d-5304-4206-9998-2709db013f5c
  spec:
  applicationRef: PetStore
  subscriptionRef: 1.0.0

we did update application ref and subscription ref manually so it worked!! We think this is a bug

dushan:apk-agent dushan$ kubectl edit applicationmappings -n apk -o yaml
apiVersion: cp.wso2.com/v1alpha2
kind: ApplicationMapping
metadata:
creationTimestamp: "2024-05-17T04:39:35Z"
generation: 2
name: cbdfe466-d970-4c4b-9392-da7296252d08
namespace: apk
resourceVersion: "13791"
uid: e332ea0d-5304-4206-9998-2709db013f5c
spec:
applicationRef: aa915026-ea56-4c5d-b5de-4310a94061de
subscriptionRef: cbdfe466-d970-4c4b-9392-da7296252d08