Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2706

Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.0.0
    • Component/s: None
    • Labels:
      None
    • Template:

      Description

      We keep getting this error during Puppet installation for our PuppetDB builds:

      Setting up ruby-augeas (0.5.0-2) ...
      Setting up libaugeas-ruby (0.5.0-2) ...
      Setting up ruby-shadow (2.2.0-1) ...
      Setting up ruby-json (1.8.0-1build1) ...
      Setting up hiera (1.3.3-1puppetlabs1) ...
      Setting up puppet-common (3.6.1-1puppetlabs1) ...
      chage: the shadow password file is not present
      /usr/bin/chage failed with return code 15, shadow not enabled, password aging cannot be set. Continuing.
      chfn: PAM: Authentication failure
      adduser: `/usr/bin/chfn -f Puppet configuration management daemon puppet' returned error code 1. Exiting.
      dpkg: error processing package puppet-common (--configure):
       subprocess installed post-installation script returned error exit status 1
      dpkg: dependency problems prevent configuration of puppet:
       puppet depends on puppet-common (= 3.6.1-1puppetlabs1); however:
        Package puppet-common is not configured yet.
       
      dpkg: error processing package puppet (--configure):
       dependency problems - leaving unconfigured
      Processing triggers for libc-bin (2.19-0ubuntu6) ...
      Processing triggers for ca-certificates (20130906ubuntu2) ...
      Updating certificates in /etc/ssl/certs... 164 added, 0 removed; done.
      Running hooks in /etc/ca-certificates/update.d....done.
      Errors were encountered while processing:
       puppet-common
       puppet
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      A package failed to install.  Trying to recover:
      Setting up puppet-common (3.6.1-1puppetlabs1) ...
      Setting up puppet (3.6.1-1puppetlabs1) ...
      initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
      invoke-rc.d: policy-rc.d denied execution of start.
      

      (see http://jenkins-release.delivery.puppetlabs.net/job/puppetdb-packaging-2014-06-01-21-11-50-afb66e3aa28a5fe69963f490114c9a9f15cf927c/command=pl_deb%20COW=base-trusty-i386.cow/1/console)

      Now this only happens for Ubuntu 14.04, no other distro we can see exhibits this. It seems we're getting it about 50% of the time (rough guess).

      Just today we received the error twice in a row for both our stable and master branches:

      http://jenkins-release.delivery.puppetlabs.net/job/puppetdb-packaging-2014-06-01-21-11-50-afb66e3aa28a5fe69963f490114c9a9f15cf927c/command=pl_deb%20COW=base-trusty-i386.cow/1/console
      http://jenkins-release.delivery.puppetlabs.net/job/puppetdb-packaging-2014-06-01-23-08-48-d07001846081a5f187b287faddd80c9931ce8dbd/command=pl_deb%20COW=base-trusty-i386.cow/1/consoleFull

      If we can't get a resolution soon we'll have to drop Ubuntu 14.04 build targets from PDB temporarily as its starting to get more and more frequent now and its affecting our day to day.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ken Ken Barber
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support