-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
Not sure how reproducible this is, and haven't come across it more than once while
browsing CSIT results. But, maybe it's more common than we know, and maybe it's
something obvious we can figure out in the logs
the problem request and response looks like this:
GET /restconf/config/neutron:neutron/networks/network/9336700e-077a-4209-b88d-8a94ad1ab441/
resp:
{"network":[{"uuid":"9336700e-077a-4209-b88d-8a94ad1ab441","admin-state-up":true,"neutron-provider-ext:segmentation-id":"1076","neutron-provider-ext:network-type":"neutron-networks:network-type-vxlan","neutron-L3-ext:external":false,"shared":false,"revision-number":2,"name":"vpn_net_1"}]}
as an example of output our CSIT is expecting:
{"network":[{"uuid":"1b1172d0-8fd4-4b71-a7d7-5d81fd81b322","admin-state-up":true,"neutron-provider-ext:segmentation-id":"1001","neutron-provider-ext:network-type":"neutron-networks:network-type-vxlan","tenant-id":"b9f05034-9221-4e03-9e97-2467d7ffa9dd","neutron-L3-ext:external":false,"shared":false,"revision-number":2,"name":"vpn_net_1"}]}
