SCV errors when attaching a disk from a backup to a vm

• When using SCV to right click a VM, choose the attach disk among the SCV tasks, a policy with ExportPolicy* name is created by SCV but it is not associated with the clone volume.
• When a clone volume is created in Ontap, the cloned volume is automatically associated to the export policy that the parent destination volume is using: SCV is expected to  modify that but it doesn't.
• SCV gets an error when querying Ontap for the existence of the new clone:

[Request URL]: https://SVM1.my.domain.com/api/storage/volumes/?name=vol1_v070000000000001
[Response]: {
  "records": [
  ],
  "num_records": 0,
  "_links": {
    "self": {
      "href": "/api/storage/volumes/?name=vol1_v070000000000001"
    }
  }
}

• In the Ontap Mlog Auditlog the following error can be observed:

CLUSTER01: http :: 10.1.1.1:41000 :: SVM1:scadmin :: GET /api/private/cli/volume/clone/objects/SVM1/vol1_v070000000000001 :: Pending
CLUSTER01: http :: 10.1.1.1:41000 :: SVM1:scadmin :: GET /api/private/cli/volume/clone/objects/SVM1/vol1_v070000000000001 :: Error: entry doesn’t exist
0x8240dc200: 8503e80001fa89bb: ERR: zapis:ZapiServer: Failed to look up API registration for endpoint: /private/cli/volume/clone/objects/SVM1/vol1_v070000000000001