CONTAP-589571: Source cluster shows relationship details couldn't be retrieved error in local source TAB

Issue

• Source cluster shows relationship details couldn't be retrieved error in local source TAB
• Since relationship was created, relationship details are seen healthy on destination cluster but on source cluster GUI shows an error as:

• sysmgr.log from the source:
  {}No relationship details returned, exception in fetching peek view details{}{}...{}{}...{}{}Http failure response for https://<Cluster_IP>/api/snapmirror/relationships/<Cluster_UUID>?fields=source.path%2Csource.svm%2Csource.cluster.name%2Csource.cluster.uuid%2Cdestination.path%2Cdestination.svm%2Cdestination.uuid%2Cdestination.cluster.uuid%2Cpolicy.name%2Cpolicy.type%2Cpolicy.uuid%2Cstate%2Clag_time%2Cuuid%2Ctransfer.state%2Ctransfer.bytes_transferred%2Ctransfer.uuid%2Cexported_snapshot%2Crestore%2Chealthy%2Cunhealthy_reason%2Cdestination.cluster.name%2Cthrottle%2Ctransfer_schedule&return_timeout=120: 404 Not Found","error":{"error":{}{}{"message":"entry doesn't exist","code":"4","target":"uuid"}{}}}
  

• Manual trigger of the API:
  {}https://<cluster_IP>/api/snapmirror/relationships/<Cluster_UUID>?fields=source.path%2Csource.svm%2Csource.cluster%2Cdestination.path%2Cdestination.svm%2Cdestination.cluster%2Cpolicy.name%2Cpolicy.type%2Cpolicy.uuid%2Chealthy%2Cstate%2Clag_time%2Cuuid%2Cunhealthy_reason&source.path=ODKSVMFYSFC%3AODKSVMFYSFC_adm_ai_03_system_vol&return_timeout=120{}{}{{}{}"error":{}{}{ "message": "entry doesn't exist", "code": "4", "target": "uuid" {}}}
  

• The error message/scenario matches exactly with *CONTAP-262358* but unlike the root cause identified on *CONTAP-262358* ,  there is no name change on destination cluster. So that is not applicable here.

• Same error is also present on the snapmirror section of the volume page of the source cluster where Target volumes show no protection policy, schedule, status and lag by default
• However, it shows them all as soon as the the bar for "Show Uninitialized" is toggled
• This means, System Manager somehow thinks those relations as not initialized.

• After the bar for "Show Uninitialized" is toggled, the API call changes from
  https://<cluster_IP>/api/snapmirror/relationships/<Cluster_UUID>?fields=source.path%2Csource.svm%2Csource.cluster%2Cdestination.path%2Cdestination.svm%2Cdestination.cluster%2Cpolicy.name%2Cpolicy.type%2Cpolicy.uuid%2Chealthy%2Cstate%2Clag_time%2Cuuid%2Cunhealthy_reason&source.path=<Source SVM:Source Vol>&return_timeout=120
  to
  https://<cluster_IP>/api/snapmirror/relationships/<Cluster_UUID>?fields=source.path%2Csource.svm%2Csource.cluster%2Cdestination.path%2Cdestination.svm%2Cdestination.cluster%2Cuuid%2Cstate&source.path=<Source SVM:Source Vol>&list_destinations_only=true&return_timeout=120
  

• As we can see there are fields like Cpolicy.name, Cpolicy.type, Cpolicy.uuid, Chealthy, Clag_time and Cunhealthy_reason without any list_destinations_only=true which are asked when having a 404-Not Found error and where having a successful result, those parameters are not asked and list_destinations_only=true is added in the API call for getting snapmirror relationships