Bug 1458724 - [DNS] [REST] - Add option to send an empty DNS configuration
Summary: [DNS] [REST] - Add option to send an empty DNS configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.0
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Martin Mucha
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-05 10:28 UTC by Michael Burman
Modified: 2017-12-20 10:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:52:32 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 78856 0 master MERGED restapi: allow to remove dns configuration 2017-07-16 15:23:55 UTC

Description Michael Burman 2017-06-05 10:28:46 UTC
Description of problem:
[DNS] [REST] - Add option to send an empty DNS configuration.

We would like to have the option to send an empty DNS configuration via rest api, just like in UI, we can un check the DNS configuration checkbox, which will remove the entity from the engine data base(not from the host if it's a single name server). 

It will prevent from the engine the check if the network is in sync or out-of-sync.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170604201000.git24e53f5.el7.centos

Comment 1 Meni Yakove 2017-07-20 07:59:08 UTC
ovirt-engine-4.2.0-0.0.master.20170718165351.gita56ecd5.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 10:52:32 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, 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.