RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 868213 - [RHEV-H 6.4][RFE]Better to show an example about "NFSv4 Domain"
Summary: [RHEV-H 6.4][RFE]Better to show an example about "NFSv4 Domain"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-19 09:40 UTC by haiyang,dong
Modified: 2013-02-28 16:41 UTC (History)
12 users (show)

Fixed In Version: ovirt-node-2.5.0-8.el6
Doc Type: Enhancement
Doc Text:
The installation screen for the hypervisor now provides an example format (example.redhat.com) to guide users in specifying an NFSv4 domain as a remote storage location.
Clone Of:
Environment:
Last Closed: 2013-02-28 16:41:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0556 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2013-02-28 21:29:06 UTC

Description haiyang,dong 2012-10-19 09:40:03 UTC
Description of problem:
Clean install rhev-hypervisor6-6.4-20121015.1.el6,
When configure "kernel Dump" by using "NFS/SSH",
There are some example shown:
NFS Location(example.redhat.com:/var/crash):
SSH Location(root.com)
on TUI
check Remote Storage Page, About "NFSv4 Domain".
Better to show an example about hot to use "NFSv4 Domain"
For example "NFSv4 Domain(example.redhat.com:/var/nfsdomain):"

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121015.1.el6

How reproducible:
100%

Steps to Reproduce:
1.Clean install rhev-hypervisor6-6.4-20121015.1.el6
2.Check "NFSv4 Domain" on Remote Storage Page 

Actual results:


Expected results:


Additional info:

Comment 4 haiyang,dong 2012-12-14 08:04:14 UTC
Test version:
rhev-hypervisor6-6.4-20121212.1.el6 
ovirt-node-2.5.0-11.el6

Tested as follows:
1.Clean install rhev-h
2.Check "NFSv4 Domain" on Remote Storage Page 

Notice that added example:

NFSv4 Domain (example.redhat.com):

so this bug has been fixed, change the status into "VERIFIED"

Comment 6 errata-xmlrpc 2013-02-28 16:41:40 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-2013-0556.html


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