[Bug 1827286] [NEW] autofs - "Too many levels of symbolic links" after apt upgrade

Jason D. Kelleher 1827286 at bugs.launchpad.net
Wed May 1 22:03:24 UTC 2019 

Public bug reported:

Description:    Ubuntu 16.04.6 LTS
Release:        16.04

I moved to autofs this week as a workaround for Bug #1577575 failing to
mount NFS entries at boot. This worked file until I ran 'apt upgrade'
today.

Now trying to access /vol/home mount results in the following error:

root at chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root at chi:~# 

Oddly enough, the other two autofs entries work fine (output trimmed):
root at chi:~# ls -la /vol/media
total 4
...
root at chi:~# 
root at chi:~# ls -al /vol/temp/
total 24
...
root at chi:~# 


I have a scratch VM I can break tonight by performing upgrades individually and testing after each.  Will provide that detail when available.


Here is /var/log/apt/history.log

 Start-Date: 2019-05-01  17:37:00
Commandline: apt upgrade
Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), ureadahead:amd64 (0.100.0-19, 0.100.0-19.1), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.4, 2.4.42+dfsg-2ubuntu3.5), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), passwd:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), login:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), iproute2:amd64 (4.3.0-1ubuntu3.16.04.4, 4.3.0-1ubuntu3.16.04.5), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), unattended-upgrades:amd64 (0.90ubuntu0.10, 1.1ubuntu1.18.04.7~16.04.2), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), uidmap:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9-doc:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), tzdata:amd64 (2018i-0ubuntu0.16.04, 2019a-0ubuntu0.16.04)
End-Date: 2019-05-01  17:37:24

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1827286

Title:
  autofs  - "Too many levels of symbolic links" after apt upgrade

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:    Ubuntu 16.04.6 LTS
  Release:        16.04

  I moved to autofs this week as a workaround for Bug #1577575 failing
  to mount NFS entries at boot. This worked file until I ran 'apt
  upgrade' today.

  Now trying to access /vol/home mount results in the following error:

  root at chi:~# ls -la /vol/home/
  ls: cannot access '/vol/home/': Too many levels of symbolic links
  root at chi:~# 

  Oddly enough, the other two autofs entries work fine (output trimmed):
  root at chi:~# ls -la /vol/media
  total 4
  ...
  root at chi:~# 
  root at chi:~# ls -al /vol/temp/
  total 24
  ...
  root at chi:~# 

  
  I have a scratch VM I can break tonight by performing upgrades individually and testing after each.  Will provide that detail when available.

  
  Here is /var/log/apt/history.log

   Start-Date: 2019-05-01  17:37:00
  Commandline: apt upgrade
  Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), ureadahead:amd64 (0.100.0-19, 0.100.0-19.1), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.4, 2.4.42+dfsg-2ubuntu3.5), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), passwd:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), login:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), iproute2:amd64 (4.3.0-1ubuntu3.16.04.4, 4.3.0-1ubuntu3.16.04.5), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), unattended-upgrades:amd64 (0.90ubuntu0.10, 1.1ubuntu1.18.04.7~16.04.2), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), uidmap:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9-doc:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), tzdata:amd64 (2018i-0ubuntu0.16.04, 2019a-0ubuntu0.16.04)
  End-Date: 2019-05-01  17:37:24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1827286/+subscriptions

More information about the foundations-bugs mailing list