[FOLIO-3760] Vagrant box -- yarn install failure Created: 19/Apr/23 Updated: 19/Apr/23 Resolved: 19/Apr/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 160 |
| Development Team: | FOLIO DevOps |
| RCA Group: | TBD |
| Description |
|
Jens Heinrich reports:
This is somewhat mysterious, because of course yarn install is used in creating the Stripes UI that is served up on the Vagrant box. Speculation: we use n lts to set the node version for the root user when building the box. Perhaps using lts is not specific enough. |
| Comments |
| Comment by Wayne Schneider [ 19/Apr/23 ] |
|
The explanation for the mystery is that the stripes-build role executes n 14 (pinning Node.js to v14 for actually building Stripes), while the add-users role executes n lts (after Stripes has been built), so the system Node.js moves to v18. I am fixing by adding the n invocation to the nodejs role and using a variable to allow us to set the version through configuration rather than code (and removing all other n invocations from the playbooks). |
| Comment by Wayne Schneider [ 19/Apr/23 ] |
|
This has been fixed in the default branch of folio-ansible, as well as the release-r3-2022 and release-r1-2023 branches. Next builds of Vagrant boxes should have the Node.js version set correctly. |