Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
The here are the correction for the following steps:
Chapter 9.3. Setting up a Kerberized NFS Server
- I removed the 'v4'
6. Install the NFS package. For example:
yum install nfs-utils
7. Add the NFS probe modules.
- Not needed
9. Edit the NFS server configuration to use NFSv4 security.
vi /etc/sysconfig/nfs
uncomment SECURE_NFS="yes"
10. Edit the NFS common configuration to enable the domain and UID/GID mapping.
- Not needed.
11. Configure the NFS domain
- is only needed if clients and servers are in different DNS domains
15. Restart the NFS server.
Changes for: 9.3.2. Setting up a Kerberized NFS Client
5. Edit the NFS common configuration to enable the domain and UID/GID mapping
- Not needed
6. Edit the NFS common configuration to enable the domain and UID/GID mapping.
- Definitely not needed.. ;-)
7. Configure the NFS domain. The idmapd.conf must be the same on the NFS client as it is on the NFS server.
- again only needed if clients and the server are in different DNS domains
8. Start the GSS and name mapping daemons.
- only the rpcgssd daemon has to be started.
service rpcgssd start
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description of problem: The here are the correction for the following steps: Chapter 9.3. Setting up a Kerberized NFS Server - I removed the 'v4' 6. Install the NFS package. For example: yum install nfs-utils 7. Add the NFS probe modules. - Not needed 9. Edit the NFS server configuration to use NFSv4 security. vi /etc/sysconfig/nfs uncomment SECURE_NFS="yes" 10. Edit the NFS common configuration to enable the domain and UID/GID mapping. - Not needed. 11. Configure the NFS domain - is only needed if clients and servers are in different DNS domains 15. Restart the NFS server. Changes for: 9.3.2. Setting up a Kerberized NFS Client 5. Edit the NFS common configuration to enable the domain and UID/GID mapping - Not needed 6. Edit the NFS common configuration to enable the domain and UID/GID mapping. - Definitely not needed.. ;-) 7. Configure the NFS domain. The idmapd.conf must be the same on the NFS client as it is on the NFS server. - again only needed if clients and the server are in different DNS domains 8. Start the GSS and name mapping daemons. - only the rpcgssd daemon has to be started. service rpcgssd start Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: