ubuntu-base on jammy daily: apt-key has no access to /dev/null

Bug #1955859 reported by Joshua Peisach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu QA Website
New
Undecided
Unassigned
apt (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Jammy Core - Smoke test fails.

One of the issues that I believe may be the primary issue is that apt-key has no access to /dev/null.

root@Joshua-PC:/# apt-get update
Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:3 http://security.ubuntu.com/ubuntu jammy-security Release [89.8 kB]
Get:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg [819 B]
0% [Waiting for headers]/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg
Ign:5 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates Release [89.8 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [90.7 kB]
0% [Working] 13.8 kB/s 0s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Err:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Get:8 http://archive.ubuntu.com/ubuntu jammy Release [269 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg [819 B]
0% [Working] 13.8 kB/s 6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg
Get:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg [819 B]
0% [Working] 13.8 kB/s 6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Ign:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg
Reading package lists... Done
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security Release: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates Release: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy Release: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://archive.ubuntu.com/ubuntu jammy Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: apt 2.3.9
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 27 20:14:22 2021
InstallationDate: Installed on 2020-10-23 (430 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
SourcePackage: apt
UpgradeStatus: Upgraded to impish on 2021-10-15 (73 days ago)

Revision history for this message
Joshua Peisach (itzswirlz) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1955859

tags: added: iso-testing
Revision history for this message
Julian Andres Klode (juliank) wrote (last edit ):

Thanks for your bug report. I believe you meant ubuntu-base, not ubuntu-core (the snap based one)

How did you test this? This seems to me like you forgot to populate /dev, either statically or by bind mounting the /dev from the host.

The tarball only contains an empty /dev, and the permissions have not changed.

jak@jak-t480s:~/Downloads$ tar tvzf jammy-base-amd64.tar.gz dev
drwxr-xr-x root/root 0 2021-12-28 06:01 dev/
jak@jak-t480s:~/Downloads$ tar tvzf focal-base-amd64.tar.gz dev
drwxr-xr-x root/root 0 2021-12-28 05:44 dev/

If APT had succeeded *creating* /dev/null as a regular files, all hell would have broken lose, so I am kind of happy that did not happen.

For the record, the reason it fails with EPERM seems to be that it's apt-key that's failing and it's run as the user _apt by apt.

summary: - ubuntu-core on jammy daily: apt-key has no access to /dev/null
+ ubuntu-base on jammy daily: apt-key has no access to /dev/null
Changed in apt (Ubuntu):
status: New → Incomplete
Revision history for this message
Julian Andres Klode (juliank) wrote (last edit ):

I believe this is actually a bug in the QA website which misses the step to setup /dev in the test scenario https://iso.qa.ubuntu.com/qatracker/testcases/1318/info - so reassigning there and marking the apt task as Invalid, but keeping it around rather than deleting it, as it's related.

Changed in apt (Ubuntu):
status: Incomplete → Invalid
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.