Description of problem: I got "incorrect path" server error while trying to update existing subnet properties using the PUT server method on <server>/v2.0/api/subnets/<subnet_id> Version-Release number of selected component (if applicable): oVirt Engine Version: 4.1.0-0.0.master.20161127231313.git9bb30a5.el7.centos oVirt Provider OVN: ovirt-provider-ovn-0.1-1 How reproducible: 100% Steps to Reproduce: 1. Create two OVN networks, where one network attached to subnet. 2. Try to use PUT to update the network_id key of the subnet to the network_id of the other network (without subnet attached). Actual results: Incorrect path error is displayed. Expected results: network_id value should be modified. Additional info: https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Update_Subnet
We currently only support the part of Neutron API which is used by the engine (external networks). Since you can not modify subnets from the engine, this is not supported at this moment.
our provider must be a very shallow integration layer above OVN. we should not create and manage entities that do not exist in OVN. do we currently have any other means to modify network's subnet via our API?
We only implement a subset of the neutron REST API, only the items which are needed by the external network providers feature in ovirt-engine. PUT is not supported for subnets and networks, as it is not needed by the exernal network providers feature.
Let's wait with this until we reimplement ovirt-provider-ovn using ovsdbapp.
Patch is not merged yet.
It is possible to associate a subnet using the PUT method with non-existent network ID, do we consider this a bug?
it smells like a bug, but I am not sure I understand what you are doing. Please state here which action you do, what do you receive instead of the expected error. Also, please direct this type of questions to Marcin.
(In reply to Dan Kenigsberg from comment #7) > it smells like a bug, but I am not sure I understand what you are doing. > Please state here which action you do, what do you receive instead of the > expected error. Also, please direct this type of questions to Marcin. I will try to elaborate: I am able to change the 'network_id' value of existing subnet to non-existent network id. The provider doesn't check if the ID exist or not.
This should not be possible, needs to be fixed.
Verified on: ovirt-provider-ovn-1.2-0.20171020111522.git3dd43cf.el7.centos.noarch { "error": { "message": "Unable to move subnet to network `<id_of_network>`. The network does not exit.", "code": 400, "title": "Bad Request" } }
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.