[SERVER-1782] Unable to build ezbake packages for SLES 12 since no java-1.8.0-openjdk-headless Created: 2017/04/19  Updated: 2017/06/08  Resolved: 2017/04/26

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: 3
Sprint: Server 2017-05-03
Release Notes: Not Needed
QA Risk Assessment: Needs Assessment

 Description   

After upgrading Puppet Server's master branch to ezbake version 1.2.0, we're unable to build packages correctly for SLES12. See this build failure. In particular, this appears to be due to the following error message:

Error: No Package found for java-1.8.0-openjdk-headless



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

Rob Braden, Melissa Stone, or Morgan Rhodes - could one of you look into this for us? Past Haus indicated that he thought we might need to be running SP2 SP1 of SLES 12 in order to pull in the java-1.8.0-openjdk-headless package properly. Not sure if our rpm builders in CI are actually doing that yet or, if not, what it would take to get that to happen.

Comment by Rob Braden [ 2017/04/19 ]

Yep, my bad - I updated the PE mocks but not the FOSS mocks to use sles-12-sp2. Fixes are being submitted now.

Comment by Morgan Rhodes [ 2017/04/19 ]

This should be fixed on all the RPM builders at this point.

Comment by Jeremy Barlow [ 2017/04/19 ]

Rob Braden and Morgan Rhodes - thanks for jumping on this so quickly. Does this mean that we should be good to go for trying to build SLES12 again for Puppet Server? Are any ezbake changes required for the fix(es)?

Comment by Morgan Rhodes [ 2017/04/19 ]

Jeremy Barlow shouldn't need any ezbake changes, just missed a few module updates for setting up the mocks/cows

Comment by Morgan Rhodes [ 2017/04/19 ]

And yup, should be good to try again!

Comment by Jeremy Barlow [ 2017/04/20 ]

Hi Morgan Rhodes, we turned SLES-12 back on for our overnight run but appear to have gotten the same failure:

Error: No Package found for java-1.8.0-openjdk-headless

See this job for more details.

Is there anything on our side you can see that might be causing this?

Thanks again!

Comment by Rob Braden [ 2017/04/20 ]

Oh, looks like we need to tweak the package name for sles-12:

http://osmirror.delivery.puppetlabs.net/sles-12-sp2-x86_64/RPMS.os/java-1_8_0-openjdk-headless-1.8.0.101-14.3.x86_64.rpm

We'll submit a fix to ezbake ASAP

Comment by Jeremy Barlow [ 2017/04/20 ]

Cool, thanks Rob Braden. fyi, I moved this JIRA ticket to the "System Engineering" team so that it would appear on our scrum board for visibility but we can move things around if needed to track this from the "Release Engineering" side.

Comment by Jeremy Barlow [ 2017/04/20 ]

With the bump to lein-ezbake 1.2.1, it appears that SLES 12 is building again - see this build directory. I'll keep this ticket open long enough to confirm that build gets through CI successfully but looking good at this point. Thanks again Morgan Rhodes and Rob Braden!

Comment by Jeremy Barlow [ 2017/04/21 ]

Now that we've moved beyond just having the ability to build SLES 12 packages, we're getting failures installing the packages in CI. Here's the error, from this Jenkins job, that we see:

Problem: nothing provides java-1_8_0-openjdk-headless needed by puppetserver-5.0.0.master-0.1SNAPSHOT.2017.04.21T1009.sles12.noarch

When I logged onto the failing VM, it appeared to me that the VM had not been upgraded to SP1:

SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 0

We definitely need SP1 for JDK 1.8 on SLES 12, right, Past Haus? I don't see any flavor of java 1.8 on the SLES 12 SP 0 VM when I do a zypper search -s java, so it doesn't seem to be an issue of just a typo in our version dependency.

Do we need to work with SysOps to get SP1 used as a base on the SLES 12 pooler VMs?

Comment by Past Haus [ 2017/04/21 ]

Jeremy Barlow Yes we need to either move sles 12 pooler images to sp1 or add a new pool for sp1. I think a new ticket is required there, but i don't know what project it would go in. Rob Braden do you know?

Comment by Rob Braden [ 2017/04/21 ]

I'm on it. I'll move the sles-12 images to SP1 (or 2)

Comment by Jeremy Barlow [ 2017/04/21 ]

Awesome, thanks Rob Braden. fyi, Adrien Thebo.

Generated at Sat Jan 25 01:31:12 PST 2020 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.