[FOLIO-2381] unexpected result from module cleanup in k8s Created: 04/Dec/19 Updated: 03/Jun/20 Resolved: 09/Dec/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Ian Hardy | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 78 |
| Development Team: | Core: Platform |
| Description |
|
John noticed several missing modules for the preview build. Running a dry run of the cleanup job (tip of master in folio-tools run from workstation) yeilded expected results, which are cleaning up non-enabled modules that are not the latest N copies (where N is set in the parameters of the cleanup job). The logs from the latest cleanup show a bunch of modules being removed not according to that pattern. Some ideas:
|
| Comments |
| Comment by Ian Hardy [ 04/Dec/19 ] |
|
redeployed release platform-core modules and modified the job w/the --dry-run flag so it should now report what would be cleaned up without taking action. |
| Comment by Ian Hardy [ 09/Dec/19 ] |
|
I think I failed tag the latest change to the cleanup script as "latest". This change had to do with natural sorting so that could explain why some of the wrong modules were getting cleaned up. I pushed the "latest" tag to docker hub, and now a dry run from k8s corresponds to what I would expect running the script from folio-tools#master now. I'm re-enabling the job now. |