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.

Bug 768177

Summary: [RFE] IPA Automount cross-location support
Product: Red Hat Enterprise Linux 7 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED DEFERRED QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: jgalipea, mkosek, mniranja, rcritten, sigbjorn, ssorce
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 732791 Environment:
Last Closed: 2015-01-16 13:03:15 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: 732791    
Bug Blocks:    

Description Dmitri Pal 2011-12-15 22:54:49 UTC
+++ This bug was initially created as a clone of Bug #732791 +++

Description of problem:

IPA Automount configuration: Is it possible to reference an automount
 map from another location? E.g. under Policy -> Automount -> Add map
 -> Parent Map: <reference to other location>.auto.data

 Example: Let's say you have the following automount locations defined
 in IPA: NewYork, Washington, Miami. Each location has it's own
 auto.data map mounted under /data.

 Then making a common automount map in all the locations called
 auto.global, mounted at /global, each referencing the auto.data maps
 from the different IPA locations?

 /global/washington -> Washington's auto.data map
 /global/newyork -> NewYork's auto.data map
 /global/miami -> Miami's auto.data map

 I'm not looking for the configuration of the /global map to be
 automatic, a manual configuration for pointing to each locations
 auto.data map would do just fine.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

--- Additional comment from rcritten on 2011-08-23 13:26:11 EDT ---

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1699

Comment 2 Martin Kosek 2015-01-16 13:03:15 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in near Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the request, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request in the referred upstream Trac ticket.