package puppet 5.4.0-2ubuntu3 failed to install/upgrade: installed puppet package post-installation script subprocess returned error exit status 1

[dezi]

-no further informations known
-deleted package

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: puppet 5.4.0-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
Uname: Linux 5.0.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Thu May 16 02:23:02 2019
ErrorMessage: installed puppet package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-05-03 (12 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
Python3Details: /usr/local/bin/python3.7, Python 3.7.3, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt 1.8.1
SourcePackage: puppet
Title: package puppet 5.4.0-2ubuntu3 failed to install/upgrade: installed puppet package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

From your log:
Setting up puppet (5.4.0-2ubuntu3) ...
adduser: No UID/GID pair is available in the range 100-999 (FIRST_SYS_UID - LAST_SYS_UID).
adduser: The user `puppet' was not created.

Do you really have no ID left in 100-999?
That would be odd.

Never the less the command it runs that fails is:
    adduser --quiet --system --group --home /var/lib/puppet \
            --no-create-home \
            --gecos "Puppet configuration management daemon" \
            puppet

Maybe you could run and debug what is happening independent to the puppet package?

You could check if the user was actually created but with some odd config?
$ id puppet

For me e.g. looks like:
uid=114(puppet) gid=121(puppet) groups=121(puppet)

And to check if really all are blocked:
$ for i in $(seq 100 999); do id $i; done

Finally I don't really know what you mean with "-deleted package".
You had not installed it before, tried to install on 2019-05-16 and that failed.
Where is the "deleted" part coming in?

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for puppet (Ubuntu) because there has been no activity for 60 days.]