Description of problem: On Hosts> Network interfaces, there is an action called 'Save network configuration' which is always disabled. Inside the setup networks dialog, there is a save network configuration checkbox that seems to be the replacement for this action button. This checkbox is available on the Networks> Hosts > Setup Host networks dialog as well and the button is missing there. Since this is the same functionality seen from different ends, they need to be consistent. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
(In reply to mrao from comment #0) > Description of problem: On Hosts> Network interfaces, there is an action > called 'Save network configuration' which is always disabled. This is not entirely correct. If you don't check the "save network configuration" checkbox from within the setup networks dialog, this button will be enabled, indicating current configuration was not persisted on vdsm. If we decide to remove that button, the default of that checkbox in the setup networks dialog should be checked. That way the user will know that by unchecking it, the changes will not be saved. Also, without this button, there will be no indication in the host interfaces sub-tab whether the changes were saved or not. So, what should be the indicator of the configuration state (saved or not)? > Inside the > setup networks dialog, there is a save network configuration checkbox that > seems to be the replacement for this action button. This checkbox is > available on the Networks> Hosts > Setup Host networks dialog as well and > the button is missing there. Since this is the same functionality seen from > different ends, they need to be consistent. >
We should discuss this on list, but I think that with setupNetwork replacing individual addNetworks, users no longer need the Save button. Engine could perform the save automatically whenever it sees a host in a "dirty" state. The button is still required on clusterLevels that expose addNetwork/delNetwork. There, the auto-save suggested above should not happen.
Based on my comment #2 which explain the necessity of this button, and due to not receiving further inputs from the reporter - this bug is being closed. If wishes to modify the host networking behaviour, either start a discussion on list.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days