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.

Description of problem:

since NFSv4 requires additional configuration from both server and client side, we need to change the default value of NFS version from auto-negotiate to v3 as there are great number of RHEV users complaining a permission problem as some of the local mount created with nobody:nobody.
we need to take into account the following cases:

- upgrade from 3.0 to 3.1 
- RHEV-H which currently doesn't support NFSv4 in its TUI menus 

the real problem here is that both connectStorageServer and connectStoragePool succeeds, but some of the files are not readable.

http://gerrit.ovirt.org/8110

*** Bug 860325 has been marked as a duplicate of this bug. ***

(In reply to comment #7)
> http://gerrit.ovirt.org/8110
Please ignore this patch ^^^ and use these instead:

http://gerrit.ovirt.org/8241
http://gerrit.ovirt.org/8242

This bug is now 4 patches, containing this prior vdsm patch:
http://gerrit.ovirt.org/8241

And these 3 dependent patches to address changes in the engine:
http://gerrit.ovirt.org/8797
http://gerrit.ovirt.org/8242
http://gerrit.ovirt.org/8798

*** Bug 869956 has been marked as a duplicate of this bug. ***

Cloned bug to 871534 for the engine side of the fix.

The VDSM side of the fix has been merged, Change-Id I404df524419c663accf0890eb860c5a3afb81583.

[Note: qa-ack was removed by mistake, due to the firfox-bugzilla issue]

fixed. vdsm-4.9.6-41.0

Hi Ayal,

The bug 869956 which closed as duplicate of this bug was still reproduced in the newest package(vdsm-4.9.6-41.0.el6_3).

Thanks,
EricLee

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/RHSA-2012-1508.html