it also improves the network not available at startup problem that users have seen.
fix deadlock in dumpmaps and some amd map handling problems.
sudo dnf upgrade --advisory=FEDORA-2017-eda74692fc
This update has been submitted for testing by iankent.
This update has obsoleted autofs-5.1.4-1.fc27, and has inherited its bugs and notes.
Works for me
This update has been pushed to testing.
Still broken here, just like -1. Reverting to 5.1.3-4 fixes the problem immediately. I just just have a simple NFS mount.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@bojan, my testing on F27 indicates the opposite and AFAICT you have not provided information on your problem in a bug, please do so.
I can open a bug if you want, but this is a pretty straightforward regression for me. An NFS mount that works under 5.1.3-4 (and previous versions) simply stopped working under 5.1.4-1 and -4. Zero configuration changes on my end. Both server and client are running F27. What would you like me to put into the bug? Any specific diagnostic output?
I don't see that we have any other choice, there are some known problems with 5.1.3.
Include a debug log of the problem occurring (preferably from the start up of autofs).
These days it seems easiest to set "logging = debug" in /etc/autofs.conf and collect the log information with something along the lines of "journalctl -f 2>&1|tee autofs.log".
OK, here is what the problem is. I had this in my /etc/nsswitch.conf:
automount: files sss ldap
On my machine, neither sss nor ldap provide any auto mount points. This is all defined using regular files. So, I changed that to:
And it worked. With 5.1.3-4, the other two were simply ignored. But, somehow, this extra bit of configuration confuses version 5.1.4.
Note that I do run both ldap and sss, but I have no auto mounts defined there. So, autofs should try that, find nothing and carry on, I guess. Particularly because the files bit is set up correctly.
I'm well aware of this type of problem, it is a side effect of resolving a different problem and has been difficult to handle, here is not the place to discus it.
I'm just a user. From my perspective, this is a regression. That's all I'm trying to say. Anyway, I have a workaround now, so don't worry about it.
The regression was introduced in 5.1.3, you just weren't affected.
Fair enough, but I can only report what I see on the system where I use autofs.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
my mounts work
Works for me for auto-mounting NFS shares on LAN.
Tested and works.
Works for me.
iankent edited this update.
Karma has been reset.
We've had several reports of this change working ok.
We've also had one report of it not working properly but the reporter wasn't able to follow up with a bug report.
Hopefully pushing this to stable will flush out this problem.
This update has been submitted for batched by iankent.
This update has been submitted for stable by iankent.
This update has been pushed to stable.
Hello Ian, still getting automount[xxxxx]: add_host_addrs: hostname lookup failed: No address associated with hostname on all NIS clients. We don't see it on the NIS server at least. Should I enable debug in autofs?
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.