Bug 1063993

Summary:	NFSv4 Domain can not remove once your configured it
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.6	CC:	acathrow, bsarathy, cboyle, cpelland, cshao, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, mburns, ovirt-maint, pm-eus, rbarry, yaniwang, ycui, zdover
Target Milestone:	rc	Keywords:	TestOnly, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, it was not possible to remove the NFSv4 domain after it had been set. It is now possible to remove the NFSv4 domain after it has been set.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-17 14:58:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	960833
Bug Blocks:

Description Chris Pelland 2014-02-11 18:11:15 UTC

This bug has been copied from bug #960833 and has been proposed
to be backported to 6.5 z-stream (EUS).

Comment 3 wanghui 2014-02-13 05:29:12 UTC

Test version:
rhevh-6.5-20140212.1.el6ev.iso 
ovirt-node-3.0.1-18.el6_5.4.noarch

Test step:
1. Clear install rhevh-6.5-20140212.1.el6ev.iso.
2. On the Remote Storage page, configure NFSv4 Domain in TUI.
3. On the Remote Storage page, remove the NFSv4 Domain in TUI.
4. Check in /etc/idmapd.conf file.

Test result:
1. After step3, it can remove the NFSv4 Domain in TUI.
2. After step4, it commented out the Domain name in /etc/idmapd.conf file.

So this bug is fixed in ovirt-node-3.0.1-18.el6_5.4.noarch. Change the status from ON_QA to Verified.

Comment 4 errata-xmlrpc 2014-02-17 14:58:19 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0182.html