Bug 1029611

Please post a full debug log of reproducing the problem.

Ensure that syslog is recording facility daemon and level debug
and above to ensure the debug logging gets recorded.

Then set LOGGING="debug" in the autofs configuration.

Also post the output from "showmount -e 10.34.73.3".

Created attachment 823319 [details]
/var/log/messages

# showmount -e 10.34.73.3
Export list for 10.34.73.3:
/nfs *


interesting part of /var/log/messages:

Nov 13 10:38:40 dhcp130-218 automount[14701]: handle_packet: type = 3
Nov 13 10:38:40 dhcp130-218 automount[14701]: handle_packet_missing_indirect: token 1, name 10.34.73.3, request pid 14734
Nov 13 10:38:40 dhcp130-218 automount[14701]: attempting to mount entry /net/10.34.73.3
Nov 13 10:38:40 dhcp130-218 automount[14701]: lookup_mount: lookup(hosts): 10.34.73.3 -> (null)
Nov 13 10:38:40 dhcp130-218 automount[14701]: get_exports: lookup(hosts): fetchng export list for 10.34.73.3
Nov 13 10:38:40 dhcp130-218 automount[14701]: get_exports: lookup(hosts): exports lookup failed for 10.34.73.3
Nov 13 10:38:40 dhcp130-218 automount[14701]: key "10.34.73.3" not found in map source(s).
Nov 13 10:38:40 dhcp130-218 automount[14701]: dev_ioctl_send_fail: token = 1
Nov 13 10:38:40 dhcp130-218 automount[14701]: failed to mount /net/10.34.73.3

Right, I'll try and duplicate it and see.
I believe the impression that the get exports works OK ....
So there might be something at bit more strange going on.

(In reply to Ian Kent from comment #3)
> I believe the impression that the get exports works OK ....

Rather, I believe the get exports works OK ....

(In reply to Ian Kent from comment #4)
> (In reply to Ian Kent from comment #3)
> > I believe the impression that the get exports works OK ....
> 
> Rather, I believe the get exports works OK ....

Yes, it does. I can manually mount it (just mount 10.34.73.3:/nfs /mnt/blah) without any issues.

I also checked the config of my RHEL 6 box where automount works just fine and apart from nsswitch (that doesn't mention sss for automount), the configuration is literally the same...

(In reply to David Jaša from comment #5)
> (In reply to Ian Kent from comment #4)
> > (In reply to Ian Kent from comment #3)
> > > I believe the impression that the get exports works OK ....
> > 
> > Rather, I believe the get exports works OK ....

I meant the autofs get exports.

> 
> Yes, it does. I can manually mount it (just mount 10.34.73.3:/nfs /mnt/blah)
> without any issues.
> 
> I also checked the config of my RHEL 6 box where automount works just fine
> and apart from nsswitch (that doesn't mention sss for automount), the
> configuration is literally the same...

Mmmm ... I am able to reproduce it.
It's odd since that code hasn't changed for a long time.
It must be a side effect of some other change.

Ian

I see that configure was throwing an error.
It needed to be regenerated due to a recent change in Fedora
that assumed a configure function existed when it didn't.

Can you try autofs build autofs-5.0.7-34.el7 please.

(In reply to Ian Kent from comment #8)
> Can you try autofs build autofs-5.0.7-34.el7 please.

Works for me, thank you.

Hi Ian, test fail in autofs-5.0.7-34.el7.

{INFO} platform:
RedHatEnterpriseWorkstation 7.0
Linux intel-mahobay-01.rhts.eng.nay.redhat.com 3.10.0-49.el7.x86_64 #1 SMP Tue Nov 12 16:19:27 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
autofs-5.0.7-34.el7.x86_64

================================================================================
[20:57:47 root@ /mnt/tests/CoreOS/autofs/master-config]# ls -l /net/localhost/TEST1
ls: cannot access /net/localhost/TEST1: No such file or directory
:: [   FAIL   ] :: Test auto.net automount (Expected 0, got 2)
--------------------------------------------------------------------------------

================================================================================
[20:58:17 root@ /mnt/tests/CoreOS/autofs/master-config]# mount | grep /net/localhost/TEST1
:: [   FAIL   ] :: hosts mount is OK (Expected 0, got 1)
--------------------------------------------------------------------------------

You really should get rid of the references to auto.net in
that test.

The auto.net script hasn't been used since RHEL-4.
The hosts map is an internal autofs map now.

(In reply to Yin.JianHong from comment #10)
> Hi Ian, test fail in autofs-5.0.7-34.el7.

Odd, it worked ok for the reporter.

> 
> {INFO} platform:
> RedHatEnterpriseWorkstation 7.0
> Linux intel-mahobay-01.rhts.eng.nay.redhat.com 3.10.0-49.el7.x86_64 #1 SMP
> Tue Nov 12 16:19:27 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
> autofs-5.0.7-34.el7.x86_64
> 
> =============================================================================
> ===
> [20:57:47 root@ /mnt/tests/CoreOS/autofs/master-config]# ls -l
> /net/localhost/TEST1
> ls: cannot access /net/localhost/TEST1: No such file or directory
> :: [   FAIL   ] :: Test auto.net automount (Expected 0, got 2)
> -----------------------------------------------------------------------------
> ---
> 
> =============================================================================
> ===
> [20:58:17 root@ /mnt/tests/CoreOS/autofs/master-config]# mount | grep
> /net/localhost/TEST1
> :: [   FAIL   ] :: hosts mount is OK (Expected 0, got 1)
> -----------------------------------------------------------------------------
> ---

OK, I'll check out a machine and run the test.

That's an interesting test.

We're expecting to get the exports list from localhost but
the actual mount will be a bind mount (without the "nobind"
option).

Still it should work.

Ian

Hi Ian,

this case test all pass in RHEL6.5;
    https://beaker.engineering.redhat.com/jobs/544239
in RHEL7
    ls /net/localhost/TEST1  fail;

Created attachment 825874 [details]
Patch - fix ipv6 libtirpc getport

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

verified
  https://beaker.engineering.redhat.com/jobs/552115

FYI, we also hit this problem in rhel7 and installing
autofs-5.0.7-35.el7.x86_64.rpm fixed the problem.

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

How do I get autofs-5.0.7-35.el7.x86_64.rpm? If I connect my RHEL7 beta to the RHN can I get that package?

(In reply to Dax Kelson from comment #21)
> How do I get autofs-5.0.7-35.el7.x86_64.rpm? If I connect my RHEL7 beta to
> the RHN can I get that package?

Not sure but I will put revision 38 on people.redhat.com.

Understand this package is not the official RHEL-7.0 package
yet but it should show up in the repository at some time
unless there are further changes due to ongoing QA work.

Try:
http://people.redhat.com/~ikent/autofs-5.0.7-38.el7/

RHEL7 release candidate no longer has this bug. This bug should be closed.

(In reply to Dax Kelson from comment #23)
> RHEL7 release candidate no longer has this bug. This bug should be closed.

The bug state is VERIFIED, it'll get closed as part of process
for the GA release.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.