Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1402267

Summary: Failed to attach network to host in legacy cluster if the network's name is 'ovs'
Product: [oVirt] vdsm Reporter: Michael Burman <mburman>
Component: CoreAssignee: Petr Horáček <phoracek>
Status: CLOSED DUPLICATE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: low    
Version: ---CC: bugs, danken
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-08 14:54:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1404265, 1762717    
Bug Blocks:    
Attachments:
Description Flags
Logs none

Description Michael Burman 2016-12-07 07:23:01 UTC
Created attachment 1228906 [details]
Logs

Description of problem:
Failed to attach network to host in legacy cluster if the network's name is 'ovs'.

It is seems that when trying to attach network to host in legacy cluster and it's called 'ovs', 'ovs1', 'ovs2' and so on we failing with:

Error while executing action HostSetupNetworks: Failed to bring interface up

Traceback (most recent call last):
  File "/usr/share/vdsm/API.py", line 1473, in setupNetworks
    supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__
    return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in <lambda>
    **kwargs)
  File "<string>", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
    raise convert_to_error(kind, result)
ConfigNetworkError: (29, 'Invalid OVS interface type Bridge')


2016-12-07 09:00:55,249 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [73d2a028] START, HostSetupNetworksVDSCommand(HostName = orchid-vds2.qa.lab.tlv.redhat.com, Ho
stSetupNetworksVdsCommandParameters:{runAsync='true', hostId='119bc29a-12d6-4c85-9af4-19e9ea8ccc5a', vds='Host[orchid-vds2.qa.lab.tlv.redhat.com,119bc29a-12d6-4c85-9af4-19e9ea8ccc5a]', rollbackOnFailure='true', co
nnectivityTimeout='120', networks='[HostNetwork:{defaultRoute='false', bonding='false', networkName='ovs1', nicName='ens1f1', vlan='162', mtu='0', vmNetwork='true', stp='false', properties='null', ipv4BootProtocol
='NONE', ipv4Address='null', ipv4Netmask='null', ipv4Gateway='null', ipv6BootProtocol='NONE', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clus
terSwitchType='LEGACY'}), log id: 67909b5
2016-12-07 09:00:55,263 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [73d2a028] FINISH, HostSetupNetworksVDSCommand, log id: 67909b5
2016-12-07 09:01:14,590 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [73d2a028] Failed in 'HostSetupNetworksVDS' method
2016-12-07 09:01:14,657 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-3) [73d2a028] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM orchid-vd
s2.qa.lab.tlv.redhat.com command failed: Invalid OVS interface type Bridge
2016-12-07 09:01:14,657 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [73d2a028] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, erro
r = Invalid OVS interface type Bridge, code = 29
2016-12-07 09:01:14,658 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [73d2a028] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericE
xception: VDSErrorException: Failed to HostSetupNetworksVDS, error = Invalid OVS interface type Bridge, code = 29


Version-Release number of selected component (if applicable):
4.0.6.2-0.1.el7ev
vdsm-4.18.17-1.el7ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create new network called 'ova5' and attach to host in legacy type cluster
2. Detach the network and rename it to 'ovs5'
3. Try to attach the network to the host


Actual results:
Failed 
ConfigNetworkError: (29, 'Invalid OVS interface type Bridge')


Expected results:
Should work

Additional info:
It used to work just fine on previous version/s. It is a new regression caused by ovs i think.

Comment 1 Michael Burman 2016-12-07 07:31:11 UTC
supervdsm log:

MainProcess|jsonrpc.Executor/0::ERROR::2016-12-07 09:30:43,852::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks
Traceback (most recent call last):
  File "/usr/share/vdsm/supervdsmServer", line 94, in wrapper
    res = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 249, in setupNetworks
    _setup_networks(networks, bondings, options)
  File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 277, in _setup_networks
    netswitch.setup(networks, bondings, options, in_rollback)
  File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line 132, in setup
    _setup_legacy(legacy_nets, legacy_bonds, options, in_rollback)
  File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line 153, in _setup_legacy
    bondings, _netinfo)
  File "/usr/lib/python2.7/site-packages/vdsm/network/legacy_switch.py", line 464, in add_missing_networks
    _netinfo=_netinfo, **attrs)
  File "/usr/lib/python2.7/site-packages/vdsm/network/legacy_switch.py", line 182, in wrapped
    return func(network, configurator, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/network/legacy_switch.py", line 243, in _add_network
    net_ent_to_configure.configure(**options)
  File "/usr/lib/python2.7/site-packages/vdsm/network/models.py", line 187, in configure
    self.configurator.configureBridge(self, **opts)
  File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 116, in configureBridge
    _ifup(bridge)
  File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 994, in _ifup
    _exec_ifup(iface, cgroup)
  File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 951, in _exec_ifup
    _exec_ifup_by_name(iface.name, cgroup)
  File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 937, in _exec_ifup_by_name
    raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')
ConfigNetworkError: (29, 'Invalid OVS interface type Bridge')

Comment 2 Petr Horáček 2016-12-13 13:52:42 UTC
Thanks Michael, it is a bug in ifcfg init scripts.

Comment 3 Dan Kenigsberg 2017-01-08 14:54:28 UTC
there's nothing much to do on ovirt side.

*** This bug has been marked as a duplicate of bug 1404265 ***