[SERVER-1785] Debian 8 test failure with openjdk-8-jre-headless missing Created: 2017/04/21  Updated: 2017/06/28  Resolved: 2017/04/25

Status: Closed
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: SERVER 5.0.0

Type: CI Blocker Priority: Normal
Reporter: Jeremy Barlow Assignee: Adrien Thebo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

CI Pipeline/s:
platform puppetserver
Epic Link: Drop Java 7
Team: Systems Engineering
Sub-team: Server
Story Points: 2
Sprint: Server 2017-05-03
Release Notes: Not Needed
QA Risk Assessment: Needs Assessment

 Description   

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.



 Comments   
Comment by Jeremy Barlow [ 2017/04/21 ]

Rob Braden, Past Haus - The puppetserver team talked about this and was thinking for now about adding the work to setup jessie-backports, etc. as a pre-suite step in the Puppet Server pipeline. But the disadvantage of doing that is that presumably other teams would need to do something similar in each of their pipelines as well. Do you think we should try to get this baked into our vmpooler images / somehow integrate into beaker to make this more common.

/CC Josh Cooper and Russell Mull.

Generated at Thu Nov 21 02:45:16 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.