Cannot purge biond glance-common (train)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Medium
|
Unassigned | ||
Queens |
Triaged
|
Medium
|
Unassigned | ||
Rocky |
Triaged
|
Medium
|
Unassigned | ||
Stein |
Triaged
|
Medium
|
Unassigned | ||
Train |
Triaged
|
Medium
|
Unassigned | ||
Ussuri |
Triaged
|
Medium
|
Unassigned | ||
Victoria |
Fix Released
|
Medium
|
Unassigned | ||
glance (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Triaged
|
Medium
|
Unassigned | ||
Focal |
Triaged
|
Medium
|
Unassigned | ||
Groovy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
when I am trying to purge glance-comon I am receiving and error.
The question about this issue is at:
https:/
Output of:
+ cat -n /var/lib/
1 #!/bin/sh
2
3 set -e
4
5 case $1 in
6 purge)
7 if (which deluser && getent passwd glance) > /dev/null 2>&1; then
8 deluser --system --quiet --backup-to /var/lib glance
9 fi
10 if (which delgroup && getent group glance) > /dev/null 2>&1; then
11 delgroup --system --quiet glance
12 fi
13 ;;
14 esac
15
16
+ getent passwd glance
glance:
+ getent group glance
glance:x:64062:
+ set +x
Shows that the glance user and group id are not system(ie under 1000).
Due to this the deluser and delgroup with the "--system" fails.
I don't know if the UID and GID are wrong or if the "--system" flag is wrong.
Either way it need to be fixed.
Thanks,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: glance-common 2:19.0.
ProcVersionSign
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB:
{
}
Date: Fri Jul 31 15:28:00 2020
InstallationDate: Installed on 2020-07-31 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: glance
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
mtime.conffile.
Changed in cloud-archive: | |
status: | Triaged → Fix Committed |
Eliezer, Thank you for reporting this bug and making Ubuntu better. I've confirmed this is a bug and triaged it as medium as there is a known work-around.