Bug 768199 - autofs global variable not properly passed to second-level file map
Summary: autofs global variable not properly passed to second-level file map
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ian Kent
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-16 01:17 UTC by sysedpks
Modified: 2013-02-14 01:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 01:18:43 UTC
Type: ---


Attachments (Terms of Use)

Description sysedpks 2011-12-16 01:17:18 UTC
Description of problem:

I have two-level automount file maps where the top /etc/auto.work defines a global variable 'name' as follows,
* -fstype=autofs -Dname=& file:/etc/auto.work.sub

The first file map /etc/auto.work.sub then uses a second file map as follows,
subwork -fstype=autofs file:/etc/auto.work.sub2

The second file map /etc/auto.work.sub2 then uses the variable to nfs mount,
* -fstype=nfs,vers=3 server:/work/${name}/subwork/&

It used to work in Fedora 14 but now the '${name}' variable is empty.

Version-Release number of selected component (if applicable):
autofs-5.0.6-3.fc16.x86_64
kernel-3.1.5-1.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. setup two-level automount file maps with a global variable defined at the top as above
2. cd /work/myname/subwork/mydir
3.
  
Actual results:
-bash: cd: /work/myname/subwork/mydir: No such file or directory

Expected results:
mount the directory

Additional info:

Here is the /var/log/messages output relevant to this problem:
automount[10791]: lookup_mount: lookup(file): looking up mydir
automount[10791]: lookup_mount: lookup(file): mydir -> -fstype=nfs,vers=3   server:/work/${name}/subwork/&
automount[10791]: parse_mount: parse(sun): expanded entry: -fstype=nfs,vers=3   server:/work//subwork/mydir
automount[10791]: parse_mount: parse(sun): gathered options: fstype=nfs,vers=3
automount[10791]: parse_mount: parse(sun): dequote("server:/work//subwork/mydir") -> server:/work//subwork/mydir
automount[10791]: parse_mount: parse(sun): core of entry: options=fstype=nfs,vers=3, loc=server:/work//subwork/mydir

We can see that ${name} is parsed as empty instead of 'myname'.

I tried to pass down the variable by defining it again in /etc/auto.work.sub as follows,
subwork -fstype=autofs,-Dname=${name} file:/etc/auto.work.sub2

but then it would duplicate the value, so that /work/myname/subwork/mydir will be mapped to server:/work/mynamemyname/subwork/mydir

I found a workaround though. If I change the first file map /etc/auto.work.sub to re-define it as an empty variable, it works,
subwork -fstype=autofs,-Dname= file:/etc/auto.work.sub2

Comment 1 Ian Kent 2012-01-03 00:21:27 UTC
OK, I'll investigate.

Comment 2 Ian Kent 2012-01-06 02:27:09 UTC
(In reply to comment #1)
> OK, I'll investigate.

Looks to me like this is broken on F14 also.
Can you give me a package version where this last worked
for you?

Comment 3 Fedora End Of Life 2013-01-16 22:46:14 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-14 01:18:47 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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