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 1687951 - ipa-client-automount needs option to specify domain
Summary: ipa-client-automount needs option to specify domain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 8.1
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks: 1733209
TreeView+ depends on / blocked
 
Reported: 2019-03-12 18:16 UTC by joel
Modified: 2023-03-24 14:42 UTC (History)
9 users (show)

Fixed In Version: ipa-4.8.0-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1733209 (view as bug list)
Environment:
Last Closed: 2019-11-05 20:52:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github freeipa/freeipa/blob/master/ipatests/test_integration/test_nfs.py#L148 0 None None None 2019-11-13 05:49:04 UTC
Red Hat Issue Tracker FREEIPA-9600 0 None None None 2023-03-24 14:42:20 UTC
Red Hat Product Errata RHBA-2019:3348 0 None None None 2019-11-05 20:53:10 UTC

Description joel 2019-03-12 18:16:09 UTC 
Description of problem:
ipa-client-automount automatically sets idmapping to the idm domain

Version-Release number of selected component (if applicable):
7.6

How reproducible:
constant

Steps to Reproduce:
1. run the command 
2.
3.

Actual results:
ipa-client-automount adds the Domain as last line in /etc/idmapd

Expected results:
option to specify the domain, so admins don't have to manually change mapping

Additional info:
Comment 2 Rob Crittenden 2019-03-13 13:26:31 UTC 
Please provide a more detailed use case.
Comment 3 joel 2019-03-14 00:56:33 UTC 
Cu is requesting an option for ipa-client-automount like "--domain"  so the "Domain =" directive within /etc/idmapd.conf is set from the command line. This is so admins don't have to manually change the domain from the default idm one to another.
Comment 4 Rob Crittenden 2019-03-14 12:04:55 UTC 
Please confirm. The problem is that the client has a separate DNS domain than the IdM master so the Domain setting in /etc/idmapd.conf does not match the local value causing mapping to not work?
Comment 5 joel 2019-03-18 17:43:11 UTC 
customer responded:

Actually, there are 3 domains we are dealing with...

Our DNS domain
Our IDM domain 
Our NFSv4 domain

All of these are different.  Therefore, ipa-client-automount should not change an existing domain in /etc/idmapd.conf.

Currently, ipa-client-automount changes whatever domain is configured in /etc/idmapd.conf to that of the IDM domain, breaking NFSv4 mapping
Comment 10 François Cami 2019-04-17 12:16:17 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7918
Comment 11 François Cami 2019-05-06 15:48:14 UTC 
Fixed upstream
master:
https://pagure.io/freeipa/c/660c4984c6281055752d74dc276fc39a07da324a
https://pagure.io/freeipa/c/d76737e4c6131ae6b4f550b2b7c1a19304f1e3a8
Comment 12 François Cami 2019-05-06 16:49:06 UTC 
Fixed upstream
ipa-4-7:
https://pagure.io/freeipa/c/aefe6cecde7c756f3f593887cdd8e378639d6e62
https://pagure.io/freeipa/c/728cc314c85836cee29fef250cf197fc0fa8c908
Comment 21 anuja 2019-08-19 08:05:55 UTC 
Verified Using Version :
-----------------------------------------------------------
ipa-client-4.8.0-8.module+el8.1.0+3977+ec23ef34.x86_64
ipa-server-4.8.0-8.module+el8.1.0+3977+ec23ef34.x86_64
sssd-ipa-2.2.0-11.el8.x86_64
-----------------------------------------------------------

Verified Using Test:
upstream : test_nfs.py::TestNFS::test_automount()

[1m============================= test session starts ==============================[0m
platform linux -- Python 3.6.8, pytest-3.4.2, py-1.5.3, pluggy-0.6.0 -- /usr/libexec/platform-python
cachedir: .pytest_cache
rootdir: /home/cloud-user, inifile:
plugins: sourceorder-0.5, multihost-3.0
[1mcollecting ... [0mcollected 4 items

test_nfs.py::TestNFS::test_prepare_users <- ../../usr/lib/python3.6/site-packages/ipatests/test_integration/test_nfs.py [32mPASSED[0m[36m [ 25%][0m
test_nfs.py::TestNFS::test_krb5_nfsd <- ../../usr/lib/python3.6/site-packages/ipatests/test_integration/test_nfs.py [32mPASSED[0m[36m [ 50%][0m
test_nfs.py::TestNFS::test_krb5_nfs_manual_configuration <- ../../usr/lib/python3.6/site-packages/ipatests/test_integration/test_nfs.py [32mPASSED[0m[36m [ 75%][0m
test_nfs.py::TestNFS::test_automount <- ../../usr/lib/python3.6/site-packages/ipatests/test_integration/test_nfs.py [32mPASSED[0m[36m [100%][0m

---------------- generated xml file: /home/cloud-user/junit.xml ----------------
[32m[1m========================== 4 passed in 678.43 seconds ==========================[0m
Comment 24 errata-xmlrpc 2019-11-05 20:52:32 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.

https://access.redhat.com/errata/RHBA-2019:3348
Note You need to log in before you can comment on or make changes to this bug.