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
Bugs, which is subscribed to Ubu
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: debian
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount: exports lookup" fails on IPv6-only hosts
To manage notifi
> Is there any chance the new libtirpc will get backported into 18.04.1?
Unlikely. See https://wiki.ubuntu.com/StableReleaseUpdates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
aut
Is there any chance the new libtirpc will get backported into 18.04.1?
Not having IPv6-enabled autofs is going to wreck a lot of my workflow
once I start upgrading machines in August. I'm currently running a
custom build of autofs with libtirpc in 16.04 to enable this
functionality.
--
You receiv
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
Simon, I think you misunderstood. He had to revert this patch since it
caused a regression. So this bug isn't fixed yet. Ubuntu's libtirpc
needs to be updated before autofs can switch over to using it, is my
understanding.
--
You received this bug notification because you are a member of Ubunt
@ahasenack
Andreas, your linked-bug has supposedly been fixed, can you check this autofs
bug has therefore also been fixed and comment-further or close again...? Be
good to get this sorted-out before 18.04.1, with thanks!.
--
You received this bug notification because you are a member of Ubunt
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 receive
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/autofs/+git/autofs/+merge/343237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount:
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_moun
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
This appears to have caused a regression.
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1745817
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount: exports loo
This bug was fixed in the package autofs - 5.1.2-1ubuntu2
---
autofs (5.1.2-1ubuntu2) bionic; urgency=medium
* Fix IPv6 support by linking with libtirpc (LP: #1101779, Closes: #737679):
- d/control: add libtirpc-dev to build-depends
- d/rules: add --with-libtirpc to configur
** 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
Bugs, which is subscr
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/autofs/+git/autofs/+merge/336567
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount:
I have tested the package provided by ahasenack in ppa:autofs-ipv6-1101779
A 'cd' into the autofs managed directory worked perfectly right off the bat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/110
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
/bio
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
su
There is a patch filed against Debian 737679 that fixes the problem. If
it doesn't make it through Debian in time, can Ubuntu pick up this patch
for the next LTS? It would be a shame for another two years to go by and
not have proper IPv6 support.
--
You received this bug notification because you
Launchpad has imported 21 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=711844.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
In addition to the already linked bug, Debian bug 737679 also appears to
be closely related: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=737679
** Bug watch added: Debian Bug tracker #737679
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737679
--
You received this bug notification
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount: exports lookup" fails on IPv6-only hosts
To manage notifications about this bug go
Can confirm this still affects 16.04 LTS (autofs 5.1.1-1ubuntu3)
attempting to mount entry /net/data6
lookup_mount: lookup(file): looking up data6
lookup_mount: lookup(file): data6 -> atlantis.home.nivex.net:/data
parse_mount: parse(sun): expanded entry: atlantis.home.nivex.net:/data
parse_mount:
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 (underp
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
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
Bugs, which is subscri
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "l
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 => Me
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount: exports lookup" fails on IPv6-only h
** Changed in: debian
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101779
Title:
autofs "lookup_mount: exports lookup" fails on IPv6-only hosts
To manage notificatio
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, nosymlin
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 aff
33 matches
Mail list logo
