On Thu, May 01, 2014 at 03:03:55PM -0700, Derek Robati wrote:
> We use NIS on our Ubuntu 14.04 LTS HP ProLiant server.
> 
> After following the steps at 
> https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
> 
> $ sudo apt-get install jenkins                                             
>              
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> jenkins is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] 
> Setting up jenkins (1.561) ...
> adduser: The user `jenkins' already exists. Exiting.
> dpkg: error processing package jenkins (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  jenkins
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> I really believe the issue is with NIS. Any suggestions?

I would call it a bug in the upstream Jenkins Debian package postinst script.

E.g. the official Ubuntu Jenkins package checks whether the user exists
before attempting to install it:

        # Create jenkins user if it doesn't exist.
        if ! id jenkins > /dev/null 2>&1 ; then
            adduser --system --home /var/lib/jenkins --no-create-home \
                --group --disabled-password --quiet --shell /bin/bash \
                jenkins 
        fi

while the .deb provided upstream blindly goes ahead and tries to create
it always (despite the comment):

        # Create jenkins user if it doesn't exist.
        # sometimes tools that users want Jenkins to run need a shell,
        # so use /bin/bash. See JENKINS-4830
        addgroup --system --quiet $JENKINS_GROUP
        adduser --system --quiet --home /var/lib/jenkins --no-create-home \
            --ingroup $JENKINS_GROUP --disabled-password --shell /bin/bash \
            --gecos 'Jenkins' \
            $JENKINS_USER


Marius Gedminas
-- 
Never, ever expect hackers to be able to read closed proprietary document
formats like Microsoft Word. Most hackers react to these about as well as you
would to having a pile of steaming pig manure dumped on your doorstep.
        -- ESR (http://www.tuxedo.org/~esr/faqs/smart-questions.html)

Attachment: signature.asc
Description: Digital signature

Reply via email to