You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When using cisco.mso.mso_rest to patch NDO schema I ran into some issues. The code was previously working on earlier NDO (3.7.(1j)) and collection version (2.2.1), but after upgrade to 4.2.3e, along with update of the collection from 2.2.1 to 2.6.0 the code no longer worked. This problem is now resolved, but to find the cause I needed to use Postman as the output returned by mso-rest was quite unhelpful for some reason. The raw output returned from Postman, for the exact same request, provided a clear insight into what was going wrong in the API call
Affected Module Name(s):
mso_rest
MSO version and MSO Platform
V 4.2.3e and ND-based.
APIC version and APIC Platform for Site Level Resources
{
"code": 400,
"message": "site-local Contract CI9380650 in site e-us-site1 in template CommonTemplate_001: missing Service Graph configuration",
"info": null
}
Actual Behavior
The output from the mso_rest module in Ansible seems to have lost/dropped the useful info returned by the API endpoint, so the helpful text explaining why the API call failed is missing. I would expect the module to give me the useful info so I could correct the code and not have to resort to constructing the faulty call in Postman in order to understand what is going wrong
The reason for the failure is that NDO now requires the template and site level contract service graph structures to be provided at the same time, in the same API call, whereas in previous versions this could be delivered as two separate calls.
References
#0000
The text was updated successfully, but these errors were encountered:
Hi @phil-dotchon, I am unable to reproduce this error (tested on MSO collection v2.6 and v2.9), does this error occor on v2.9 as well?
Will it be possible to attach the complete playbook that generated this error?
I wanted to bring to your attention that modules are available for template and site-level Service graphs (mso_schema_template_service_graph, mso_schema_site_service_graph).
Hi Anvitha, sorry for being slow. I can't really attach the whole playbook because it is very large and would have all kinds of dependencies, but I'll try to recreate a scenario using an empty schema when I can find some time.
I did look at the service graph modules some time ago, but there were still some parts missing then. In the meantime I have written a custom module that generates schema patches for multiple contracts in one pass; speed/performance has increasing become an issue for us, as some of our plays can take 40/50 minutes+ where we are deploying app environments with a lot of contracts, so removing Ansible loops where possible has helped speed things up
Community Note
Description
cisco.mso.mso_rest
to patch NDO schema I ran into some issues. The code was previously working on earlier NDO (3.7.(1j)
) and collection version (2.2.1
), but after upgrade to4.2.3e
, along with update of the collection from2.2.1
to2.6.0
the code no longer worked. This problem is now resolved, but to find the cause I needed to use Postman as the output returned bymso-rest
was quite unhelpful for some reason. The raw output returned from Postman, for the exact same request, provided a clear insight into what was going wrong in the API callAffected Module Name(s):
MSO version and MSO Platform
4.2.3e
and ND-based.APIC version and APIC Platform for Site Level Resources
5.3(2b)
and on-premCollection versions
2.6.0
Output/ Error message
mso_rest
Expected Behavior
Actual Behavior
mso_rest
module in Ansible seems to have lost/dropped the useful info returned by the API endpoint, so the helpful text explaining why the API call failed is missing. I would expect the module to give me the useful info so I could correct the code and not have to resort to constructing the faulty call in Postman in order to understand what is going wrongPlaybook tasks to Reproduce
Postman call:
Important Factoids
The reason for the failure is that NDO now requires the template and site level contract service graph structures to be provided at the same time, in the same API call, whereas in previous versions this could be delivered as two separate calls.
References
The text was updated successfully, but these errors were encountered: