Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1785

Debian 8 test failure with openjdk-8-jre-headless missing


    • Type: CI Blocker
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 5.0.0
    • Component/s: None
    • Labels:
    • CI Pipeline/s:
      platform puppetserver
    • Epic Link:
    • Team:
      Systems Engineering
    • Sub-team:
    • Story Points:
    • Sprint:
      Server 2017-05-03
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment


      After updating Puppet Server to use openjdk-8 dependency changes in the newest ezbake, we started seeing CI failures related to the inability to install openjdk-8-jre-headless on Jessie:

      From this job, we see:

      The following packages have unmet dependencies:
      	 puppetserver : Depends: openjdk-8-jre-headless but it is not installable

      The problem appears to be that for Jessie, we need to configure the jessie-backports repo and install openjdk-8-jre-headless via it. On the VM that failed to install puppetserver, I did the following:

      echo "deb http://ftp.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d
      apt-get update
      apt-get -t jessie-backports install "openjdk-8-jdk-headless"
      apt-get install --force-yes  -y puppetserver

      Note that I had to do the "apt-get -t jessie-backports" command before the puppetserver one because apt did not appear to want to install openjdk-8-jdk-headless from the backports repo without it:

      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.


          Issue Links



              • Assignee:
                adrien Adrien Thebo
                jeremy.barlow Jeremy Barlow
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:

                  Zendesk Support