Created attachment 1186667 [details] LOgs Description of problem: Once moving host from legacy switch type to ovs type it's not possible to sync the networks back to legacy type again if moving back to legacy switch type cluster. Version-Release number of selected component (if applicable): 4.0.2.3-0.1.el7ev vdsm-4.18.9-1.el7ev.x86_64 openvswitch-2.4.1-1.git20160727.el7_2.x86_64 How reproducible: 100 Steps to Reproduce: 1. Add host to rhev-m 4.0.2 to legacy type cluster 2. Create ovs type cluster and move the host to this cluster(maintenance) 3. Sync the network/s on host 4. Move the host back to legacy type cluster and sync the network/s Actual results: Networks remain as ovs switch type, it seems like the sync succeeded, but there was no change. 'switch': 'ovs'}} Expected results: Should be able to switch back to legacy type
We do not yet support changing a legacy network to ovs and vice versa. it is in our immediate TODO list.
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.
Partial fail - Failing when bond configured on the host - 2016-12-12 08:34:56,782 ERROR (jsonrpc/0) [vds] All bondings must be reconfigured on switch type change (API:1526) Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1523, 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: (21, 'All bondings must be reconfigured on switch type change') - Without bond, ovs >> legacy succeeded smoothly I believe we should fail it at the moment.
As discussed with Dan, this bug has failedQa.
verification failed because we did not make sure we use ovs with a fix for bug 1397050. I hope we can retry in the future, but currently this bug is deferred.
New and fresh logs tested on latest rhv 4.2 - 4.2.0.2-0.1.el7 vdsm-4.20.9.3-1.el7ev openvswitch-2.7.3-2.git20171010.el7fdp.x86_64
- Add host to ovs type cluster - Move host to legacy type cluster - ovirtmgmt is out of sync - ovirtmgmt must be synced - we not sending setup networks to sync the network if moving from ovs to legacy. Trying to sync it manually, will result as failure on a SPM host(host lost connection and sync failed) and might success on a non-SPM host. Any how, if moving from ovs to legacy type we must sync the network and make it linux bridge on the host.
Created attachment 1375149 [details] fresh logs
We will only support setting the switch type in cluster creation.