[FOLIO-3966] Vagrant box build failure 25 Jan 2024 Created: 25/Jan/24 Updated: 26/Jan/24 Resolved: 26/Jan/24 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | 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 Requests |
| Development Team: | FOLIO DevOps |
| RCA Group: | TBD |
| Description |
|
The Vagrant box build has been in a failure state for the last 2+ weeks. Some of that is due to platform instability, but the latest failure is unusual. In the create-admin role, this task failed: snapshot: TASK [create-tenant-admin : Enable authtoken and dependencies] snapshot: fatal: [default]: FAILED! => {"changed": false, "elapsed": 37, "msg": "Status code was -1 and not [200]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://10.0.2.15:9130/_/proxy/tenants/diku/install"} This suggests that one or more of the modules that were disabled in order to be able to create the tenant admin user (modules that have a dependency on the authtoken interface) failed to be re-enabled. |
| Comments |
| Comment by Wayne Schneider [ 25/Jan/24 ] |
|
Two subsequent builds failed trying to enable all modules. Trying to reproduce locally. It's possible that the 20GB VBox image used to build the Vagrant images no longer provides enough resources for the build to complete. |
| Comment by Damien [ 25/Jan/24 ] |
|
Disk space has been very tight lately. I had to resize the logical volume in the Vagrantfile because the disk was larger (I think 32G) but not all that space could be used. sudo lvresize -rl +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv |
| Comment by Wayne Schneider [ 26/Jan/24 ] |
|
Thanks, Damien, I'll take a look at that as well. |
| Comment by Wayne Schneider [ 26/Jan/24 ] |
|
Updating the memory allocation for the build box to 24GB allowed the build to complete, there is now an updated snapshot box. I also resized lvol on the base box as Damien recommended, so there is now plenty of free space on the newest box. |
| Comment by Damien [ 26/Jan/24 ] |
|
An alternative to increasing memory allocation would be to enable Dynamic Swap Space. This is usually what I do with vagrant to avoid OOM crashes. 24G might make it hard for people to run on a machine with 32G. So far I only needed 15G to run the snapshot vagrant. sudo apt install swapspace -y |