Created attachment 1423404 [details] evm.log Description of problem: When trying to add an interface to a router, it fails with: Unable to add Subnet "ovn_router": undefined method `response' for #<Fog::Network::OpenStack::NotFound:0x000000000f54cc70> Did you mean? respond_to? Using OVN provider for all entitties. Version-Release number of selected component (if applicable): cfme - 5.9.2.2.20180410215257_6961422 ovirt-engine-4.2.2.5-0.1.el7.noarch ovirt-provider-ovn-1.2.9-1.el7ev.noarch openvswitch-ovn-common-2.9.0-1.el7fdp.x86_64 openvswitch-ovn-central-2.9.0-1.el7fdp.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create network, subnet and router in ovirt OVN provider 2. Go to add interface to the router, select the created subnet 3. Actual results: Unable to add Subnet "ovn_router": undefined method `response' for #<Fog::Network::OpenStack::NotFound:0x000000000f54cc70> Did you mean? respond_to? Expected results: interface added Additional info: It may be somehow related issue to BZ 1561962
I tried to reproduce the bug and it worked for me. Can you please add the ovirt-provider-ovn.log?
Created attachment 1425560 [details] ovirt-provider-ovn.log
Marcin, please take a look at the ovn-provider log.
The subnet given as a parameter for the router interface seems to be incorrect. The rest request to add a router interface looks like: /v2.0/routers/{router_id}/add_router_interface { "subnet_id": "{subnet_id}" } and a record for {subnet_id} seems not to exist. Is it possible to send a rest query to list all the subnets? If so, please do: curl --insecure https://{host where provider is installed}:9696/v2.0/subnets/ in case you have authentication enabled do: curl --insecure --data '{"auth":{"tenantName": "customer-x","passwordCredentials": {"username": "admin@internal","password": "{admin pasword}"}}}' https://{host where provider is installed}:35357/v2.0/tokens and use the received token: curl --insecure --header 'X-Auth-Token: {token}' https://{host where provider is installed}:9696/v2.0/networks
output of: curl --insecure --header 'X-Auth-Token: {token}' https://{host where provider is installed}:9696/v2.0/subnets {"subnets": [{"ip_version": 4, "allocation_pools": [{"start": "10.0.0.2", "stop": "10.0.0.255"}], "name": "my_subnet", "enable_dhcp": true, "network_id": "db1170be-3343-415b-851f-37808aabc908", "tenant_id": "00000000000000000000000000000001", "cidr": "10.0.0.1/24", "dns_nameservers": [], "id": "d1e937c6-2b72-4c41-a7af-9259aa442339"}]} However, with the recent change to parsing errors [1], I found out that the problem was that the subnet I tried to attach to a router interface didn't have specified default gateway. With default gateway specified, the subnet is successfully attached to router interface. Therefore closing as not a bug. [1] https://github.com/ManageIQ/manageiq-providers-openstack/pull/263