[FOLIO-3315] Elasticsearch failing in folio-testing Vagrant box Created: 20/Oct/21 Updated: 21/Oct/21 Resolved: 21/Oct/21 |
|
| 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 125 |
| Development Team: | FOLIO DevOps |
| Description |
|
Aivar Iusupov reports:
The error returned is:
|
| Comments |
| Comment by Aivar Iusupov [ 20/Oct/21 ] |
|
Wayne Schneider could you please also check folio-release vagrant box. Thank you. |
| Comment by Wayne Schneider [ 20/Oct/21 ] |
|
It appears that the Elasticsearch container is not created with the correct restart policy, so it does not come up with a fresh boot of the system. |
| Comment by Wayne Schneider [ 20/Oct/21 ] |
|
Aivar Iusupov as a temporary workaround until new Vagrant boxes are available, you can start the Elasticsearch container by logging into your VM with vagrant ssh and executing the command docker start elasticsearch. In my testing, once the container is up and available, searches in the Inventory app succeed. Note that in the folio/release Vagrant box, the sample Inventory records are not indexed in Elasticsearch (see
|
| Comment by Wayne Schneider [ 20/Oct/21 ] |
|
This has been fixed in folio-ansible and tested, and future Vagrant builds should have the correct behavior of starting up the Elasticsearch container on boot. |
| Comment by Aivar Iusupov [ 21/Oct/21 ] |
|
Wayne Schneider everything works well when I've applied your instructions. Thanks a lot! |
| Comment by Wayne Schneider [ 21/Oct/21 ] |
|
Validated with latest folio/testing and folio/snapshot box images. |