This was fixed in
https://launchpad.net/ubuntu/+source/autofs/5.1.5-1ubuntu1, which is
linked with a newer libtirpc.
** Changed in: autofs (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
** Changed in: autofs (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: autofs (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Correct. We need to bring in the newer libtirpc, then we can link autofs
with it and fix this bug here about ipv6 support.
As of now, ubuntu cosmic has libtirpc-0.2.5-1.2 (old), and debian has
1.0.2-0.2 in experimental. That's a bit better than how it was a while
ago, when debian had a new source
Reopening the bug because autofs cannot be linked to our old libtirpc
without introducing a crash (see bug #1745817).
** Changed in: autofs (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: autofs (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/autofs/+git/autofs/+merge/343237
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs
It did, and I'm afraid I will have to revert this change. I couldn't get
autofs to work with the -hosts builtin map with libtirpc 0.2.x. It
worked with 1.0.3, which shows how ancient the package is in ubuntu (and
debian). Unfortunately now is too late to upgrade that lib to 1.0.3, as
that's even a
** No longer affects: autofs5 (Ubuntu)
** Changed in: autofs (Ubuntu)
Status: Confirmed => In Progress
** Changed in: autofs (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
This PPA has test packages built with libtirpc if someone has an
ipv6-only setup and is willing to give them a quick test:
https://launchpad.net/~ahasenack/+archive/ubuntu/autofs-ipv6-1101779/
Associated git branch:
https://code.launchpad.net/~ahasenack/ubuntu/+source/autofs/+git/autofs/+ref
It looks like upstream has settled on using libtirpc if ipv6 is needed. From
the autofs(5) manpage:
" To be able to use IPv6 within autofs maps the package must be build to
use the libtirpc library for its RPC communications. This is becuase the glibc
RPC implementation doesn't
There have been various upstream ipv6 related fixes in the debian/ubuntu
changelogs,, imported from upstream and otherwise.
Is this bug still present in debian stretch and ubuntu xenial with newer autofs
packages ? I'd suggest testing ubuntu-xenial in particular as the next LTS
release
The attachment auto.diff seems to be a patch. If it isn't, please
remove the patch flag from the attachment, remove the patch tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any
Seems that enabling libtirpc solves this.
I've attached simple patch.
** Patch added: auto.diff
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1101779/+attachment/4306761/+files/auto.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: autofs5 (Ubuntu)
Status: New = Confirmed
** Changed in: autofs (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1101779
I'm a bit confused - the linked redhat bug is listed as fixed with an
older version of autofs; the debian bug claims that using an FQDN for
an ipv6 host works, only ipv6 addresses fail, which seems different from
this bug description.
** Changed in: autofs (Ubuntu)
Importance: Undecided =
Is this bug also present in Debian, or does it only affect the Ubuntu
package?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs lookup_mount: exports lookup
Note that I turned on debug output in /etc/default/autofs:
LOGGING=debug
My NFS server has IPv4 as well as IPv6. Both addresses are in DNS (as A
and record, respectively).
** Bug watch added: Debian Bug tracker #709366
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709366
** Also
autofs fails to mount an IPv6 server. It seems to be that, regardless of
proto=tcp6, the DNS lookup uses IPv4:
Feb 26 15:09:15 svartkulp automount[21673]: mount_mount: mount(nfs): nfs
options=nfsvers=4,proto=tcp6,rsize=32768,wsize=32768,soft,async,intr,noatime,nodiratime,rw,
nobind=0,
** Changed in: debian
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs lookup_mount: exports lookup fails on IPv6-only hosts
To
18 matches
Mail list logo
