Topics started by etr.eric

4 Topics

E
etr.ericAdventurer
asked in How It works

Updating VM via PrismCentral v3 API

This is a continuation of the post that I wrote here: https://next.nutanix.com/topic/show?tid=33950&fid=31 Part of this was resolved however we are still running into an issue with some of our VMs in which they get stuck in this state: { "status": { "description": "2016 Template-4/17/19", "state": "ERROR", "execution_context": { "task_uuids": [ "8d0c2110-461b-4252-a223-11016ff8714b" ] }, "message_list": [ { "message": "Edit conflict: please retry change. Entity CAS version mismatch.", "reason": "CONCURRENT_REQUESTS_NOT_ALLOWED" } ]} The only way to clear it is to power the VM down and update the VM within the GUI.  However, upon trying to subsequently update the VM by API it results int the same error. Please advise.

3
P
2 years ago
E
etr.ericAdventurer
asked in How It works

FIQL Filtering - Not Equal

We make use of a lot of the FIQL filtering in our automation to pare down results from various REST calls. However, it seems that while filtering on things like category_name or category_value work just fine with an ==, they don’t seem to work with an !=. Is there a way to do an inequality filter, specifically with v3 of the Prism Central API?

1
AntonioG
Nutanix Employee
3 years ago
E
etr.ericAdventurer
asked in How It works

Updating a VM via PrismCentral v3 API

While attempting to update a VM category via the prism central API, we are getting a 409 response saying: { 'api_version': '3.1', 'code': 409, 'message_list': [{ 'message': 'Edit conflict: please retry change. Entity CAS version mismatch.', 'reason': 'CONCURRENT_REQUESTS_NOT_ALLOWED' }], 'state': 'ERROR'} It seems to be occurring on only one VM as all others seem to update normally. I can clear it by updating the VM through the gui, however once I try and do it via API I get that error.   Any thoughts on what could be going on with this VM?

7
E
4 years ago
E
etr.ericAdventurer
asked in How It works

Move API 3.3 - Create migration plan from ESX to AHV

Just curious if there is going to be an update to the Move API documentation to explain how we can create a migration plan from ESX to AHV. Currently the only example shown is for AWS to AHV and when we try to substitute that payload with values from ESX it fails. Create plan example is here:http://{{ move-ip-address }}:8082/#/v2api/plans/createplan We’ve tried using this same template to create a plan for ESX, but it seems to choke on the network identification section with a return code of {'ApiVersion': '2.0.0', 'Code': 20512, 'Message': "Invalid Network Mapping for VM 'NX-TEST'. Ensure sufficient user permissions on source environment to fetch network information.", 'State': 'Error'}(we have validate permissions) This appears to be the part of the payload that it doesn’t like:From the AWS example: "Networks": [            {                "SourceID": "vpc-8e1c3de7",                "TargetUUID": "343eaa8f-a251-4ec0-8ede-729c97f7cddc"            } We’ve substituted these AWS specific

4
M
Nutanix Employee
4 years ago

Badges

Show all badges
Terms & Conditions