assign a category and value to an existing vm

[dleanes]

Describe the bug
A playbook was created that assigns a category and value to an already existing vm but it gives message 422 due to how the category entity is being added, I have checked and how I am doing it is how it should be added, but it continues with message 422 I created a case to nutanix support and they asked me to open a case here

To Reproduce
Steps to reproduce the behavior:
2. attached file asigncategtovm.txt
asigncategtovm.txt

error message

msg": "Failed fetching URL: https://iaxxxxxxxx.es.mgmt.xxxxxxx.com:9440/api/nutanix/v3/vms/3efec4d5-9111-42c5-b12b-1f9148485d36",
"response": null,
"status_code": 422

log cvm nutanix
024-07-24T12:42:06.530Z] "PUT /api/nutanix/v3/vms/3efec4d5-9111-42c5-b12b-1f9148485d36 HTTP/1.1" 422 - 4483 349 208 208 "172.30.178.19" "ansible-httpget" "xxxxxxx-xxx-xxx-xxxx" "172.xx.xxxx.xx" "172.xx.xxxx.xx:9444"
Expected behavior
I need to add the categories to the vm and it can be seen in the prism central
asigncategtovm.txt

[stahnjones]

did you try the new_categories as a list instead of a string?

vars:
new_categories:
"Disaster_Recovery":
- value_L1_DR

[dleanes]

Hi, yes I probé and messages is: HTTP: Error BAD REQUEST El jue, 25 jul 2024, 3:01, stahnjones ***@***.***> escribió:

…

did you try the new_categories as a list instead of a string? vars: new_categories: "Disaster_Recovery": - value_L1_DR — Reply to this email directly, view it on GitHub <#487 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGT44JR3WXACRCRS34EWSM3ZOBE7PAVCNFSM6AAAAABLMPXPDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZGE2DKOJTGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dleanes]

Hi sorry, test again because iI put name of the vm wrong, I test name correct y restult is succesfull . Leave as stay with bar Vars Category_key: "{{ category_key }}" Category_value: "{{ category_value}}" Categories: "{{ { (category_key): [category_value] } }}" Thank you for you help El jue, 25 jul 2024, 7:03, Daniel Leanes ***@***.***> escribió:

…

Hi, yes I probé and messages is: HTTP: Error BAD REQUEST El jue, 25 jul 2024, 3:01, stahnjones ***@***.***> escribió: > did you try the new_categories as a list instead of a string? > > vars: > new_categories: > "Disaster_Recovery": > - value_L1_DR > > — > Reply to this email directly, view it on GitHub > <#487 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGT44JR3WXACRCRS34EWSM3ZOBE7PAVCNFSM6AAAAABLMPXPDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZGE2DKOJTGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[george-ghawali]

Since it is working fine for the reporter, as well as I also checked. Hence, closing this ticket.