Bug 1723804 - Operation Failed: [Resource unavailable] - failed to sync networks on host
Summary: Operation Failed: [Resource unavailable] - failed to sync networks on host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: eraviv
QA Contact: msheena
URL:
Whiteboard:
Depends On:
Blocks: 1766193
TreeView+ depends on / blocked
 
Reported: 2019-06-25 12:37 UTC by Michael Burman
Modified: 2020-05-20 20:01 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:01:21 UTC
oVirt Team: Network
Embargoed:
mperina: ovirt-4.4?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 103558 0 'None' MERGED core: feature supported condition for skip commit network changes 2020-04-29 07:07:42 UTC
oVirt gerrit 103580 0 'None' MERGED core: skip commit network changes if supported 2020-04-29 07:07:43 UTC
oVirt gerrit 103924 0 'None' MERGED core: skip commit network changes if supported 2020-04-29 07:07:43 UTC

Description Michael Burman 2019-06-25 12:37:30 UTC
Description of problem:
Operation Failed: [Resource unavailable] - failed to sync networks on host

During network's sync test, we see this error time after time -

2019-06-25 10:47:41,979+0300 INFO  (jsonrpc/3) [api.network] START setupNetworks(networks={u'C4_sync1_1': {u'ipv6autoconf': False, u'nic': u'enp1s0f1', u'mtu': 1500, u'swi
tch': u'legacy', u'dhcpv6': False, u'STP': u'no', u'bridged': u'true'}, u'C4_sync1_3': {u'ipv6autoconf': False, u'switch': u'legacy', u'mtu': 1500, u'bonding': u'bond41', 
u'dhcpv6': False, u'STP': u'no', u'bridged': u'true'}, u'C4_sync1_2': {u'ipv6autoconf': False, u'nic': u'enp2s0f0', u'mtu': 1500, u'switch': u'legacy', u'dhcpv6': False, u
'STP': u'no', u'bridged': u'true'}}, bondings={}, options={u'connectivityCheck': u'true', u'connectivityTimeout': 120, u'commitOnSuccess': True}) from=::ffff:1.0.0.1,
45488, flow_id=129d17f3 (api:48)
2019-06-25 10:47:41,979+0300 WARN  (jsonrpc/3) [vds] concurrent network verb already executing (API:1512)
2019-06-25 10:47:41,979+0300 INFO  (jsonrpc/3) [api.network] FINISH setupNetworks return={'status': {'message': 'Resource unavailable', 'code': 40}} from=::ffff:1.0.0.1
45,45488, flow_id=129d17f3 (api:54)

2019-06-25 10:47:41,956+03 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-29) [15932d15] Command 'org.ovirt.engine.core.bll.network.
host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to Host
SetupNetworksVDS, error = Resource unavailable, code = 40 (Failed with error unavail and code 40)

2019-06-25 10:47:42,386+03 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-29) [] Operation Failed: [Resource unavailable]

* It is possible that setSafeNetworkConfig takes semaphore on vdsm and at the same time setupnetworks tries to grab same semaphore.
setup networks queues up and waits for lock, which it did not before. so once previous setup networks is done next one starts, but setSafe has not completed yet. 

The fix for BZ 1061569 has exposed this bug. 

Version-Release number of selected component (if applicable):
vdsm-4.40.0-395.git01b7715.el7.x86_64

How reproducible:
100% on 4.4 master

Steps to Reproduce:
1. Run host_network_api tests on 4.4 master

Actual results:
Operation Failed: [Resource unavailable] - failed to sync networks on host

Expected results:
Should work as expected

Comment 5 msheena 2020-03-22 10:57:32 UTC
Verified on
===========
ovirt-engine-4.4.0-0.25.master.el8ev.noarch
vdsm-4.40.5-1.el8ev.x86_64

Comment 6 Sandro Bonazzola 2020-05-20 20:01:21 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.