Created attachment 1384401 [details] engine log Description of problem: [DNS] - SetupNetworks command doesn't sent on remove DNS name server from network. We have a new regression in the DNS feature. When removing a DNS entry via the network, engine doesn't send setup networks command to the host as it used be. Version-Release number of selected component (if applicable): 4.2.1.2-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Add host to RHV 2. Via edit network(ovirtmgmt) add 2 new DNS name servers 3. After all changes applied(manual refresh caps is needed in order to sync the network - BZ 1451261) remove 1 name server from the network. Actual results: Nothing happens, no event in the ui saying that engine applying changes on the host. On the host nothing changes. On previous versions, engine was sending events and was trying to apply the changes. Something has changed. Discovered in our automation tests. Expected results: Should work as expected.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
VDSM doesn't support removing existing nameservers. Therefore, sending the setup networks command to the vdsm once the nameserver is removed from the network won't have any effect anyway.
Reopened the bug since vdsm does support the removal.
Verified on - 4.3.0-0.0.master.20181014151735.git18593d9.el7
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 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.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.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.