Bug 1537095 - [DNS] multi-host SetupNetworks command is not sent when a DNS entry is removed from network
Summary: [DNS] multi-host SetupNetworks command is not sent when a DNS entry is remove...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.1.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Alona Kaplan
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-22 12:29 UTC by Michael Burman
Modified: 2019-02-13 07:46 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:46:50 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.3+
rule-engine: blocker+


Attachments (Terms of Use)
engine log (238.98 KB, application/x-gzip)
2018-01-22 12:29 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87171 0 master MERGED engine: Calling setup networks after removing name server from a network 2020-08-17 11:17:27 UTC

Description Michael Burman 2018-01-22 12:29:55 UTC
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.

Comment 1 Red Hat Bugzilla Rules Engine 2018-01-29 16:28:29 UTC
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.

Comment 2 Red Hat Bugzilla Rules Engine 2018-02-05 15:43:01 UTC
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.

Comment 3 Alona Kaplan 2018-02-08 12:36:12 UTC
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.

Comment 4 Alona Kaplan 2018-02-11 08:53:38 UTC
Reopened the bug since vdsm does support the removal.

Comment 5 Michael Burman 2018-10-15 06:53:23 UTC
Verified on - 4.3.0-0.0.master.20181014151735.git18593d9.el7

Comment 6 Sandro Bonazzola 2018-11-02 14:38:14 UTC
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.

Comment 7 Sandro Bonazzola 2018-11-02 14:51:22 UTC
Closed by mistake, moving back to qa -> verified

Comment 8 Sandro Bonazzola 2019-02-13 07:46:50 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.