[FOLIO-1766] stripes container on folio/snapshot VM is not created Created: 31/Jan/19 Updated: 17/Aug/20 Resolved: 17/Aug/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps: Sprint 95 |
| Development Team: | FOLIO DevOps |
| Description |
|
On the folio/snapshot Vagrant VM, the stripes container seems to not be created and running. I noticed it while using the VM to troubleshoot another issue, no one else has reported the problem, to my knowledge. |
| Comments |
| Comment by David Crossley [ 07/Jan/20 ] |
|
See some discussion in the Slack #support channel on 2019-11-15 |
| Comment by David Crossley [ 21/Jan/20 ] |
|
And other on 2020-01-07 in #support |
| Comment by Wayne Schneider [ 17/Aug/20 ] |
|
Discussion on #sys-ops https://folio-project.slack.com/archives/C9BBWRCNB/p1597332485331400 and following. |
| Comment by Wayne Schneider [ 17/Aug/20 ] |
|
It looks like the packer configuration file in folio-infrastructure was not putting the snapshot build in the right Ansible group. Fixed in this commit: https://github.com/folio-org-priv/folio-infrastructure/commit/18f4fec50eec9a94fda7208ffe89162b4e952fe3 |