Description of problem: A host might have several out-of-sync networks, a user has to currently go network-by-network and mark them to be synchronized as part of a Setup Networks command. This is tedious, especially when numerous hosts have numerous out-of-sync networks, especially via the GUI. Moreover, the "barrier" to start using the 3.6 Host Network QoS feature is quite high at the moment. Say a user has an existing setup, where several networks exist on each host interface, and they want to apply QoS on all their networks Due to the engine validation that either none or all of the networks on a specific NIC has QoS configured, adding QoS to each network separately (via the edit network dialog) will never succeed to propagate to the hosts using it. The end-state will be that all these networks will remain out-of-sync on all the hosts, their QoS configuration not applied - and to apply them, a user would have to go host-by-host, and mark each network to be synchronized. Version-Release number of selected component (if applicable): 3.6. How reproducible: Always. Steps to Reproduce: 1. Have one or more hosts with several networks on one interface. 2. Edit all these logical network entities, and attach QoS to each of them. Actual results: The logical network entities are up-to-date, but these networks will remain out-of-sync (and with no QoS applied) on the hosts using them (as long as no network was the only network on the same interface). Expected results: When editing each logical network entity separately, I don't see how the out-of-sync situation could be avoided. However, it should be easier for users to get out of this state - at least via the GUI, I'd expect users to be able to select all out-of-sync hosts and just press a button to synchronize all networks that are out-of-sync on them.
Could be implemented by properly crafting a Setup Networks command to the host, based on its current configuration and only marking all out-of-sync networks to be synchronized. Would be nice to also expose a special action via REST (on /api/hosts/{host:id}), not sure if necessary.
(In reply to Lior Vernia from comment #1) > Could be implemented by properly crafting a Setup Networks command to the > host, based on its current configuration and only marking all out-of-sync > networks to be synchronized. > > Would be nice to also expose a special action via REST (on > /api/hosts/{host:id}), not sure if necessary. From a customer perspective I think this would be a very cool feature!
Also, an "out-of-sync" column should be added to the hosts main tab - currently it would be marked as such if at least one of its networks is out-of-sync, but eventually this display might be affected by other notions of "out-of-sync-ness" if they exist (similarly the button would not only synchronize networks, rather anything that is out-of-sync).
Is this similar to BZ #1037612?
Could be considered related, but there's no overlap in actual functionality/implementation.
What about rest api ?
Verified on - 3.6.0.2-0.1.el6
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days