I am attempting to create a flexclone that resides in a different vserver from the parent volume. These attempts are using Python SDK with ONTAP 9.2. The CLI equivalant of the API commands works just fine.
The XML of my request is below  used by doing toEncodedString() on the API request. Message I get is "Extra input: junction-path". If I run the same command via CLI , I am successful:
netapp-home::> volume clone create -parent-vserver systems -parent-volume owens_root_rhel73_3 -parent-snapshot clone.owens_root_rhel73_test -vserver test -flexclone owens_root_rhel73_test -type rw -space-guarantee volume -junction-path /owens_root_rhel73_test
[Job 19548] Job is queued: Create owens_root_rhel73_test.
The code I'm using is below. My parameters are logged below too:
Does it work without providing the junction path? If so, what is the state after creating the clone (e.g. is it junctioned or not)? If it's not junctioned, would it be an acceptable solution to make a separate API call to "volume-mount" to junction the clone?
Hope that helps.
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
If I leave off the junction-path in API call then one is not setup and the volume is not mounted. I could issue a volume-mount API call but it seems like that should be unnecessary when the same operation is successful in the CLI. This seems like a potential bug in the API unless the "volume clone" CLI does a separate mount that is not then exposed in the same way via the API.
Experienced the same error in a wfa workflow with the Create Clone command. With junciton path specified the command gets the error "coud not create clone with extra input junction path (13125). Workaround is to omit junciton path in the create clone command and to add an extra command to mount the volume clone. Is there any information if this will get fixed or has already been fixed in the newest SDK?