Clone VM Fails with "OVMAPI_9037E Cannot clone VM" After Upgrade to PCA 2.3.1
Last updated on AUGUST 18, 2017
Applies to:Private Cloud Appliance - Version 2.3.1 and later
Oracle VM - Version 3.4.2 and later
After upgrading to PCA 2.3.1 (Oracle VM 3.4.2) :
Clone a VM fails as below:
- OVMAPI_9037E Cannot clone VM: test1, to server pool: POOL, when the destination repository: repo-for-POOL, is associated to a different clustered server pool: Rack1_ServerPool. [Mon Jul 31 12:09:06 AEST 2017]
But start, stop or migrate VM works on the same repository.
This repository repo-for-POOL is presented to a non-default Server pool, but it's still owned by the default PCA pool "Rack1-ServerPool".
Changing the ownership of this repository from the Rack1-ServerPool to the correct pool also fails.
Upgraded to PCA 2.3.1 (Oracle VM 3.4.2)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms