fail to upgrade fuse in xenial, in lxd

Bug #1556143 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fuse (Ubuntu)
Fix Released
Undecided
Unassigned
lxd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

# apt install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libfuse2
The following packages will be upgraded:
  fuse libfuse2
2 upgraded, 0 newly installed, 0 to remove and 111 not upgraded.
Need to get 110 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main s390x fuse s390x 2.9.4-1ubuntu2 [24.5 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports xenial/main s390x libfuse2 s390x 2.9.4-1ubuntu2 [85.4 kB]
Fetched 110 kB in 0s (167 kB/s)
(Reading database ... 26065 files and directories currently installed.)
Preparing to unpack .../fuse_2.9.4-1ubuntu2_s390x.deb ...
Unpacking fuse (2.9.4-1ubuntu2) over (2.9.4-1ubuntu1) ...
Preparing to unpack .../libfuse2_2.9.4-1ubuntu2_s390x.deb ...
Unpacking libfuse2:s390x (2.9.4-1ubuntu2) over (2.9.4-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libfuse2:s390x (2.9.4-1ubuntu2) ...
Setting up fuse (2.9.4-1ubuntu2) ...
Creating fuse device...
mknod: fuse-: Operation not permitted
makedev fuse c 10 229 root root 0660: failed
chmod: cannot access '/dev/fuse': No such file or directory
dpkg: error processing package fuse (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Errors were encountered while processing:
 fuse
E: Sub-process /usr/bin/dpkg returned an error code (1)

In an lxd container (beta-1, installing fuse latest).

Tags: s390x
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I am really confused about:

  if [ ! -e /dev/fuse ]
  then
   if [ -x /sbin/MAKEDEV ]
   then
    echo "Creating fuse device..."

    cd /dev
    MAKEDEV fuse
    chmod 0666 /dev/fuse
   else
    echo "MAKEDEV not installed, skipping device node creation."
   fi
  fi

as far as I understand /dev/fuse is automatically created by kernel/udev what not, so it shouldn't be created with makedev. If it's not there, it's not there....

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Indeed created by /lib/udev/rules.d/50-udev-default.rules

Changed in lxd (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fuse - 2.9.4-1ubuntu3

---------------
fuse (2.9.4-1ubuntu3) xenial; urgency=medium

  * Drop modprobing fuse module, it's builtin on ubuntu.
  * Drop creating /dev/fuse, udev does it for us. (LP: #1556143).
  * Drop udev|makedev dependency.

 -- Dimitri John Ledkov <email address hidden> Fri, 11 Mar 2016 15:37:54 +0000

Changed in fuse (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.