[SERVER-2161] Document issues with third party gems when upgrading 9k Created: 2018/03/23  Updated: 2018/04/19  Resolved: 2018/04/19

Status: Closed
Project: Puppet Server
Component/s: DOCS, Puppet Server
Affects Version/s: SERVER 5.3.0
Fix Version/s: SERVER 5.3.1

Type: Task Priority: Normal
Reporter: Justin Stoller Assignee: Justin Stoller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Epic Link: JRuby in the Wild
Team: Server
Release Notes: Known Issue
Release Notes Summary: See the ticket description, which will be updated with known issues and workarounds.
QA Risk Assessment: Needs Assessment

 Description   

This is a ticket to track issues that we or the community run into with gem dependencies when switching from JRuby 1.7 to JRuby 9k. Please edit the description to keep it current with the known issues.

Problem: Autosign 0.1.2/Yard 0.8.x
Yard's rubygem integration is incompatible with the rubygems version we ship with 9k. It seems to cause a warning printed during puppetserver gem list (called during puppet runs applying updates via the puppetserver_gem provider). In our case this is caused by using autosign 0.1.2. Upgrading to autosign 0.1.3 bumps the yard requirement to a version compatible with the rubygems we ship in 9k based puppetserver.

Solution:
Upgrade yard to a 0.9.x version and look at bumping any server side gems that require yard 0.8.x. The autosign gem specifically should be at >= 0.1.3.



 Comments   
Comment by Justin Stoller [ 2018/03/23 ]

/cc Garrett Guillotte Don't know if this is a helpful way to track this or not but we'll want to call out compat issues discovered with JRuby 9k in a big way for folks. This (third party gems) seems like a family of compat issues that we'll see.

Comment by Kenn Hussey [ 2018/04/09 ]

Garrett Guillotte do you have the information you need here?

Comment by Garrett Guillotte [ 2018/04/09 ]

I see one known issue in this ticket. Justin Stoller are we expecting to hear more before the 5.3.1 release?

Comment by Justin Stoller [ 2018/04/09 ]

No, no one's reported any other issues. So hopefully we're in the clear for the release.

Comment by Garrett Guillotte [ 2018/04/09 ]

Kenn Hussey Then it sounds like I've got what I need here.

Comment by Garrett Guillotte [ 2018/04/17 ]

Kenn Hussey I'm not sure how to handle this ticket because the scope is open-ended.

Justin Stoller Is this ticket intended to be kept open to capture future issues or complaints beyond today's release?

Comment by Justin Stoller [ 2018/04/17 ]

This was intended to be a catch all, though I think we can say the timeframe we were expecting it catch things in has ended.

Comment by Kenn Hussey [ 2018/04/19 ]

Justin Stoller Garrett Guillotte can this be resolved/closed now that 5.3.1 has shipped?

Generated at Sun Oct 20 19:36:51 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.