Join us for a virtual Nutanix User Group meeting with Jarian Gibson as he covers Nutanix Cloud Clusters (NC2) on Azure and AWS with Citrix. <\/span><\/p>

Jarian will take a deep dive into NC2 on Azure architecture and Citrix on NC2 on Azure\u00a0that helps you strengthen your business continuity and disaster recovery position. He\u2019ll also provide the latest updates for NC2 on AWS.<\/span><\/p>

Plus, we're\u00a0giving away a Nutanix suitcase to one lucky winner!\u00a0Opt-in when you register\u00a0to be entered to win.\u00a0<\/p>","author":{"id":113632,"url":"\/members\/karlie-beil-113632","name":"Karlie Beil","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/1581aab3-bcf6-49f4-b2fb-3d11e8c010dc.png","userTitle":"Community Manager","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Community Manager","color":"#0873ba"},"userLevel":4},"type":"Webinar","url":"https:\/\/next.nutanix.com\/events\/global-nug-nc2-on-azure-and-aws-with-citrix-151","image":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f9693b5b-436b-427a-9b98-531b4040ff24_thumb.png","location":"","startsAt":1678298400,"endsAt":1678302000,"contentType":"event","attendees":[],"attendeeCount":0,"isLoggedInUserAttendee":false,"createdAt":"1675974969"},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

解决了

通过Prismentral V3 API更新VM

e
徽章 +1

在尝试通过Prism Central API更新VM类别时，我们得到409回复说：

