Created attachment 1151804 [details] host logs Description of problem: Ovirt fail save network configuration. Task hangs forever. Version-Release number of selected component (if applicable): [root@hp1 ~]# rpm -qa | grep vdsm vdsm-xmlrpc-4.17.26-1.el7.noarch vdsm-jsonrpc-4.17.26-1.el7.noarch vdsm-infra-4.17.26-1.el7.noarch vdsm-yajsonrpc-4.17.26-1.el7.noarch vdsm-4.17.26-1.el7.noarch vdsm-cli-4.17.26-1.el7.noarch vdsm-hook-vmfex-dev-4.17.26-1.el7.noarch vdsm-python-4.17.26-1.el7.noarch How reproducible: Have 2 network. ovirtmgmt and OldLan. Both have default GW. But after change network structure need delete gw in ovirtmgmt. Steps to Reproduce: 1. Go to network in host manage UI 2. Network ovirtmgmt not synced 3. Go to edit ovirtmgmt 4. Sync 5. UI was add default gw in ovirtmgmt 6. Delete default gw becouse OldLan have privary gw. 7. Save 8. Result - forever task
Created attachment 1151805 [details] engine log 2
can you add vdsm.log and supervdsm.log?
"Engine log" - it all log from HOST... wrong description
I see bug 1320606. Would you please upgrade to ovirt-3.6.6 (beta), make sure that you have vdsm-jsonrpc-java-1.1.10 (or later), and try again. We have solved similar issues, but it is likely that we more work to be done, so please report your findings here. jsonrpc.Executor/2::DEBUG::2016-04-28 13:31:15,211::__init__::533::jsonrpc.JsonRpcServer::(_serveRequest) Return 'Host.ping' in bridge with True jsonrpc.Executor/7::DEBUG::2016-04-28 13:31:15,213::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.ping' in bridge with {} jsonrpc.Executor/7::DEBUG::2016-04-28 13:31:15,214::__init__::533::jsonrpc.JsonRpcServer::(_serveRequest) Return 'Host.ping' in bridge with True jsonrpc.Executor/0::DEBUG::2016-04-28 13:31:15,216::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'Host.ping' in bridge with {}
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
*** This bug has been marked as a duplicate of bug 1320128 ***