[FOLIO-2921] Docker-based slave nodes fail to launch after plugin updates Created: 16/Dec/20 Updated: 16/Dec/20 Resolved: 16/Dec/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P1 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps: Sprint 104 |
| Development Team: | FOLIO DevOps |
| Description |
|
After applying routine Jenkins plugins updates, Jenkins fails to launch Docker-based slave nodes. |
| Comments |
| Comment by John Malconian [ 16/Dec/20 ] |
|
The issue appears to be an incompatibility between the Jackson-2-api plugin and the Docker API plugin, but it's not enough to merely rollback to the previous version of the Jackson-2-api plugin. Junit 1.47 fails to load since it requires the new version of the Jackson-2-API plugin causing Jenkins crash. Rolled back jackson-2-api and junit updates manually and removed unused Kubernetes plugin since it relies on the latest version of jackson-2-api. Details are on the bug are located here: |