{
'api_version'：'3.1'，
“代码”：409，
'Message_list'：[{{
“消息”：'编辑冲突：请重试更改。实体CAS版本不匹配。'，
'原因'：'concurrent_requests_not_lowered'
}]，
'状态'：'错误'
}

它似乎仅在一个VM上发生，因为所有其他VM似乎都在正常更新。我可以通过通过GUI更新VM来清除它，但是，一旦尝试通过API进行操作，我会发现该错误。

关于此VM可能发生的事情有什么想法吗？

图标

最好的答案etr.Eric2020年1月15日，22:14

Found the solution. You have to make sure that the value is set:<\/p> 
\"use_catetories_mapping\": True<\/code><\/pre> 
Oddly enough, this value doesn\u2019t show up when you pull the config of a VM, so you don\u2019t know if it\u2019s ever set or not. It appears to be a hidden value but in order to utilize the categories mapping so that you can have multiple category:values set, you need to make sure that it is set to True.<\/p>","className":"post__content__best_answer"}">
查看原件
    While attempting to update a VM category via the prism central API, we are getting a 409 response saying:<\/p> 
    {
     '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'
    }<\/code><\/pre> 
    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.<\/p> 
    \u00a0<\/p> 
    Any thoughts on what could be going on with this VM?<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    7个答复

    s
    秩
    UserLevel 2
    徽章 +1

    @etr.eric感谢您发布问题。您能告诉我您的PE和PC版本是什么？如果PE和PC之间的版本不兼容，则会发生此问题。

    过去，我们有类似的问题。我们尝试升级PC。请让我知道各自的版本。

    @etr.eric<\/user-mention>\u00a0Thank you for posting the question. Could you please tell me what are your PE and PC versions? This issue occurs if there is version incompatibility between PE and PC.\u00a0<\/p>

    We have had similar issue in the past. We tried upgrading the PC. Please do let me know respective versions.<\/p>","quoteUsername":"Sneha Patekar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    e
    徽章 +1

    两者都在5.11上。由于这仅在我们的测试集群上，因此我正在考虑更新为5.11.2，但是如果您认为这可能会有所帮助，肯定会这样做。

    老实说，我有很多不一致之处，即使成功更新的机器，也可以将类别留在原地。它将通过，但是当我添加另一个类别时，它似乎会下降。您能告诉我哪个字典与VM元数据中的类别分配最相关？是“类别”字段或“ categories_mapping”字段？他们如何互动？

    “元数据”：{

    “ categories_mapping”：{
    “ category_1”：[
    “ category_value”
    ]，，
    “ category_2”：[
    “ cat_value_1”，
    “ cat_value_2”
    这是给予的
    }，，
    “类别”：{
    “ category_1”：“ category_value”，
    “ category_2”：“ cat_value_1”
    }
    }

    我们还注意到，似乎只有一个k，v对给定类别的v对可以列入类别字典，但是映射dict可以保留多个类别值。可以将多少值分配给VM有限制吗？

    Both are on 5.11. Since this is just on our test cluster, I was thinking about updating to 5.11.2 anyway but will definitely do it if you think that might help with this.<\/p>

    I\u2019ve honestly had a lot of inconsistency getting the category to stay in place even on the machines that update successfully. It will go through but then when I add another category, it seems like it will drop off. Can you tell me which dictionary is most relevant to the category assignment in the VM metadata? Is it the \u201ccategories\u201d field or the \u201ccategories_mapping\u201d field? How do they interact?<\/p> 

    \"metadata\":{

     \"categories_mapping\": {
     \"category_1\": [
     \"category_value\"
     ],
     \"category_2\": [
     \"cat_value_1\",
     \"cat_value_2\"
     ]
     },
     \"categories\": {
     \"category_1\": \"category_value\",
     \"category_2\": \"cat_value_1\"
     }
    }
    <\/code><\/pre> 
    We\u2019ve also noticed that seemingly only one k,v pair of a given category can live in the categories dictionary, however the mapping dict can hold multiple category values. Is there a limit to how many values can be assigned to a VM?<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    e
    徽章 +1

    我不知道这是否还在任何人的雷达上，但是我仍然在这些领域遇到麻烦。实际上，似乎通过PrismCentral API对VM类别的任何更新都无法正常工作。最初添加它时似乎有效，但是一旦我尝试添加一个其他类别：值，任务将进入待处理状态，然后尽管返回了成功的代码，但实际上还没有完成。我需要打开支持案例吗？

    是否有任何已知问题通过V3 Prism Central API更新VM的类别/项目字段？

    I don\u2019t know if this is on anyone\u2019s radar still, but I am still having trouble with these fields. In fact, it seems that any update to the categories of a VM\u00a0via the PrismCentral API isn\u2019t working correctly. It seems to work when adding it initially, however once I try to add an additional category:value, the task goes to a state of PENDING and then doesn\u2019t actually finish despite returning a successful code. Do I need to open a support case?\u00a0<\/p>

    Are there any known issues updating category\/project fields of a VM via the v3 prism central API?<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    e
    徽章 +1

    找到了解决方案。您必须确保设置该值：

    “ use_catetories_mapping”：true

    奇怪的是，当您拉出VM的配置时，该值不会显示出来，因此您不知道它是否设置为设置。它似乎是一个隐藏的值，但为了利用类别映射，以便您可以拥有多个类别：值集，您需要确保将其设置为true。

    Found the solution. You have to make sure that the value is set:<\/p> 
    \"use_catetories_mapping\": True<\/code><\/pre> 
    Oddly enough, this value doesn\u2019t show up when you pull the config of a VM, so you don\u2019t know if it\u2019s ever set or not. It appears to be a hidden value but in order to utilize the categories mapping so that you can have multiple category:values set, you need to make sure that it is set to True.<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    e
    徽章 +1

    @sneha patekar我错误地将其标记为已回答，事实并非如此。

    在启用“ use_category_mapping”标志的同时，VM是否使用了多个类别，在尝试更新VM时，我们仍在遇到409冲突响应。它似乎并非在所有VM上。似乎是在与Spec_version发生冲突或可能与Spec_hash发生冲突时。这仍然是一个空旷的问题。

    您可以将其重置为未解决的问题吗？

    @Sneha Patekar<\/user-mention>\u00a0I mistakenly marked this as answered and it is not.<\/p>

    While enabling the \u201cuse_category_mapping\u201d flag did fix whether the VM used multiple categories, we are still running into the 409 CONFLICT response when trying to update VMs. It doesn\u2019t appear to be on all VMs. Seems to be when there is a conflict with the spec_version or possibly something with spec_hash. This is still an open issue.<\/p>

    Can you reset this as unanswered?<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    e
    徽章 +1

    我相信这一点的关键点是，您必须意识到Spec_version，如果您尝试将更新推向VM，则会出于同步而将其推出，您将获得409冲突。如果您完全将Spec_version删除，则将获得422个无效。因此，不仅需要Spec_version，而且必须在更新VM API请求进行之前必须匹配。

    I believe that the critical point to this is that you have to be aware of the spec_version and if you try and push an update to a VM with it\u00a0out of sync, you will get a 409 CONFLICT. If you pull the spec_version out entirely, you will get a 422 INVALID. So not only is spec_version required, but it has to match before an update VM API request will go through.<\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    e
    徽章 +1

    这被错误地被标记了。虽然一部分被理解，但对于为什么VM会陷入“错误”状态，仍然尚不清楚。

    在这里打开一个新主题：https://next.nutanix.com/api-31/updating-vm-via-prismcentral-v3-api-37435

    This was marked as answered by mistake. While part of it is understood, there still isn\u2019t any clarity on why a VM will get stuck in the \u201cERROR\u201d state.<\/p>

    Opened a new topic here:\u00a0https:\/\/next.nutanix.com\/api-31\/updating-vm-via-prismcentral-v3-api-37435<\/a><\/p>","quoteUsername":"etr.eric","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu