Adding TesBlocker because it actually blocked us from testing SetupNetworks in automation framework.
Automation framework automatically generated data structures from XSD.
Missing actions for nics collection leads for missing SetupNEtworks action for nics data structure object.
BTW, the common use cases in automation is to automatically generate objects from XSD so i suspect many API users will scream this issue.
Comment 7Michael Pasternak
2012-08-23 09:40:27 UTC
lowering priority as action code exist - QE can assume the url [1], and sdk has setupnetworks() method, so no blocker for testing.
(this is complex infrastructure change that may take time)
[1] /api/hosts/xxx/nics/setupnetwork
Comment 8Michael Pasternak
2012-08-23 15:40:44 UTC
patch is NACK'ED at upstream.
Comment 9Michael Pasternak
2012-08-25 14:31:57 UTC
Description of problem: htttp://engine:port/hosts/{host id}/nics/setupnetworks This action link is missing under /nics Exists: <host_nics> <host_nic> ... </host_nic> <host_nic> ... </host_nic> </host_nics> -- should look like: <host_nics> <actions> <link href='.../nics/setupnetworks' rel='setupnetworks' /> </actions> <host_nic> ... </host_nic> <host_nic> ... </host_nic> </host_nics>